diff --git a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx index c21604a90459c69..4daa25055043a15 100644 --- a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx +++ b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx @@ -25,7 +25,7 @@ captures and processes. ## View your website analytics -To view metrics for your website, in the Cloudflare dashboard, go to the **Analytis & Logs** page. +To view metrics for your website, in the Cloudflare dashboard, go to the **Analytics & Logs** page. diff --git a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx index ccd12acea299f70..722f506168473bc 100644 --- a/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx +++ b/src/content/docs/analytics/graphql-api/tutorials/querying-email-routing.mdx @@ -11,7 +11,7 @@ products: This example uses the GraphQL Analytics API to query for Email Routing events over a specified time period. -## Activiy Logs API Call +## Activity Logs API Call The following API call will request Email Routing activity logs over a one day 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 as required. diff --git a/src/content/docs/api-shield/security/schema-validation/index.mdx b/src/content/docs/api-shield/security/schema-validation/index.mdx index 21be2e76f7bd631..c55514aad05ac65 100644 --- a/src/content/docs/api-shield/security/schema-validation/index.mdx +++ b/src/content/docs/api-shield/security/schema-validation/index.mdx @@ -511,7 +511,7 @@ For example, when the OpenAPI file specifies `application/*` as part of the requ Cloudflare recommends keeping the media-ranges as tight as possible by setting them to an individual media-type. If you need to support multiple content-types on an API endpoint, you can utilize wildcard media-ranges. -Care should also be taken if the origin is configured to perform [MIME sniffing](https://mimesniff.spec.whatwg.org/). For example, when a request carrying a JSON body is deliberately carrying an `application/malicous` content-type and Cloudflare was configured to allow `application/*` media-ranges, the request would be passed along to the origin without validating the JSON body contents. However, an origin that ignores the content-type and either trial deserializes or sniffs the MIME type may deserialize the JSON body with a wrong assumption of having passed schema body validation. +Care should also be taken if the origin is configured to perform [MIME sniffing](https://mimesniff.spec.whatwg.org/). For example, when a request carrying a JSON body is deliberately carrying an `application/malicious` content-type and Cloudflare was configured to allow `application/*` media-ranges, the request would be passed along to the origin without validating the JSON body contents. However, an origin that ignores the content-type and either trial deserializes or sniffs the MIME type may deserialize the JSON body with a wrong assumption of having passed schema body validation. As such, if you need to support `application/json` and `application/xml` on the same endpoint, you can use `application/*`. Cloudflare will validate the provided schema for request bodies where the content-type is set to `application/json`. Requests with content-type `application/xml` (and others matching `application/*`) will be let through. It is still strongly advised to disable content-type sniffing on your origin. diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx index 5627bf13803761c..9e1d2c97c8bc34a 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/impersonation-registry.mdx @@ -73,7 +73,7 @@ To edit users from other integrations: :::note -Adiministrators can remove users who belong to the Email security directory from the **Impersonation registry**. Users who come from an integrated directory cannot be removed from the **Impersonation registry** directly. +Administrators can remove users who belong to the Email security directory from the **Impersonation registry**. Users who come from an integrated directory cannot be removed from the **Impersonation registry** directly. To remove a user from an integrated directory: diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx index 0264b89bc62af73..5c0e77741d6ff99 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx @@ -55,7 +55,7 @@ To use Email security, you will need to have: On the [Google Cloud Console](https://console.cloud.google.com/welcome/new): -1. On the sidebar, select **IAM & Admim** > **Service Accounts**. +1. On the sidebar, select **IAM & Admin** > **Service Accounts**. 2. Locate your email, select the three dots, then select **Manage keys**. 3. Select **Add key** > **Create new key**. 4. Select **JSON** > Select **CREATE**. This downloads a `.json` file which you will use when [uploading a JSON key](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/#3-upload-json-key). diff --git a/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx b/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx index bc4f4cf4fdb2976..0e10f92d57bd46b 100644 --- a/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx +++ b/src/content/docs/cloudflare-one/tutorials/mongodb-tunnel.mdx @@ -16,7 +16,7 @@ tags: import { Details } from "~/components"; -You can build Zero Trust rules to secure connections to MongoDB deployments using Cloudflare Access and Cloudflare Tunnel. Cloudflare Tunnel requires a lightweight daemon, `cloudflared`, running alongisde the deployment and as on the client side. +You can build Zero Trust rules to secure connections to MongoDB deployments using Cloudflare Access and Cloudflare Tunnel. Cloudflare Tunnel requires a lightweight daemon, `cloudflared`, running alongside the deployment and as on the client side. In this tutorial, a client running `cloudflared` connects over SSH to a MongoDB deployment running on Kubernetes. The deployment example is structured to connect [Compass](https://www.mongodb.com/products/compass) to the MongoDB instance. The MongoDB Kubernetes deployment runs both the MongoDB database service and `cloudflared` as a ingress service that operates like a jump host. diff --git a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx index 67b07408d9070cd..ddf48da6a5d915f 100644 --- a/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx +++ b/src/content/docs/learning-paths/holistic-ai-security/get-started/define-ai-risk-tolerance.mdx @@ -4,7 +4,7 @@ pcx_content_type: overview sidebar: label: Define your company's AI risk tolerance and strategy order: 3 -description: Learn about define your companys ai risk tolerance and strategy in this guide. +description: Learn about define your company's AI risk tolerance and strategy in this guide. products: - gateway - cloudflare-one diff --git a/src/content/docs/r2/data-catalog/config-examples/spark-scala.mdx b/src/content/docs/r2/data-catalog/config-examples/spark-scala.mdx index e8937c95df1729a..9e47e4ec42e1078 100644 --- a/src/content/docs/r2/data-catalog/config-examples/spark-scala.mdx +++ b/src/content/docs/r2/data-catalog/config-examples/spark-scala.mdx @@ -103,7 +103,7 @@ assembly / assemblyMergeStrategy := { case x => MergeStrategy.first } -// For Java 17 Compatability +// For Java 17 Compatibility Compile / javacOptions ++= Seq("--release", "17") ``` @@ -134,11 +134,11 @@ To run the application, you will use `spark-submit`. Below is an example shell s ``` # We need to set these "--add-opens" so that Spark can run on Java 17 (it needs access to # parts of the JVM which have been modularized and made internal). -JAVA_17_COMPATABILITY="--add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED" +JAVA_17_COMPATIBILITY="--add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED" spark-submit \ ---conf "spark.driver.extraJavaOptions=$JAVA_17_COMPATABILITY" \ ---conf "spark.executor.extraJavaOptions=$JAVA_17_COMPATABILITY" \ +--conf "spark.driver.extraJavaOptions=$JAVA_17_COMPATIBILITY" \ +--conf "spark.executor.extraJavaOptions=$JAVA_17_COMPATIBILITY" \ --class com.example.R2DataCatalogDemo target/scala-2.12/R2DataCatalogDemo-assembly-1.0.jar ``` diff --git a/src/content/docs/reference-architecture/architectures/sase.mdx b/src/content/docs/reference-architecture/architectures/sase.mdx index 737fee4c2b7c58b..25a3e17ccc96d18 100644 --- a/src/content/docs/reference-architecture/architectures/sase.mdx +++ b/src/content/docs/reference-architecture/architectures/sase.mdx @@ -664,7 +664,7 @@ DLP policies can also be applied in the other direction, ensuring that company s ### Visibility across the deployment -At this point in the SASE journey, users have re-architectured the IT network and security infrastructure to fully leverage all the capabilities of the Cloudflare One SASE platform. A critical element in long term deployment involves establishing complete visibility into the organization and the ability to diagnose and quickly resolve issues. +At this point in the SASE journey, users have re-architected the IT network and security infrastructure to fully leverage all the capabilities of the Cloudflare One SASE platform. A critical element in long term deployment involves establishing complete visibility into the organization and the ability to diagnose and quickly resolve issues. For quick analysis, Cloudflare provides built-in dashboards and analytics that offers a daily overview of the deployment's operational status. As traffic flows through Cloudflare, the dashboard will alert internal users to the most frequently used SaaS applications, enabling quick actions if any unauthorized applications are accessed by external users. Moreover, all logging information from all Cloudflare One services is accessible and searchable from the administrator's dashboard. This makes it efficient to filter for specific blocked requests, with each log containing useful information such as the user's identity, device information, and the specific rule that triggered the block. This can be very handy in the early stages of deployment where rules can often need tweaking. diff --git a/src/content/docs/reference-architecture/index.mdx b/src/content/docs/reference-architecture/index.mdx index 1d8e012c5839d69..83b4327c784205c 100644 --- a/src/content/docs/reference-architecture/index.mdx +++ b/src/content/docs/reference-architecture/index.mdx @@ -24,7 +24,7 @@ All the documents in this section are designed to help you understand how Cloudf -No matter if you know Cloudflare well, or if you are just starting out. These documents help you understand how our connectivity cloud is architectured and how the services can be integrated with your own infrastructure. Read [How to use](/reference-architecture/how-to-use/) to understand how the documentation is structured, and either navigate by type from the menu or [find by solution](/reference-architecture/by-solution/) area. +No matter if you know Cloudflare well, or if you are just starting out. These documents help you understand how our connectivity cloud is architected and how the services can be integrated with your own infrastructure. Read [How to use](/reference-architecture/how-to-use/) to understand how the documentation is structured, and either navigate by type from the menu or [find by solution](/reference-architecture/by-solution/) area. diff --git a/src/content/docs/stream/stream-live/watch-live-stream.mdx b/src/content/docs/stream/stream-live/watch-live-stream.mdx index 1e10a6c70430370..0faa9454132c848 100644 --- a/src/content/docs/stream/stream-live/watch-live-stream.mdx +++ b/src/content/docs/stream/stream-live/watch-live-stream.mdx @@ -36,7 +36,7 @@ input; it will not change. Use a Video ID in instances where a player should be used to display a single broadcast or its recording once the broadcast has concluded. This option is best for cases where -a page is dedicated to a one-time event, specific episode/occurance, or date. +a page is dedicated to a one-time event, specific episode/occurrence, or date. There is a _new_ Video ID generated for each broadcast _when it starts._ Using DVR mode, explained below, there are additional considerations. diff --git a/src/content/docs/workers-ai/features/fine-tunes/public-loras.mdx b/src/content/docs/workers-ai/features/fine-tunes/public-loras.mdx index d82bdcbe4a069c5..c8e3832b72634b3 100644 --- a/src/content/docs/workers-ai/features/fine-tunes/public-loras.mdx +++ b/src/content/docs/workers-ai/features/fine-tunes/public-loras.mdx @@ -64,7 +64,7 @@ const answer = await env.AI.run("@cf/mistral/mistral-7b-instruct-v0.1", { { role: "user", content: - "Summarize the following: Some newspapers, TV channels and well-known companies publish false news stories to fool people on 1 April. One of the earliest examples of this was in 1957 when a programme on the BBC, the UKs national TV channel, broadcast a report on how spaghetti grew on trees. The film showed a family in Switzerland collecting spaghetti from trees and many people were fooled into believing it, as in the 1950s British people didnt eat much pasta and many didnt know how it was made! Most British people wouldnt fall for the spaghetti trick today, but in 2008 the BBC managed to fool their audience again with their Miracles of Evolution trailer, which appeared to show some special penguins that had regained the ability to fly. Two major UK newspapers, The Daily Telegraph and the Daily Mirror, published the important story on their front pages.", + "Summarize the following: Some newspapers, TV channels and well-known companies publish false news stories to fool people on 1 April. One of the earliest examples of this was in 1957 when a programme on the BBC, the UKs national TV channel, broadcast a report on how spaghetti grew on trees. The film showed a family in Switzerland collecting spaghetti from trees and many people were fooled into believing it, as in the 1950s British people didn't eat much pasta and many didn't know how it was made! Most British people wouldnt fall for the spaghetti trick today, but in 2008 the BBC managed to fool their audience again with their Miracles of Evolution trailer, which appeared to show some special penguins that had regained the ability to fly. Two major UK newspapers, The Daily Telegraph and the Daily Mirror, published the important story on their front pages.", }, ], lora: "cf-public-cnn-summarization", diff --git a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx index 7218158dad2f5ea..76410832c187ce3 100644 --- a/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx +++ b/src/content/docs/workers/framework-guides/web-apps/nextjs.mdx @@ -111,7 +111,7 @@ Most Next.js features are supported by the Cloudflare OpenNext adapter: [**Workers Builds**](/workers/ci-cd/builds/) requires you to configure environment variables in the ["Build Variables and secrets"](/workers/ci-cd/builds/configuration/#:~:text=Build%20variables%20and%20secrets) section. - This ensures the Next build has the necessary access to both public `NEXT_PUBLC...` variables and [non-`NEXT_PUBLIC_...`](https://nextjs.org/docs/pages/guides/environment-variables#bundling-environment-variables-for-the-browser), which are essential for tasks like inlining and building SSG pages. + This ensures the Next build has the necessary access to both public `NEXT_PUBLIC...` variables and [non-`NEXT_PUBLIC_...`](https://nextjs.org/docs/pages/guides/environment-variables#bundling-environment-variables-for-the-browser), which are essential for tasks like inlining and building SSG pages. Learn more in the [OpenNext environment variable guide](https://opennext.js.org/cloudflare/howtos/env-vars#workers-builds) @@ -238,7 +238,7 @@ If you prefer to configure your project manually, follow the steps below. [**Workers Builds**](/workers/ci-cd/builds/) requires you to configure environment variables in the ["Build Variables and secrets"](/workers/ci-cd/builds/configuration/#:~:text=Build%20variables%20and%20secrets) section. - This ensures the Next build has the necessary access to both public `NEXT_PUBLC...` variables and [non-`NEXT_PUBLIC_...`](https://nextjs.org/docs/pages/guides/environment-variables#bundling-environment-variables-for-the-browser), which are essential for tasks like inlining and building SSG pages. + This ensures the Next build has the necessary access to both public `NEXT_PUBLIC...` variables and [non-`NEXT_PUBLIC_...`](https://nextjs.org/docs/pages/guides/environment-variables#bundling-environment-variables-for-the-browser), which are essential for tasks like inlining and building SSG pages. Learn more in the [OpenNext environment variable guide](https://opennext.js.org/cloudflare/howtos/env-vars#workers-builds) diff --git a/src/content/docs/workers/runtime-apis/nodejs/test.mdx b/src/content/docs/workers/runtime-apis/nodejs/test.mdx index bad533eaca9fe0f..b26975393f2ea90 100644 --- a/src/content/docs/workers/runtime-apis/nodejs/test.mdx +++ b/src/content/docs/workers/runtime-apis/nodejs/test.mdx @@ -22,7 +22,7 @@ const fn = mock.fn(); fn(1,2,3); // does nothing... but console.log(fn.mock.callCount()); // Records how many times it was called -console.log(fn.mock.calls[0].arguments)); // Recoreds the arguments that were passed each call +console.log(fn.mock.calls[0].arguments)); // Records the arguments that were passed each call ``` The full `MockTracker` API is documented in the [Node.js documentation for `MockTracker`](https://nodejs.org/docs/latest/api/test.html#class-mocktracker).