Refine documentation for clarity and consistency (#22432)

hyperlint-ai[bot] · kodster28 · web-flow · commit 438f421b1053 · 2025-05-14T11:28:40.000-05:00
* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Apply suggestions from code review

---------

Co-authored-by: hyperlint-ai[bot] &lt;154288675+hyperlint-ai[bot]@users.noreply.github.com&gt;
Co-authored-by: Kody Jackson &lt;kody@cloudflare.com&gt;
diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx
@@ -17,9 +17,9 @@ Below you will find answers to our most commonly asked questions. If you cannot
 
 1.1.1.1 is Cloudflare's fast and secure DNS resolver. When you request to visit an application like `cloudflare.com`, your computer needs to know which server to connect you to so that it can load the application. Computers don't know how to do this name to address translation, so they ask a specialized server to do it for them.
 
-This specialized server is called a DNS recursive resolver. The resolver’s job is to find the address for a given name, like `2400:cb00:2048:1::c629:d7a2` for `cloudflare.com`, and return it to the computer that asked for it.
+This specialized server is called a DNS recursive resolver. The resolver's job is to find the address for a given name, like `2400:cb00:2048:1::c629:d7a2` for `cloudflare.com`, and return it to the computer that asked for it.
 
-Computers are configured to talk to specific DNS resolvers, identified by IP address. Usually the configuration is managed by your ISP (like Comcast or AT\&T) if you are on your home or wireless Internet, and by your network administrator if you’re connected to the office Internet. You can also change the configured DNS resolver your computer talks to yourself.
+Computers are configured to talk to specific DNS resolvers, identified by IP address. Usually the configuration is managed by your ISP (like Comcast or AT\&T) if you are on your home or wireless Internet, and by your network administrator if you are connected to the office Internet. You can also change the configured DNS resolver your computer talks to yourself.
 
 
 ## How can I check if my computer / smartphone / tablet is connected to 1.1.1.1?
diff --git a/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx b/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx
@@ -34,7 +34,7 @@ When a request is blocked by guardrails, you will receive a structured error res
   - `"code": 2016`  
   - `"message": "Prompt blocked due to security configurations"`
 
-- **Response blocked**  
+- **Response blocked**
   - `"code": 2017`  
   - `"message": "Response blocked due to security configurations"`
 
diff --git a/src/content/docs/ai-gateway/universal.mdx b/src/content/docs/ai-gateway/universal.mdx
@@ -19,7 +19,7 @@ You can use the Universal endpoint to contact every provider. The payload is exp
 
 - `provider` : the name of the provider you would like to direct this message to. Can be OpenAI, workers-ai, or any of our supported providers.
 - `endpoint`: the pathname of the provider API you’re trying to reach. For example, on OpenAI it can be `chat/completions`, and for Workers AI this might be [`@cf/meta/llama-3.1-8b-instruct`](/workers-ai/models/llama-3.1-8b-instruct/). See more in the sections that are specific to [each provider](/ai-gateway/providers/).
-- `authorization`: the content of the Authorization HTTP Header that should be used when contacting this provider. This usually starts with "Token" or "Bearer".
+- `authorization`: the content of the Authorization HTTP Header that should be used when contacting this provider. This usually starts with 'Token' or 'Bearer'.
 - `query`: the payload as the provider expects it in their official API.
 
 ## cURL example
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
@@ -11,7 +11,7 @@ Cloudflare account analytics lets you access a wide range of aggregated metrics
 
 :::note
 
-For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/). 
+For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
 :::
 
 ***
@@ -32,7 +32,7 @@ Once it loads, the Account Analytics app displays a collection of categorized ch
 
 ## 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:
+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.
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
@@ -7,9 +7,9 @@ title: Cloudflare analytics with Workers
 
 Learn how Cloudflare analytics tracks requests made by [Cloudflare Workers](/workers/).
 
-## What is a subrequest?
+## What is a subrequest
 
-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.
+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.
 
 ***
 
@@ -29,7 +29,7 @@ For a breakdown of subrequest traffic (origin facing traffic), you may go to the
 
 ## FAQ
 
-**Why don’t I have any analytics for Workers?**
+**Why don't I have any analytics for Workers?**
 
 * If you are not currently using Workers (don’t 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
diff --git a/src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx b/src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx
@@ -7,7 +7,7 @@ title: Status codes
 
 :::note
 
-Status Codes analytics by data center is exclusive to the [enterprise level of service](https://www.cloudflare.com/plans/enterprise/contact/). 
+Status Codes analytics by data center is exclusive to the [enterprise level of service](https://www.cloudflare.com/plans/enterprise/contact/).
 :::
 
 Status Codes metrics in the Cloudflare dashboard **Analytics** app provide customers with a deeper insight into the distribution of errors that are occurring on their website per data center. A data center facility is where Cloudflare runs its servers that make up our edge network ([current locations](https://www.cloudflare.com/network/)).
@@ -59,7 +59,7 @@ For more information, refer to [4xx Client Error](/support/troubleshooting/http-
 - `522` - Our edge could not establish a TCP connection to the origin server.
 - `523` - Origin server is unreachable (for example, the origin IP changed but DNS was not updated, or due to network issues between our edge and the origin).
 - `524` - Our edge established a TCP connection, but the origin did not reply with a HTTP response before the connection timed out.
-- `525` - This error indicates that the SSL handshake between Cloudflare and the origin web server failed, either due to a network issue or a certificare issue at the origin.
+- `525` - This error indicates that the SSL handshake between Cloudflare and the origin web server failed, either due to a network issue or a certificate issue at the origin.
 - `526` - The certificate configured at the origin is not valid.
 
 For more information, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/).
diff --git a/src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx b/src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx
@@ -4,7 +4,7 @@ source: https://support.cloudflare.com/hc/en-us/articles/204191238-What-are-the-
 title: Threat types
 ---
 
-Cloudflare classifies the threats that it blocks or challenges. To help you understand more about your site’s traffic, the “Type of Threats Mitigated” metric on the analytics page measures threats blocked or challenged by the following categories:
+Cloudflare classifies the threats that it blocks or challenges. To help you understand more about your site’s traffic, the 'Type of Threats Mitigated' metric on the analytics page measures threats blocked or challenged by the following categories:
 
 ## Bad browser
 
@@ -14,7 +14,7 @@ Cloudflare's [Browser Integrity Check](/waf/tools/browser-integrity-check/) look
 
 ## Blocked hotlink
 
-[Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/) ensures that other sites cannot use your bandwidth by building pages that link to images hosted on your origin server. This feature can be turned on and off by Cloudflare’s customers.
+[Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/) ensures that other sites cannot use your bandwidth by building pages that link to images hosted on your origin server. This feature can be turned on and off by Cloudflare's customers.
 
 ## Human challenged
 
@@ -52,7 +52,7 @@ A /24 IP range that was blocked based on the [user configuration](/waf/tools/ip-
 
 ## New Challenge (user)
 
-[Challenge](/cloudflare-challenges/) based on user configurations set for visitor’s IP in either WAF managed rules or custom rules, configured in **Security** > **WAF**.
+[Challenge](/cloudflare-challenges/) based on user configurations set for visitor's IP in either WAF managed rules or custom rules, configured in **Security** > **WAF**.
 
 ## Challenge error
 
diff --git a/src/content/docs/analytics/account-and-zone-analytics/total-threats-stopped.mdx b/src/content/docs/analytics/account-and-zone-analytics/total-threats-stopped.mdx
@@ -4,7 +4,7 @@ source: https://support.cloudflare.com/hc/en-us/articles/204964927-How-does-Clou
 title: Total threats stopped
 ---
 
-Total Threats Stopped measures the number of “suspicious” and “bad” requests that were aimed at your site. Requests receive these labels as they enter Cloudflare’s network:
+Total Threats Stopped measures the number of 'suspicious' and 'bad' requests that were aimed at your site. Requests receive these labels as they enter Cloudflare's network:
 
 - **Legitimate:** Request passed directly to your site.
 - **Suspicious:** Request has been challenged with a [Cloudflare challenge](/cloudflare-challenges/).
diff --git a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
@@ -39,7 +39,7 @@ Once it loads, you can find tabs for **Traffic**, **Security**, **Performance**,
 This section outlines the metrics available under each Analytics app tab. Before proceeding, note that each tab may contain:
 
 * One or more panels to further categorize the underlying metrics.
-* A dropdown (on the panel’s top right) to filter metrics for a specific time period. The time period you can select may vary based on the Cloudflare plan that your domain is associated with.
+* A dropdown (on the panel's top right) to filter metrics for a specific time period. The time period you can select may vary based on the Cloudflare plan that your domain is associated with.
 
 Below is a summary of each Analytics app tab.
 
@@ -60,7 +60,7 @@ Privacy-first Web Traffic Analytics are available on the Pro, Business,
 and Enterprise plans.
 :::
 
-Analytics are based on Cloudflare’s edge logs, with no need for third party scripts or trackers. The Traffic tab features the following metrics:
+Analytics are based on Cloudflare's edge logs, with no need for third party scripts or trackers. The Traffic tab features the following metrics:
 
 * **Requests** - An HTTP request. A typical page view requires many requests. If you are using Cloudflare Workers, subrequests data will not be visible in zone Traffic Analytics. Instead, you can find subrequests analytics under the **Workers & Pages** tab in the **Overview** section. Refer to [Worker Analytics](/analytics/account-and-zone-analytics/analytics-with-workers/#worker-analytics) for more information.
 * **Data Transfer** - Total HTTP data transferred in responses.
