Skip to content

Commit c3f563a

Browse files
authored
Remove trailing spaces (#21836)
1 parent 36b906e commit c3f563a

File tree

5 files changed

+9
-9
lines changed

5 files changed

+9
-9
lines changed

src/content/docs/turnstile/concepts/hostname-management.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ If the widget is embedded on a hostname not listed, it will display an error mes
6363

6464
Customers with Enterprise Bot Management or Enterprise Turnstile can have the optional `any hostname` validation entitlement.
6565

66-
By default, a widget requires at least one hostname to be entered. With this entitlement, you can create and use a widget without entering any hostnames for the widget.
66+
By default, a widget requires at least one hostname to be entered. With this entitlement, you can create and use a widget without entering any hostnames for the widget.
6767

6868
Contact your account team to enable this entitlement.
6969

src/content/docs/turnstile/concepts/widget.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Every instance of Turnstile belongs to a Turnstile widget. It is configured on a
1212

1313
The 3 modes for Turnstile are **Managed**, **Non-Interactive**, and **Invisible**.
1414

15-
Refer to [appearance modes](/turnstile/get-started/client-side-rendering/#appearance-modes) to configure whether to have the widget be always visible or visible only when interaction is required, and to customize your widget theme between automatic, light, or dark mode.
15+
Refer to [appearance modes](/turnstile/get-started/client-side-rendering/#appearance-modes) to configure whether to have the widget be always visible or visible only when interaction is required, and to customize your widget theme between automatic, light, or dark mode.
1616

1717
Widgets can be implemented in normal, flexible, or compact sizes.
1818

src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ When a visitor encounters Turnstile, it assesses whether they are human or bot-l
1313

1414
A "solved" Turnstile challenge does not automatically confirm the visitor is human. You must [call the siteverify API](#call-siteverify) to validate the token and proceed only if the response returns `success:true`.
1515

16-
For example, the challenge outcome values in your analytics may look like this:
16+
For example, the challenge outcome values in your analytics may look like this:
1717

1818
![Challenge outcome example values](~/assets/images/turnstile/challenge-outcomes.png "Challenge outcome example")
1919

@@ -31,11 +31,11 @@ By analyzing these metrics, you can identify trends such as high failure rates i
3131

3232
## Solve rates
3333

34-
Turnstile's solve rate is a critical metric that helps gauge how many legitimate visitors are passing a challenge. Solve rates can be broken down into the total number of challenges solved and whether they are interactive, non-interactive, or pre-clearance solves.
34+
Turnstile's solve rate is a critical metric that helps gauge how many legitimate visitors are passing a challenge. Solve rates can be broken down into the total number of challenges solved and whether they are interactive, non-interactive, or pre-clearance solves.
3535

36-
If you are using [managed mode](/turnstile/concepts/widget/#widget-types), you can monitor how many of your visitors were prompted interactivity to check the box on the widget (interactive solves) and how many were verified without any disruptions to their experience (non-interactive solves).
36+
If you are using [managed mode](/turnstile/concepts/widget/#widget-types), you can monitor how many of your visitors were prompted interactivity to check the box on the widget (interactive solves) and how many were verified without any disruptions to their experience (non-interactive solves).
3737

38-
For example, the solve rate values in your analytics may look like this:
38+
For example, the solve rate values in your analytics may look like this:
3939

4040
![Solve rate example values](~/assets/images/turnstile/solve-rates.png "Solve rate example")
4141

src/content/docs/turnstile/turnstile-analytics/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ Turnstile Analytics provides you with a view of the top widget statistics across
2626

2727
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
2828
2. Go to **Turnstile** and then navigate to your widget to see an overview of its analytics.
29-
29+
3030
The metrics show changes in the solve rate, widget traffic, and top actions for your widget.
3131

3232
![Turnstile Analytics overview](~/assets/images/turnstile/top-actions.png)
3333

34-
Refer to the pages below for more information about Turnstile Analytics:
34+
Refer to the pages below for more information about Turnstile Analytics:
3535

3636
<DirectoryListing />

src/content/docs/turnstile/turnstile-analytics/token-validation.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ import { Render } from "~/components"
99

1010
After a visitor successfully completes a Turnstile challenge, a token is generated and validated via the siteverify API. Token validation data provides crucial insights into your security posture.
1111

12-
For example, the token validation values in your analytics may look like this:
12+
For example, the token validation values in your analytics may look like this:
1313

1414
![Token validation example values](~/assets/images/turnstile/token-validation.png "Token validation example")
1515

0 commit comments

Comments
 (0)