diff --git a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx index c96b438f1cf7b5..a74e7e033eca2a 100644 --- a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx +++ b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx @@ -37,7 +37,7 @@ To access this content, you must verify your AI crawler. Ensure your AI crawler identifies itself with the required headers for Web Bot Auth. -Follow the steps found in [Web Both Auth](/bots/concepts/bot/verified-bots/web-bot-auth/). +Follow the steps found in [Web Bot Auth](/bots/concepts/bot/verified-bots/web-bot-auth/). ## 2. Follow verified bot policy diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx index 487911efbaf43f..c905f89d042bbb 100644 --- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx +++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx @@ -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 diff --git a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference.mdx b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference.mdx index 0a7f42c92fe995..05cca3cc99bde2 100644 --- a/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference.mdx +++ b/src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/node-reference.mdx @@ -72,7 +72,7 @@ The sample rate is 1/1,000 packets. ### `advancedDnsProtectionNetworkAnalyticsAdaptiveGroups` -This node is only available to Magic Transit customers. Provides metadata about DNS-based DDoS attacks mitigated by Cloudflare's [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) system. +This node is only available to Magic Transit customers. Provides metadata about DNS-based DDoS attacks mitigated by Cloudflare's [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/) system. Samples include information about the following DNS header fields: 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 fdd3264b42cc13..8ba7beee5f8660 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 @@ -103,4 +103,4 @@ Rather than filter by `cfRayId`, you may also [filter](/analytics/graphql-api/fe 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-firewall-events.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx index 9a9c75e6e4a08c..e3f91a7c24c75a 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-firewall-events.mdx @@ -6,7 +6,7 @@ title: Querying Firewall Events with GraphQL In this example, we are going to use the GraphQL Analytics API to query for Firewall Events over a specified time period. -The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace ``, ``, and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace ``, ``, and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -183,4 +183,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^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-firewall-ids-samples.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx index 00b8a116764462..2ea435683ab98a 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-ids-samples.mdx @@ -6,7 +6,7 @@ title: Querying Magic Firewall Intrusion Detection System (IDS) samples with Gra In this example, we are going to use the GraphQL Analytics API to query for IDS samples over a specified time period. -The following API call will request IDS samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your account tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request IDS samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your account tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -66,13 +66,13 @@ https://api.cloudflare.com/client/v4/graphql \ #=> { #=> sum: { bits: 327680, packets: 16384 }, #=> dimensions: { -#=> datetimeFiveMinute: '2021-05-12T22:00-00:00' + datetimeFiveMinutes: '2021-05-12T22:00-00:00' #=> } #=> }, #=> { #=> sum: { bits: 360448, packets: 8192 }, #=> dimensions: { -#=> datetimeFiveMinute: '2021-05-12T22:05-00:00' + datetimeFiveMinutes: '2021-05-12T22:05-00:00' #=> } #=> }, #=> { @@ -102,4 +102,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^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-firewall-samples.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx index 598181b891a80c..e70c6025917fb2 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-magic-firewall-samples.mdx @@ -6,7 +6,7 @@ title: Querying Magic Firewall Samples with GraphQL In this example, we are going to use the GraphQL Analytics API to query for Magic Firewall Samples over a specified time period. -The following API call will request Magic Firewall Samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. +The following API call will request Magic Firewall Samples over a one hour period, and output the requested fields. Be sure to replace `` and ``[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. ## API Call @@ -107,4 +107,4 @@ https://api.cloudflare.com/client/v4/graphql \ #=> } ``` -[^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.