Improve clarity and consistency in documentation

src/content/docs/1.1.1.1/faq.mdx

@@ -15,7 +15,7 @@ Below you will find answers to our most commonly asked questions. If you cannot
 
 ## What is 1.1.1.1?
 
-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.
+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 do not 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.
 

src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx

@@ -31,7 +31,7 @@ After enabling Guardrails, you can monitor results through **AI Gateway Logs** i
 When a request is blocked by guardrails, you will receive a structured error response. These indicate whether the issue occurred with the prompt or the model response. Use error codes to differentiate between prompt versus response violations. 
 
 - **Prompt blocked**
-  - `"code": 2016`  
+  - `"code": 2016`
   - `"message": "Prompt blocked due to security configurations"`
 
 - **Response blocked**

src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx

@@ -29,9 +29,9 @@ 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 do I not 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 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
 
 **Will this impact billing?** 

src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx

@@ -12,7 +12,7 @@ Status Codes analytics by data center is exclusive to the [enterprise level of s
 
 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/)).
 
-HTTP status codes that appear in a response passing through our edge are displayed in analytics. 
+HTTP status codes that appear in a response passing through our edge are displayed in analytics.
 
 The `Origin Status Code` can help you investigate issues on your origin. If your origin returns a `5xx` error, Cloudflare's edge will forward this error to the end user. Comparing the `Edge Status Code` and `Origin Status Code` can help determine whether the issue is occurring on your origin or on the Cloudflare edge.
 

src/content/docs/analytics/analytics-integrations/looker.mdx

@@ -26,7 +26,7 @@ Before sending your Cloudflare log data to Looker, make sure that you:
 :::note[Note]
 
 
-Cloudflare logs are HTTP/HTTPS request logs in JSON format and are gathered from our 200+ data centers globally. By default, timestamps are returned as Unix nanosecond integers. We recommend using the RFC 3339 format for sending logs to Looker.
+Cloudflare logs are HTTP/HTTPS request logs in JSON format and are gathered from our 200+ data centers globally. By default, timestamps are returned as UNIX nanosecond integers. We recommend using the RFC 3339 format for sending logs to Looker.
 
 
 :::
@@ -147,8 +147,8 @@ Available Filters:
 
 With the following pre-set filter values in the Looker dashboards all workers subrequests and client request method PURGE are excluded from the calculations:
 
-* **WorkerSubrequet** set to value *False*
+* **WorkerSubrequest** set to value *False*
 
-* **ClientRequestMethod** doesn’t equal to *PURGE*
+* **ClientRequestMethod** doesn't equal to *PURGE*
 
 You can always adjust your default filters values according to your needs.

src/content/docs/analytics/analytics-integrations/splunk.mdx

@@ -41,7 +41,7 @@ To install the [Cloudflare App for Splunk](https://splunkbase.splunk.com/app/450
 
    1. Open the setup screen by clicking the **Settings** dropdown, then click **Indexes**.
    2. Select **New Index**. Note that the **Indexes** page also gives you the status of all your existing indexes so that you can see whether you're about to use up your licensed amount of space.
-   3. Name the index **cloudflare**, which is the default index that the Cloudflare App will use.
+   3. Name the index **Cloudflare**, which is the default index that the Cloudflare App will use.
 
 7. Set up the HTTP Event Collector (HEC) on Splunk. To create an HEC: