copy edits

Author: patriciasantaana

src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/index.mdx

@@ -16,21 +16,20 @@ The level of interactivity and visibility of the Challenge Page depends on the A
 
 ## Actions
 
-The following Challenge types are the available Actions when you create a WAF rule for a Challenge Page. 
+The following Challenge types are the available actions when you create a WAF rule for a Challenge Page. 
 
 ### Managed Challenge (recommended)
 
 Managed Challenges are where Cloudflare dynamically chooses the appropriate type of challenge served to the visitor based on the characteristics of a request from the signals indicated by their browser. This helps avoid [CAPTCHAs](https://www.cloudflare.com/learning/bots/how-captchas-work/), which also reduces the lifetimes of human time spent solving CAPTCHAs across the Internet.
 
-Most human visitors are automatically verified and will see Successful on the Challenge Page. However, if Cloudflare detects non-human attributes from the visitor’s browser, they may be required to interact with the Challenge to solve it.
+Most human visitors are automatically verified and will see **Successful** on the Challenge Page. However, if Cloudflare detects non-human attributes from the visitor's browser, they may be required to interact with the Challenge to solve it.
 
 Unless there are specific compatibility issues or other reasons to use other types of Challenges, Cloudflare recommends you to use Managed Challenges for your custom rules.
 
 :::caution
 Using Cloudflare Challenges along with Rules features may cause Challenge loops. Refer to [Rules troubleshooting](/rules/reference/troubleshooting/) for more information.
 :::
 
-
 ### Interactive Challenge
 
 Interactive Challenge Pages offer the highest security for your website or application because it requires a visitor to interact with the Interstitial Challenge Page, presenting the visitor with an interactive challenge to solve. 

src/content/docs/cloudflare-challenges/challenge-types/turnstile.mdx

@@ -7,9 +7,9 @@ sidebar:
 
 import { Render } from "~/components";
 
-[Turnstile](/turnstile/) is Cloudflare’s CAPTCHA-alternative solution. You can embed Turnstile as a widget on your website or application, where it runs a client-side Challenge directly in the background of the visitor’s browser.
+[Turnstile](/turnstile/) is Cloudflare's CAPTCHA-alternative solution. You can embed Turnstile as a widget on your website or application, where it runs a client-side Challenge directly in the background of the visitor's browser.
 
-Turnstile differs from Challenges Pages in that the Challenge does not pause the request or interrupt the user’s experience. Since the widget is embedded onto the webpage and only runs on a specific part of the HTML, the visitor will have already arrived at the destination URL and is viewing the page when they encounter a Turnstile widget. Instead of blocking the visitor from accessing the entire website, the Turnstile widget prevents the visitor from certain actions such as completing login or sign up forms, and more, until the widget is solved.
+Turnstile differs from Challenges Pages in that the Challenge does not pause the request or interrupt the user's experience. Since the widget is embedded onto the webpage and only runs on a specific part of the HTML, the visitor will have already arrived at the destination URL and is viewing the page when they encounter a Turnstile widget. Instead of blocking the visitor from accessing the entire website, the Turnstile widget prevents the visitor from certain actions such as completing login or sign up forms, and more, until the widget is solved.
 
 In most cases, nothing further is required from the visitor. However, if necessary, Turnstile may display a simple checkbox that the visitor must click to proceed.
 
@@ -21,11 +21,11 @@ After the Challenge passes, Turnstile issues a clearance token to the visitor th
 
 While there are three types of widgets that you can choose to implement on your website or application, the Challenge logic behind them remains the same.
 
-- **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a Challenge based on the signals gathered from the visitor’s browser and presents an interaction only if it detects potentially automated traffic.
+- **Managed (recommended)**: Functions similar to a Managed Challenge Page. It selects a Challenge based on the signals gathered from the visitor's browser and presents an interaction only if it detects potentially automated traffic.
 
 - **Non-Interactive**: The visitor can see the widget, but does not need to interact with it to verify their identity. 
 
-- **Invisible**: The widget is completely invisible from the visitor, but the Challenge still runs in the background.
+- **Invisible**: The widget is completely invisible to the visitor, but the Challenge still runs in the background.
 
 ## Implementation
 

src/content/docs/cloudflare-challenges/concepts/how-challenges-work.mdx

@@ -17,9 +17,9 @@ Challenges can be issued in three primary ways depending on which Cloudflare pro
 | [HTTP DDoS attack protection](/ddos-protection/managed-rulesets/http/) | Any Challenge |
 | [Under Attack Mode](/fundamentals/reference/under-attack-mode/) | [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge-recommended) |
 
-Challenge Pages and Turnstile rely on the same underlying mechanism to issue challenges to your website or application’s visitors.
+Challenge Pages and Turnstile rely on the same underlying mechanism to issue challenges to your website or application's visitors.
 
-JavaScript detections support Cloudflare’s Enterprise Bot Management. While it still relies on client-side detections, JavaScript detections function using a more performant challenge logic than Challenge Pages or Turnstile.
+JavaScript detections support Cloudflare's Enterprise Bot Management. While it still relies on client-side detections, JavaScript detections function using a more performant challenge logic than Challenge Pages or Turnstile.
 
 ---
 

src/content/docs/cloudflare-challenges/frequently-asked-questions.mdx

@@ -85,7 +85,7 @@ Block Amazon Web Services (AWS) and Google Cloud Platform (GCP) because of large
 
 Previously, unless you customize your front-end application, any AJAX request that is challenged will fail because AJAX calls are not rendered in the DOM.
 
-Now, you can [opt-in to Turnstile’s Pre-Clearance cookies](/turnstile/concepts/pre-clearance-support/). This allows you to issue a challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie’s validity is controlled by the zone-specific configurable [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage) security setting.
+Now, you can [opt-in to Turnstile's Pre-clearance cookies](/turnstile/concepts/pre-clearance-support/). This allows you to issue a challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie's validity is controlled by the zone-specific configurable [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage) security setting.
 
 ## Why would I not find any failed challenges?
 

src/content/docs/turnstile/concepts/pre-clearance-support.mdx

@@ -1,41 +1,8 @@
 ---
 title: Pre-clearance support
 pcx_content_type: reference
+external_link: /cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile
 sidebar:
   order: 3
 
----
-
-Pre-clearance in Turnstile allows websites to streamline user experiences by using clearance cookies. These cookies enable visitors to bypass WAF challenges downstream, based on the security clearance level set by the customer. This can be particularly useful for trusted visitors, enhancing usability while maintaining security.
-
-You can integrate Cloudflare challenges by allowing Turnstile to issue a pre-clearance cookie. The pre-clearance level is set upon widget creation or widget modification using the Turnstile API's `clearance_level`. Possible values for the configuration are:
-
-- `no_clearance`
-- `jschallenge`
-- `managed`
-- `interactive`
-
-All widgets are set to `no_clearance` by default.
-
-For Enterprise customers eligible to toggle off domain checks, Cloudflare recommends issuing pre-clearance cookies on widgets where at least one domain is specified.
-
-:::note
-
-Clearance cookies only support zones that are orange-clouded.
-:::
-
-Refer to the [blog post](https://blog.cloudflare.com/integrating-turnstile-with-the-cloudflare-waf-to-challenge-fetch-requests) for more details on how pre-clearance works with WAF.
-
-## Pre-clearance level options
-
-- **Interactive (High)**: Allows a user with a clearance cookie to not be challenged by Interactive, Managed Challenge, or JavaScript Challenge Firewall Rules
-- **Managed (Medium)**: Allows a user with a clearance cookie to not be challenged by Managed Challenge or JavaScript Challenge Firewall Rules
-- **Non-interactive (Low)**: Allows a user with a clearance cookie to not be challenged by JavaScript Challenge Firewall Rules
-
-## Clearance cookie duration
-
-Clearance cookies generated by the Turnstile widget will be valid for the time specified by the zone-level Challenge Passage value. To configure the Challenge Passage setting, refer to the [Challenges documentation](/cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage).
-
-## Setup
-
-To set up pre-clearance cookies, refer to [Enable pre-clearance cookies](/turnstile/get-started/pre-clearance/). 
+---

src/content/docs/turnstile/get-started/mobile-implementation.mdx

@@ -8,7 +8,7 @@ sidebar:
 
 Turnstile is designed to run in a standard browser environment, which includes mobile devices. On native mobile applications, Turnstile can be used with WebViews. This applies to native web applications for iOS and Android. When implementing Turnstile for mobile, ensure you address the common issues below to avoid integration problems.
 
-Any modifications to the environment, such as the User Agent, [Content Security Policy settings](/turnstile/reference/content-security-policy/), or domain allowlisting, can disrupt the successful completion of Turnstile challenges. To ensure compatibility, it is recommended to start with a default, unmodified environment and gradually introduce changes, validating Turnstile’s functionality after each adjustment.
+Any modifications to the environment, such as the User Agent, [Content Security Policy settings](/turnstile/reference/content-security-policy/), or domain allowlisting, can disrupt the successful completion of Turnstile challenges. To ensure compatibility, it is recommended to start with a default, unmodified environment and gradually introduce changes, validating Turnstile's functionality after each adjustment.
 
 
 ## WebView configurations
@@ -46,4 +46,4 @@ If pre-clearance is done in a different environment, the clearance cookie may be
 
 ## Use Flutter with Turnstile
 
-For developers using [Flutter](https://pub.dev/packages/flutter_inappwebview), Turnstile is compatible and tested with Flutter’s WebView implementation. Refer to the official Flutter WebView package for more details and usage. 
+For developers using [Flutter](https://pub.dev/packages/flutter_inappwebview), Turnstile is compatible and tested with Flutter's WebView implementation. Refer to the official Flutter WebView package for more details and usage. 

src/content/docs/turnstile/get-started/server-side-validation.mdx

@@ -11,7 +11,7 @@ import { GlossaryTooltip, Render, TabItem, Tabs } from "~/components";
 
 Turnstile needs to be verified using Siteverify because it is a front-end widget that creates a token which is cryptographically secured. To ensure that a token is not forged by an attacker or has not been consumed yet, it is necessary to check the validity of a token using Cloudflare's Siteverify API.
 
-You must call the Siteverify endpoint to validate the Turnstile widget response from your website’s backend. The widget response must only be considered valid once it has been verified by the Siteverify endpoint. The presence of a response alone is not enough to verify it as it does not protect from replay or forgery attacks. In some cases, Turnstile may purposely create invalid responses that are rejected by the Siteverify API.
+You must call the Siteverify endpoint to validate the Turnstile widget response from your website's backend. The widget response must only be considered valid once it has been verified by the Siteverify endpoint. The presence of a response alone is not enough to verify it as it does not protect from replay or forgery attacks. In some cases, Turnstile may purposely create invalid responses that are rejected by the Siteverify API.
 
 Tokens issued to Turnstile using the success callbacks, via explicit or implicit rendering, must be validated using the Siteverify endpoint. The Siteverify API will only validate a token once. If a token has already been checked, the Siteverify API will yield an error on subsequent verification attempts indicating that a token has already been consumed.
 
@@ -244,7 +244,7 @@ async function handlePost(request) {
 The `remoteip` parameter helps to prevent abuse by ensuring the current visitor is the one who received the token. This is currently not strictly validated.
 :::
 
-The Siteverify endpoint behaves similar to reCAPTCHA’s or hCaptcha's Siteverify endpoint.
+The Siteverify endpoint behaves similar to reCAPTCHA's or hCaptcha's Siteverify endpoint.
 The API accepts `application/x-www-form-urlencoded` and `application/json` requests, but the response type will always be `application/json`.
 
 It always contains a `success` property, either true or false, indicating whether the operation was successful or not.

src/content/docs/turnstile/index.mdx

@@ -20,7 +20,7 @@ import {
 
 <Description>
 
-Cloudflare’s smart CAPTCHA alternative.
+Cloudflare's smart CAPTCHA alternative.
 
 </Description>
 

src/content/docs/turnstile/reference/workers-templates/price-scraping.mdx

@@ -73,7 +73,7 @@ async function getPrice(token){
    );
    // await price information from pricing endpoint
    const price = await response.json();
-   // set the pricing information to what’s returned in the callback
+   // set the pricing information to what's returned in the callback
    priceBox.innerText = price.pricing
 }
 function init(){

src/content/docs/turnstile/troubleshooting/client-side-errors/error-codes.mdx

@@ -18,7 +18,7 @@ When an error code is marked with `***`, it means that the remaining numbers can
 | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `100***`                                        | Initialization Problems: There was a problem initializing Turnstile before a challenge could be started.                                                                                                                    | No    | This could be caused by an old instance of the challenge that was solved. It is advised to reload the page and restart Turnstile. On continuous failures, this is indicative of an automated device.                                                                      |
 | `102***`                                        | Invalid Parameters: The visitor sent an invalid parameter as part of the challenge towards Turnstile.                                                                                                                       | Yes   | It is advised to retry the challenge. On continuous failures, this is indicative of an automated device.                                                                                                                                                                  |
-| `102***`<br/>`103***`<br/>`104***`<br/>`106***` | Invalid Parameters: The visitor sent an invalid parameter as part of the challenge towards Turnstile.                                                                                                                       | Yes   | It is advised to retry the challenge. On continuous failures, this is indicative of an automated device and you must verify the visitor’s authenticity by other means.                                                                                                    |
+| `102***`<br/>`103***`<br/>`104***`<br/>`106***` | Invalid Parameters: The visitor sent an invalid parameter as part of the challenge towards Turnstile.                                                                                                                       | Yes   | It is advised to retry the challenge. On continuous failures, this is indicative of an automated device and you must verify the visitor's authenticity by other means.                                                                                                    |
 | `105***`                                        | Turnstile API Compatibility: Turnstile was invoked in a deprecated or invalid way.                                                                                                                                          | No    | It is advised to refer to the [Turnstile documentation](/turnstile/) again and refresh the page to obtain the most recent Turnstile version.                                                                                                                              |
 | `110100` <br/> `110110`                         | Invalid <GlossaryTooltip term="sitekey">sitekey</GlossaryTooltip>: Turnstile was invoked with an invalid sitekey or a sitekey that is no longer active.                                                                     | No    | Verify if the sitekey provided is still active via the [Cloudflare dashboard](https://dash.cloudflare.com/).                                                                                                                                                              |
 | `110200`                                        | Unknown domain: Domain not allowed.                                                                                                                                                                                         | No    | Turnstile was used on a domain that was not allowed for this widget to be used on. Ensure that the domain is allowed in the widget configuration via the [Cloudflare dashboard](https://dash.cloudflare.com/).                                                            |