Enhance documentation for analytics integrations (cloudflare#22466)

* 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] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: Kody Jackson <[email protected]>

Author: 2 people

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

@@ -38,7 +38,7 @@ When a request is blocked by guardrails, you will receive a structured error res
   - `"code": 2017`
   - `"message": "Response blocked due to security configurations"`
 
-You should catch these errors in your application logic and implement error handling accordingly. 
+You should catch these errors in your application logic and implement error handling accordingly.
 
 For example, when using [Workers AI with a binding](/ai-gateway/integrations/aig-workers-ai-binding/):
 

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

@@ -12,7 +12,7 @@ This tutorial explains how to analyze [Cloudflare Logs](https://www.cloudflare.c
 
 If you have not used Cloudflare Logs before, refer to the [Logs documentation](/logs/) for more details. Contact your Cloudflare Customer Account Team to enable logs for your account.
 
-This tutorial uses Cloudflare Logpush to send logs to [Google Cloud Storage Bucket](https://cloud.google.com/storage) and Cloud Function and then import them into Google Big Query.
+This tutorial uses Cloudflare Logpush to send logs to [Google Cloud Storage Bucket](https://cloud.google.com/storage) and Cloud Function and then import them into Google BigQuery.
 
 ### Prerequisites
 

src/content/docs/analytics/graphql-api/index.mdx

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-The GraphQL Analytics API provides data regarding HTTP requests passing through Cloudflare’s network, as well as data from specific products, such as Firewall or Load Balancing. Network Analytics users also have access to packet-level data. Use the GraphQL Analytics API to select specific datasets and metrics of interest, filter and aggregate the data along various dimensions, and integrate the results with other applications.
+The GraphQL Analytics API provides data regarding HTTP requests passing through Cloudflare's network, as well as data from specific products, such as Firewall or Load Balancing. Network Analytics users also have access to packet-level data. Use the GraphQL Analytics API to select specific datasets and metrics of interest, filter and aggregate the data along various dimensions, and integrate the results with other applications.
 
 The basis of the API is the [GraphQL framework](https://graphql.org/), created and open-sourced by Facebook. There is an active developer community for GraphQL and powerful clients for running queries, which makes it easy to get started. GraphQL is especially useful for building visualizations and powers the analytics in the Cloudflare dashboard.
 
@@ -28,4 +28,4 @@ We are using [GraphiQL](https://github.com/skevy/graphiql-app) for our example G
 
 ## Limitations
 
-The purpose of the GraphQL API is to provide aggregated analytics about various Cloudflare products. These datasets should not be used as a measure for usage that Cloudflare uses for billing purposes. Billable traffic [excludes things like DDoS traffic](https://blog.cloudflare.com/unmetered-mitigation), while GraphQL is a measure of overall consumption/usage, so it will include all measurable traffic.
+The purpose of the GraphQL API is to provide aggregated analytics about various Cloudflare products. These datasets should not be used as a measure for usage that Cloudflare uses for billing purposes. Billable traffic [excludes things like DDoS traffic](https://blog.cloudflare.com/unmetered-mitigation), while GraphQL is a measure of overall consumption/usage, so it will include all measurable traffic.

src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx

@@ -12,7 +12,7 @@ import { Render } from "~/components"
 In early 2020, Cloudflare released the first version of the Network Analytics dashboard and its corresponding API. The second version (Network Analytics v2) was made available on 2021-09-13.
 
 :::caution
- <Render file="network-analytics-v1-deprecation" /> 
+ <Render file="network-analytics-v1-deprecation" />
 :::
 
 ## Before you start
@@ -67,7 +67,7 @@ For reference information on NAv2 nodes, refer to the [NAv2 node reference](/ana
 
 :::note[Obtaining data for ingress traffic only]
 
-All the NAv2 `*AnalyticsAdaptiveGroups` nodes include data for ingress and egress traffic. To obtain data about ingress traffic only, include `direction: "ingress"` in your [GraphQL query filter](/analytics/graphql-api/features/filtering/). 
+All the NAv2 `*AnalyticsAdaptiveGroups` nodes include data for ingress and egress traffic. To obtain data about ingress traffic only, include `direction: "ingress"` in your [GraphQL query filter](/analytics/graphql-api/features/filtering/).
 :::
 
 ## Schema comparison