diff --git a/src/content/docs/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json.mdx b/src/content/docs/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json.mdx index b8105fa7fb448c..d37186cc8ff862 100644 --- a/src/content/docs/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json.mdx +++ b/src/content/docs/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json.mdx @@ -83,7 +83,7 @@ The following tables have more information on each response field. | `AD` | If true, it means that every record in the answer was verified with DNSSEC. | | `CD` | If true, the client asked to disable DNSSEC validation. In this case, Cloudflare will still fetch the DNSSEC-related records, but it will not attempt to validate the records. | | `Question: name` | The record name requested. | -| `Question: type` | The type of DNS record requested. These are defined here: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4). | +| `Question: type` | The type of DNS record requested. These are defined here: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4). | | `Answer: name` | The record owner. | | `Answer: type` | The type of DNS record. These are defined here: [https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4). | | `Answer: TTL` | The number of seconds the answer can be stored in cache before it is considered stale. | diff --git a/src/content/docs/1.1.1.1/faq.mdx b/src/content/docs/1.1.1.1/faq.mdx index a79c373a4b4ddd..c495693bd14046 100644 --- a/src/content/docs/1.1.1.1/faq.mdx +++ b/src/content/docs/1.1.1.1/faq.mdx @@ -17,7 +17,7 @@ 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. @@ -28,19 +28,19 @@ 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. -This whole system is called the [Domain Name System (DNS)](https://www.cloudflare.com/learning/dns/what-is-dns/). This system includes the servers that host the information (called [authoritative DNS](https://www.cloudflare.com/learning/dns/dns-server-types/)) and the servers that seek the information (the DNS resolvers). +The Domain Name System (DNS) is a system that includes the servers hosting the information (called [authoritative DNS](https://www.cloudflare.com/learning/dns/dns-server-types/)) and the servers seeking the information (the DNS resolvers). ## Does 1.1.1.1 support ANY? @@ -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/). diff --git a/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx b/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx index a878df9d3ceb95..44d4c5a409454e 100644 --- a/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx +++ b/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx @@ -42,7 +42,7 @@ slug: 1.1.1.1/infrastructure/extended-dns-error-codes 3 Stale Answer EDE: 3 (Stale Answer) - This is a silent error. It notifies that the DNS resolver could only return stale data. If the issue persists reach out on the 1.1.1.1 community forum. + This error indicates that the DNS resolver could only return stale data. If the issue persists reach out on the 1.1.1.1 community forum. 6 diff --git a/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx b/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx index bfa146c3ba2331..c3409b8c4d233b 100644 --- a/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx +++ b/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx @@ -16,7 +16,7 @@ The 1.1.1.1 resolver was designed with a privacy-first approach. Refer to our [d ## Configuring 1.1.1.1 -There are multiple ways to use 1.1.1.1 as an operator: +Multiple methods exist to use 1.1.1.1 as an operator: * Including a [DNS over HTTPS](/1.1.1.1/encryption/dns-over-https/) or [DNS over TLS](/1.1.1.1/encryption/dns-over-tls/) proxy on end-user routers or devices (best for privacy). * Pushing 1.1.1.1 to devices via DHCP/PPP within an operator network (recommended; most practical). diff --git a/src/content/docs/agents/api-reference/browse-the-web.mdx b/src/content/docs/agents/api-reference/browse-the-web.mdx index 689b856339b5e3..47df80bc29c7a0 100644 --- a/src/content/docs/agents/api-reference/browse-the-web.mdx +++ b/src/content/docs/agents/api-reference/browse-the-web.mdx @@ -60,7 +60,7 @@ export class MyAgent extends Agent { -You'll also need to add install the `@cloudflare/puppeteer` package and add the following to the wrangler configuration of your Agent: +You'll also need to add install the `@cloudflare/puppeteer` package and add the following to the Wrangler configuration of your Agent: ```sh npm install @cloudflare/puppeteer --save-dev diff --git a/src/content/docs/agents/api-reference/configuration.mdx b/src/content/docs/agents/api-reference/configuration.mdx index 79426eac85ff2c..28080ec81bc30f 100644 --- a/src/content/docs/agents/api-reference/configuration.mdx +++ b/src/content/docs/agents/api-reference/configuration.mdx @@ -7,7 +7,7 @@ sidebar: import { MetaInfo, Render, Type, WranglerConfig } from "~/components"; -An Agent is configured like any other Cloudflare Workers project, and uses [a wrangler configuration](/workers/wrangler/configuration/) file to define where your code is and what services (bindings) it will use. +An Agent is configured like any other Cloudflare Workers project, and uses [a Wrangler configuration](/workers/wrangler/configuration/) file to define where your code is and what services (bindings) it will use. ### Project structure diff --git a/src/content/docs/agents/api-reference/rag.mdx b/src/content/docs/agents/api-reference/rag.mdx index b29014c20452f3..52900437c267d3 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: diff --git a/src/content/docs/agents/api-reference/run-workflows.mdx b/src/content/docs/agents/api-reference/run-workflows.mdx index 442ba327df4ca2..0a632a1a731040 100644 --- a/src/content/docs/agents/api-reference/run-workflows.mdx +++ b/src/content/docs/agents/api-reference/run-workflows.mdx @@ -16,7 +16,7 @@ Because an Agent is just like a Worker script, it can create Workflows defined i Agents and Workflows have some similarities: they can both run tasks asynchronously. For straightforward tasks that are linear or need to run to completion, a Workflow can be ideal: steps can be retried, they can be cancelled, and can act on events. -Agents do not have to run to completion: they can loop, branch and run forever, and they can also interact directly with users (over HTTP or WebSockets). An Agent can be used to trigger multiple Workflows as it runs, and can thus be used to co-ordinate and manage Workflows to achieve its goals. +Agents do not have to run to completion: they can loop, branch and run forever, and they can also interact directly with users (over HTTP or WebSocket). An Agent can be used to trigger multiple Workflows as it runs, and can thus be used to co-ordinate and manage Workflows to achieve its goals. ::: @@ -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" } 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 ee5950231f75af..c9a60db00a4685 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 diff --git a/src/content/docs/agents/api-reference/websockets.mdx b/src/content/docs/agents/api-reference/websockets.mdx index 6348a15808bb7b..419d1cde09edb3 100644 --- a/src/content/docs/agents/api-reference/websockets.mdx +++ b/src/content/docs/agents/api-reference/websockets.mdx @@ -1,5 +1,5 @@ --- -title: Using WebSockets +title: Using WebSocket pcx_content_type: concept sidebar: order: 10