fixes

Author: patriciasantaana

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

@@ -3,7 +3,6 @@ title: Challenge outcome
 pcx_content_type: Concept
 sidebar:
   order: 2
-head: []
 ---
 
 import { Render } from "~/components"
@@ -12,7 +11,7 @@ When a visitor encounters Turnstile, it assesses whether they are human or bot-l
 
 ## Metrics
 
-A "solved" Turnstile challenge does not automatically confirm the visitor is human. You must call the siteverify API to validate the token and proceed only if the response returns `success:true`.
+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`.
 
 ![Challenge outcomes](~/assets/images/turnstile/challenge-outcomes.png)
 
@@ -42,4 +41,4 @@ If you are using [managed mode](/turnstile/concepts/widget/#widget-types), you c
 - **Interactive solves**: Challenges solved that required visitor interaction to be solved.
 - [**Pre-clearance solves**](/turnstile/concepts/pre-clearance-support/): Challenges solved that issued the `cf-clearance` cookie along with the Turnstile token.
 
-A low solve rate might indicate increased bot activity attempting to bypass Turnstile or anomalous traffic patterns that require further investigation.
+A low solve rate might indicate increased bot activity attempting to bypass Turnstile or anomalous traffic patterns that require further investigation.

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

@@ -3,7 +3,6 @@ title: Turnstile Analytics
 pcx_content_type: how-to
 sidebar:
   order: 6
-head: []
 description: Use Turnstile Analytics to view the number of challenges issued,
   the challenge solve rate, and the metrics of issued challenges.
 

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

@@ -3,7 +3,6 @@ title: Token validation
 pcx_content_type: concept
 sidebar:
   order: 3
-head: []
 ---
 
 import { Render } from "~/components"

src/content/partials/turnstile/siteverify.mdx

@@ -3,7 +3,7 @@
 
 ---
 
-It is important to [call siteverify API](/turnstile/get-started/server-side-validation/). Without calling siteverify API to validate the tokens, your website or application is not protected: Skipping token validation means you cannot confirm the visitor's legitimacy.
+It is important to [call the siteverify API](/turnstile/get-started/server-side-validation/). Without calling siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
 
 - Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
 - Tokens expire after five minutes. Validation must occur within this window to be effective.