Skip to content

Commit 50180a2

Browse files
accessibility
1 parent 9fd41a2 commit 50180a2

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The following Challenge types are the available actions when you create a WAF ru
2222

2323
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.
2424

25-
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.
25+
Most human visitors are automatically verified and the Challenge Page will display **Successful**. However, if Cloudflare detects non-human attributes from the visitor's browser, they may be required to interact with the Challenge to solve it.
2626

2727
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.
2828

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ While there are three types of widgets that you can choose to implement on your
2323

2424
- **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.
2525

26-
- **Non-Interactive**: The visitor can see the widget, but does not need to interact with it to verify their identity.
26+
- **Non-Interactive**: The widget is displayed, but the visitor does not need to interact with it to verify their identity.
2727

2828
- **Invisible**: The widget is completely invisible to the visitor, but the Challenge still runs in the background.
2929

src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ When a user is presented with a Challenge Page, Cloudflare decides what Challeng
99

1010
While some Challenges are computationally complex or require interactivity, most of the Challenges served are invisible to the user.
1111

12-
The Challenge Page is an interstitial page and users will see it regardless of having a valid PAT or not. A PAT does not automatically solve a Challenge. It prevents certain Challenges from being issued.
12+
The Challenge Page is an interstitial page and users will encounter it regardless of having a valid PAT or not. A PAT does not automatically solve a Challenge. It prevents certain Challenges from being issued.

0 commit comments

Comments
 (0)