fixes

Author: patriciasantaana

src/content/docs/bots/concepts/bot/signed-bots/index.mdx renamed to src/content/docs/bots/concepts/bot/signed-agents/index.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: overview
-title: Signed bots
+title: Signed agents
 sidebar:
   order: 3
 learning_center:
@@ -23,7 +23,7 @@ A bot cannot be registered as both a verified bot and a signed agent. Review Clo
 
 For an agent to be recognized, it must meet the following requirements:
 
-1. The agent must follow the [signed agents policy](/bots/concepts/bot/signed-bots/policy/).
+1. The agent must follow the [signed agents policy](/bots/concepts/bot/signed-agents/policy/).
 2. The bot must be using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/).
 
 Once Cloudflare verifies a bot, it should appear on [Cloudflare Radar's list of verified bots](https://radar.cloudflare.com/verified-bots).

src/content/docs/bots/concepts/bot/signed-bots/policy.mdx renamed to src/content/docs/bots/concepts/bot/signed-agents/policy.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: reference
-title: Verified bots policy
+title: Signed agents policy
 sidebar:
     order: 3
     label: Policy
@@ -10,35 +10,35 @@ sidebar:
 
 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.
 
-## Agent Policy
+## Agent policy
 
-### Minimum Traffic
+### Minimum traffic
 
 An agent must have a minimum amount of traffic for Cloudflare to be able to find it in the sampled data. The minimum traffic should have more than 1,000 requests per day across multiple domains.
 
-### Minimum Zones
+### Minimum zones
 
 Service must be made for a widespread use of zones.
 
 #### Example
 
 A bot crawling one site is not valid.
 
-### Agent Identification
+### Agent identification
 
 The User-Agent field is optional as it is not required for Web Bot Authentication.
 
 However, if you choose to provide a User-Agent, it and the message signature must meet the following requirements:
 
-- Have at least 5 characters.
+- Have at least five characters.
 - Must not contain special characters.
 - Must not include the same user-agent of another verified service.
 
 #### Example
 
 `cloudflare-browser-rendering` is a valid message signature.
 
-### Service Purpose
+### Service purpose
 
 The purpose of the service should be benign or helpful to both the owner of a zone and the users of the service. The service cannot perform any of the following:
 
@@ -53,15 +53,17 @@ The purpose of the service should be benign or helpful to both the owner of a zo
 
 Mass price scraping direct e-commerce competitors is not a valid use case.
 
-### Public Documentation
+### Public documentation
 
 The agent must have a publicly documented purpose and expected behavior.
 
-## Breach of Policy
+---
+
+## Breach of policy
 
 If any of the requirements to validate are breached, a service will be removed from the global allowlist.
 
-#### Example breaches of policy
+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.

src/content/docs/bots/concepts/bot/verified-bots/index.mdx

@@ -16,7 +16,7 @@ A verified bot is a bot which has been added to Cloudflare's list of <GlossaryTo
 You can request for your bot to be added to Cloudflare's bots and agents directory by filling out an [online application](https://dash.cloudflare.com/?to=/:account/configurations/verified-bots) in the Cloudflare dashboard.
 
 :::note
-A bot cannot be registered as both a verified bot and a signed agent. Review Cloudflare's [signed bots](/bots/concepts/bot/signed-bots/) to determine how to identify your bot.
+A bot cannot be registered as both a verified bot and a signed agent. Review Cloudflare's [signed bots](/bots/concepts/bot/signed-agents/) to determine how to identify your bot.
 :::
 
 ## Verified bot requirement
@@ -80,6 +80,6 @@ The Verified Bot Categories field is not compatible with legacy Firewall rules.
 | Webhooks                   | `Webhooks`                   | Payment processors, WordPress Integration tools                         |
 | Other                      | `Other`                      |                                                                         |
 
-## Availability
+### Availability
 
 Verified Bot Categories is available on all plans.

src/content/docs/bots/concepts/bot/verified-bots/policy.mdx

@@ -13,39 +13,39 @@ In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" li
 
 ## Bot Policy
 
-### Minimum Traffic
+### Minimum traffic
 
 A bot or proxy must have a minimum amount of traffic for Cloudflare to be able to find it in the sampled data. The minimum traffic should have more than 1,000 requests per day across multiple domains.
 
-### Minimum Zones
+### Minimum zones
 
 Service must be made for a widespread use of zones.
 
 #### Example
 
 A bot crawling one site is not valid.
 
-### Bot Identification
+### Bot identification
 
 The user-agent or message signature with the following requirements:
 
-- Have at least 5 characters.
+- Have at least five characters.
 - Must not contain special characters.
 - Must not include the same user-agent of another verified service.
 
 #### Example
 
-`GoogleBot/1.0` is a valid UA.
+`GoogleBot/1.0` is a valid user-agent.
 
-### Domain Owner Consent
+### Domain owner consent
 
 Domains should only be crawled with the explicit or implicit consent of the zone's owner or terms of use. Search engines crawlers must read the `robots.txt` to exclude paths to crawl from the owner.
 
 #### Example
 
 A tool trying to scalp inventories from different websites might be breaking terms of use while a search engine bot indexing websites but complying with `robots.txt` is a valid service.
 
-### Service Purpose
+### Service purpose
 
 The purpose of the service should be benign or helpful to both the owner of a zone and the users of the service. The service cannot perform any of the following:
 
@@ -58,25 +58,27 @@ The purpose of the service should be benign or helpful to both the owner of a zo
 
 #### Example
 
-Price scraping direct ecommerce competitors is not a valid use case.
+Price scraping direct e-commerce competitors is not a valid use case.
 
-### Crawling Etiquette
+### Crawling etiquette
 
 The crawling etiquette should check `robots.txt` if crawling the whole website, and it should not attempt to crawl sensitive paths.
 
 #### Example
 
 If a search engine crawler skips `robots.txt`, it will be rejected.
 
-### Public Documentation
+### Public documentation
 
 The bot must have publicly documented expected behavior or user-agent format.
 
-## Breach of Policy
+---
+
+## Breach of policy
 
 If any of the requirements to validate are breached, a service will be removed from the global allowlist.
 
-#### Example breaches of policy
+The following are examples of breaches of policy:
 
 - Adding a set of IPs that are not solely used by verified service.
 - The service IPs are breached by an attacker.

src/content/docs/bots/reference/bot-verification/index.mdx

@@ -10,6 +10,6 @@ sidebar:
 
 import { DirectoryListing } from "~/components"
 
-Refer to the following pages for more information on Cloudflare's validation methods for [Verified] and [Signed]() bots.
+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 />

src/content/docs/bots/reference/bot-verification/web-bot-auth.mdx

@@ -9,7 +9,7 @@ sidebar:
 
 import { GlossaryTooltip, Steps } from "~/components"
 
-Web Bot Auth is an authentication method that leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. Web Bot Auth is used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/) and [signed bots](/bots/concepts/bot/signed-bots/).
+Web Bot Auth is an authentication method that leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. Web Bot Auth is used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/) and [signed bots](/bots/concepts/bot/signed-agents/).
 
 It relies on two active IETF drafts: a [directory draft](https://datatracker.ietf.org/doc/html/draft-meunier-http-message-signatures-directory) allowing the crawler to share their public keys, and a [protocol draft](https://datatracker.ietf.org/doc/html/draft-meunier-web-bot-auth-architecture) defining how these keys should be used to attach crawler's identity to HTTP requests.