From 72d12276ea80b57feefbab271bbb4051b81c5093 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:30:37 +0000 Subject: [PATCH 01/15] Hyperlint Automation Fix --- src/content/docs/1.1.1.1/faq.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index a79c373a4b4ddd6..a426bf764bc3cc8 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/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 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. @@ -28,15 +28,15 @@ Computers are configured to talk to specific DNS resolvers, identified by IP add Visit [1.1.1.1/help](https://one.one.one.one/help) to make sure your system is connected to 1.1.1.1 and that it is working. -## What do DNS resolvers do? +## What do DNS resolvers do -DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website your are looking for. +DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website you're looking for. Every resolver knows how to find the invisible `.` at the end of domain names (for example, `cloudflare.com.`). There are [hundreds of root servers](http://www.root-servers.org/) all over the world that host the `.` file, and resolvers are [hard coded to know the IP addresses](http://www.internic.net/domain/named.root) of those servers. Cloudflare itself hosts [that file](http://www.internic.net/domain/root.zone) on all of its servers around the world through a [partnership with ISC](https://blog.cloudflare.com/f-root/). The resolver asks one of the root servers where to find the next link in the chain — the top-level domain (abbreviated to TLD) or domain ending. An example of a TLD is `.com` or `.org`. Luckily, the root servers store the locations of all the TLD servers, so they can return which IP address the DNS resolver should go ask next. -The resolver then asks the TLD’s servers where it can find the domain it is looking for. For example, a resolver might ask `.com` where to find `cloudflare.com`. TLDs host a file containing the location of every domain using the TLD. +The resolver then asks the TLD's servers where it can find the domain it is looking for. For example, a resolver might ask `.com` where to find `cloudflare.com`. TLDs host a file containing the location of every domain using the TLD. Once the resolver has the final IP address, it returns the answer to the computer that asked. @@ -52,7 +52,7 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec 1.1.1.1 is a DNSSEC validating resolver. 1.1.1.1 sends the `DO` (`DNSSEC OK`) bit on every query to convey to the authoritative server that it wishes to receive signed answers if available. 1.1.1.1 supports the signature algorithms specified in [Supported DNSKEY signature algorithms](/1.1.1.1/encryption/dnskey/). -## ​Does 1.1.1.1 send EDNS Client Subnet header? +## ​Does 1.1.1.1 send EDNS Client Subnet header 1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet (ECS) header to authoritative servers. The exception is the single Akamai debug domain `whoami.ds.akahelp.net` to aid in cross-provider debugging. However, Cloudflare does not send ECS to any of Akamai's production domains, such as `akamaihd.net` or similar. @@ -62,22 +62,22 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec 1.1.1.1 has full IPv6 support. -## What is Purge Cache? +## What is Purge Cache 1.1.1.1's Purge Cache tool allows you to refresh 1.1.1.1's DNS cache for domain names. To refresh the cache for a domain name, visit the [Purge Cache page](https://one.one.one.one/purge-cache/). -## What is query name minimization? +## What is query name minimization -Cloudflare minimizes privacy leakage by only sending minimal query name to authoritative DNS servers. For example, if a client is looking for foo.bar.example.com, the only part of the query 1.1.1.1 discloses to .com is that we want to know who’s responsible for example.com and the zone internals stay hidden. +Cloudflare minimizes privacy leakage by only sending minimal query name to authoritative DNS servers. For example, if a client is looking for foo.bar.example.com, the only part of the query 1.1.1.1 discloses to .com is that we want to know who's responsible for example.com and the zone internals stay hidden. -## What are root hints? +## What are root hints For decreased latency, reduced privacy leakage of queries and lower load on the DNS system, 1.1.1.1 upstreams to [locally hosted root zone files](https://blog.cloudflare.com/f-root/). -## Can IPs used by 1.1.1.1 be allowlisted? +## Can IPs used by 1.1.1.1 be allowlisted Authoritative DNS providers may want to allowlist IP's 1.1.1.1 uses to query upstream DNS providers. The comprehensive list of IP's to allowlist is available at [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/). From 6ec1b1c47de6c9e84a4c4e6a23fdbd1e71db3061 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:30:46 +0000 Subject: [PATCH 02/15] Hyperlint Automation Fix From ce15d5bac295c6822adec3b00c3ab66d80739c09 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:30:49 +0000 Subject: [PATCH 03/15] Hyperlint Automation Fix --- src/content/docs/agents/api-reference/rag.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/agents/api-reference/rag.mdx b/src/content/docs/agents/api-reference/rag.mdx index b29014c20452f39..52900437c267d3f 100644 --- a/src/content/docs/agents/api-reference/rag.mdx +++ b/src/content/docs/agents/api-reference/rag.mdx @@ -22,7 +22,7 @@ If you're brand-new to vector databases and Vectorize, visit the [Vectorize tuto You can query a vector index (or indexes) from any method on your Agent: any Vectorize index you attach is available on `this.env` within your Agent. If you've [associated metadata](/vectorize/best-practices/insert-vectors/#metadata) with your vectors that maps back to data stored in your Agent, you can then look up the data directly within your Agent using `this.sql`. -Here's an example of how to give an Agent retrieval capabilties: +Here's an example of how to give an Agent retrieval capabilities: From 935972478cf806d01aa29070a503509a37b14da8 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:30:52 +0000 Subject: [PATCH 04/15] Hyperlint Automation Fix --- src/content/docs/agents/api-reference/run-workflows.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/agents/api-reference/run-workflows.mdx b/src/content/docs/agents/api-reference/run-workflows.mdx index 442ba327df4ca26..8653145a76ed314 100644 --- a/src/content/docs/agents/api-reference/run-workflows.mdx +++ b/src/content/docs/agents/api-reference/run-workflows.mdx @@ -97,7 +97,7 @@ You can also call a Workflow that is defined in a different Workers script from // Required: "name": "EMAIL_WORKFLOW", "class_name": "MyWorkflow", - // Optional: set tthe script_name field if your Workflow is defined in a + // Optional: set the script_name field if your Workflow is defined in a // different project from your Agent "script_name": "email-workflows" } From 9b76731ed7d9de0bcc2fe12234aeeefbc5b3e4bb Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:05 +0000 Subject: [PATCH 05/15] Hyperlint Automation Fix --- src/content/docs/agents/api-reference/using-ai-models.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/agents/api-reference/using-ai-models.mdx b/src/content/docs/agents/api-reference/using-ai-models.mdx index ee5950231f75afc..c9a60db00a46857 100644 --- a/src/content/docs/agents/api-reference/using-ai-models.mdx +++ b/src/content/docs/agents/api-reference/using-ai-models.mdx @@ -32,7 +32,7 @@ Importantly, Agents can call AI models on their own — autonomously — and can Modern [reasoning models](https://platform.openai.com/docs/guides/reasoning) or "thinking" model can take some time to both generate a response _and_ stream the response back to the client. -Instead of buffering the entire response, or risking the client disconecting, you can stream the response back to the client by using the [WebSocket API](/agents/api-reference/websockets/). +Instead of buffering the entire response, or risking the client disconnecting, you can stream the response back to the client by using the [WebSocket API](/agents/api-reference/websockets/). @@ -121,7 +121,7 @@ export class MyAgent extends Agent { -Your wrangler configuration will need an `ai` binding added: +Your Wrangler configuration will need an `ai` binding added: @@ -174,7 +174,7 @@ export class MyAgent extends Agent { -Your wrangler configuration will need an `ai` binding added. This is shared across both Workers AI and AI Gateway. +Your Wrangler configuration will need an `ai` binding added. This is shared across both Workers AI and AI Gateway. ```toml From b8f620912be059ea3c77c16586ed053a101190c6 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:16 +0000 Subject: [PATCH 06/15] Hyperlint Automation Fix --- .../docs/agents/model-context-protocol/authorization.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/agents/model-context-protocol/authorization.mdx b/src/content/docs/agents/model-context-protocol/authorization.mdx index eced8674c664697..1392cd370296164 100644 --- a/src/content/docs/agents/model-context-protocol/authorization.mdx +++ b/src/content/docs/agents/model-context-protocol/authorization.mdx @@ -124,7 +124,7 @@ Read the docs for the [Workers oAuth Provider Library](https://github.com/cloudf ### (3) Bring your own OAuth Provider -If your application already implements an Oauth Provider itself, or you use [Stytch](https://stytch.com/), [Auth0](https://auth0.com/), [WorkOS](https://workos.com/), or authorization-as-a-service provider, you can use this in the same way that you would use a third-party OAuth provider, described above in (2). +If your application already implements an OAuth Provider itself, or you use [Stytch](https://stytch.com/), [Auth0](https://auth0.com/), [WorkOS](https://workos.com/), or authorization-as-a-service provider, you can use this in the same way that you would use a third-party OAuth provider, described above in (2). You can use the auth provider to: - Allow users to authenticate to your MCP server through email, social logins, SSO (single sign-on), and MFA (multi-factor authentication). From ef333cbe637feab09cf97aafcc234cdbe497d219 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:20 +0000 Subject: [PATCH 07/15] Hyperlint Automation Fix --- src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx b/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx index ca721bace853af6..bf202fc0c4dacc0 100644 --- a/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx +++ b/src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx @@ -30,7 +30,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** +- **Prompt blocked** - `"code": 2016` - `"message": "Prompt blocked due to security configurations"` From b62a4824db7eb5e21c14336542fa459e81c94c8b Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:25 +0000 Subject: [PATCH 08/15] Hyperlint Automation Fix --- src/content/docs/ai-gateway/guardrails/usage-considerations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/ai-gateway/guardrails/usage-considerations.mdx b/src/content/docs/ai-gateway/guardrails/usage-considerations.mdx index f1510e8172491f4..60a8ef82cba26d7 100644 --- a/src/content/docs/ai-gateway/guardrails/usage-considerations.mdx +++ b/src/content/docs/ai-gateway/guardrails/usage-considerations.mdx @@ -14,7 +14,7 @@ Since Guardrails runs on Workers AI, enabling it incurs usage on Workers AI. You - **Model availability**: If at least one hazard category is set to `block`, but AI Gateway is unable to receive a response from Workers AI, the request will be blocked. Conversely, if a hazard category is set to `flag` and AI Gateway cannot obtain a response from Workers AI, the request will proceed without evaluation. This approach prioritizes availability, allowing requests to continue even when content evaluation is not possible. - **Latency impact**: Enabling Guardrails adds some latency. Enabling Guardrails introduces additional latency to requests. Typically, evaluations using Llama Guard 3 8B on Workers AI add approximately 500 milliseconds per request. However, larger requests may experience increased latency, though this increase is not linear. Consider this when balancing safety and performance. - **Handling long content**: When evaluating long prompts or responses, Guardrails automatically segments the content into smaller chunks, processing each through separate Guardrail requests. This approach ensures comprehensive moderation but may result in increased latency for longer inputs. -- **Supported languages**: Llama Guard 3.3 8B supports content safety classification in the following languages: English, French, German, Hindi, Italian, Portuguese, Spanish, and Thai. +- **Supported languages**: Llama Guard 3.3 8B supports content safety classification in the following languages: English, French, German, Hindi, Italian, Portuguese, Spanish, and Thai. :::note From 8b588758e7d9dc8ca7003e5be4a487766cde0767 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:30 +0000 Subject: [PATCH 09/15] Hyperlint Automation Fix --- src/content/docs/ai-gateway/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/ai-gateway/index.mdx b/src/content/docs/ai-gateway/index.mdx index f75d406618f0cd3..cc458a347f62d6d 100644 --- a/src/content/docs/ai-gateway/index.mdx +++ b/src/content/docs/ai-gateway/index.mdx @@ -79,7 +79,7 @@ Run machine learning models, powered by serverless GPUs, on Cloudflare’s globa -Build full-stack AI applications with Vectorize, Cloudflare’s vector database. Adding Vectorize enables you to perform tasks such as semantic search, recommendations, anomaly detection or can be used to provide context and memory to an LLM. +Build full-stack AI applications with Vectorize, Cloudflare's vector database. Adding Vectorize enables you to perform tasks such as semantic search, recommendations, anomaly detection or can be used to provide context and memory to an LLM. From 8869916a0dbbe4e49bf52e17aa7687891ea45c5a Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Wed, 14 May 2025 13:31:34 +0000 Subject: [PATCH 10/15] Hyperlint Automation Fix --- src/content/docs/ai-gateway/observability/logging/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/ai-gateway/observability/logging/index.mdx b/src/content/docs/ai-gateway/observability/logging/index.mdx index 007c534f96dc7fd..6a5ff291dfd599b 100644 --- a/src/content/docs/ai-gateway/observability/logging/index.mdx +++ b/src/content/docs/ai-gateway/observability/logging/index.mdx @@ -51,7 +51,7 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai/chat/ To manage your log storage effectively, you can: - Set Storage Limits: Configure a limit on the number of logs stored per gateway in your gateway settings to ensure you only pay for what you need. -- Enable Automatic Log Deletion: Activate the Automatic Log Deletion feature in your gateway settings to automatically delete the oldest logs once the log limit you’ve set or the default storage limit of 10 million logs is reached. This ensures new logs are always saved without manual intervention. +- Enable Automatic Log Deletion: Activate the Automatic Log Deletion feature in your gateway settings to automatically delete the oldest logs once the log limit you've set or the default storage limit of 10 million logs is reached. This ensures new logs are always saved without manual intervention. ## How to delete logs From ebe93cfd11a57708cde61485b4715b6ebd993e60 Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Wed, 14 May 2025 08:51:09 -0500 Subject: [PATCH 11/15] Update src/content/docs/1.1.1.1/faq.mdx --- src/content/docs/1.1.1.1/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index a426bf764bc3cc8..4f8aabae17c37c2 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -30,7 +30,7 @@ Visit [1.1.1.1/help](https://one.one.one.one/help) to make sure your system is c ## What do DNS resolvers do -DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website you're looking for. +DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website you are looking for. Every resolver knows how to find the invisible `.` at the end of domain names (for example, `cloudflare.com.`). There are [hundreds of root servers](http://www.root-servers.org/) all over the world that host the `.` file, and resolvers are [hard coded to know the IP addresses](http://www.internic.net/domain/named.root) of those servers. Cloudflare itself hosts [that file](http://www.internic.net/domain/root.zone) on all of its servers around the world through a [partnership with ISC](https://blog.cloudflare.com/f-root/). From 11c49fbe76a3d70ac299bfa0ea77a8dfd618e295 Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Wed, 14 May 2025 08:51:30 -0500 Subject: [PATCH 12/15] Update src/content/docs/1.1.1.1/faq.mdx --- src/content/docs/1.1.1.1/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index 4f8aabae17c37c2..5260102efd9ea36 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -28,7 +28,7 @@ Computers are configured to talk to specific DNS resolvers, identified by IP add Visit [1.1.1.1/help](https://one.one.one.one/help) to make sure your system is connected to 1.1.1.1 and that it is working. -## What do DNS resolvers do +## What do DNS resolvers do? DNS resolvers are like address books for the Internet. They translate the name of places to addresses so that your browser can figure out how to get there. DNS resolvers do this by working backwards from the top until they find the website you are looking for. From 894c1fe5fb65ab0ea0a49bbe5744426e518fe8f4 Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Wed, 14 May 2025 08:51:49 -0500 Subject: [PATCH 13/15] Update src/content/docs/1.1.1.1/faq.mdx --- src/content/docs/1.1.1.1/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index 5260102efd9ea36..b690822ce02367b 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -52,7 +52,7 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec 1.1.1.1 is a DNSSEC validating resolver. 1.1.1.1 sends the `DO` (`DNSSEC OK`) bit on every query to convey to the authoritative server that it wishes to receive signed answers if available. 1.1.1.1 supports the signature algorithms specified in [Supported DNSKEY signature algorithms](/1.1.1.1/encryption/dnskey/). -## ​Does 1.1.1.1 send EDNS Client Subnet header +## ​Does 1.1.1.1 send EDNS Client Subnet header? 1.1.1.1 is a privacy centric resolver so it does not send any client IP information and does not send the EDNS Client Subnet (ECS) header to authoritative servers. The exception is the single Akamai debug domain `whoami.ds.akahelp.net` to aid in cross-provider debugging. However, Cloudflare does not send ECS to any of Akamai's production domains, such as `akamaihd.net` or similar. From 28347ed02f77f2daca1e9b0996ec976024a7e992 Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Wed, 14 May 2025 08:52:29 -0500 Subject: [PATCH 14/15] Apply suggestions from code review --- src/content/docs/1.1.1.1/faq.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index b690822ce02367b..56cf923e3cfed66 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -68,16 +68,16 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec 1.1.1.1's Purge Cache tool allows you to refresh 1.1.1.1's DNS cache for domain names. To refresh the cache for a domain name, visit the [Purge Cache page](https://one.one.one.one/purge-cache/). -## What is query name minimization +## What is query name minimization? Cloudflare minimizes privacy leakage by only sending minimal query name to authoritative DNS servers. For example, if a client is looking for foo.bar.example.com, the only part of the query 1.1.1.1 discloses to .com is that we want to know who's responsible for example.com and the zone internals stay hidden. -## What are root hints +## What are root hints? For decreased latency, reduced privacy leakage of queries and lower load on the DNS system, 1.1.1.1 upstreams to [locally hosted root zone files](https://blog.cloudflare.com/f-root/). -## Can IPs used by 1.1.1.1 be allowlisted +## Can IPs used by 1.1.1.1 be allowlisted? Authoritative DNS providers may want to allowlist IP's 1.1.1.1 uses to query upstream DNS providers. The comprehensive list of IP's to allowlist is available at [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/). From 853d03895b455f0d6363f71f7917f3ef18d6563f Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Wed, 14 May 2025 09:08:46 -0500 Subject: [PATCH 15/15] Update src/content/docs/1.1.1.1/faq.mdx --- src/content/docs/1.1.1.1/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index 56cf923e3cfed66..822b6830c8f4a72 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -62,7 +62,7 @@ Cloudflare [stopped supporting the ANY query](https://blog.cloudflare.com/deprec 1.1.1.1 has full IPv6 support. -## What is Purge Cache +## What is Purge Cache? 1.1.1.1's Purge Cache tool allows you to refresh 1.1.1.1's DNS cache for domain names. To refresh the cache for a domain name, visit the [Purge Cache page](https://one.one.one.one/purge-cache/).