chore: update translations and generated content (#1387)

* chore: update translations and generated content

* fix: lint errors

---------

Co-authored-by: charIeszhao <12833674+charIeszhao@users.noreply.github.com>
Co-authored-by: Charles Zhao <charleszhao@silverhand.io>

Author: silverhand-bot

docs/end-user-flows/sign-up-and-sign-in/passkey-sign-in.mdx

@@ -8,7 +8,7 @@ Passkey sign-in lets users authenticate with a WebAuthn credential directly duri
 
 This document explains how passkey sign-in works in Logto's built-in sign-in experience, what the different entry paths look like for end users, and how it interacts with MFA.
 
-## How passkey sign-in works
+## How passkey sign-in works \{#how-passkey-sign-in-works}
 
 To use passkey sign-in, you first need to enable it in the <CloudLink to="/sign-in-experience/sign-up-and-sign-in">sign-in experience</CloudLink> configuration. After it is enabled, Logto can offer passkey sign-in in up to three ways on the sign-in page:
 
@@ -34,9 +34,9 @@ flowchart LR
     I --> J["Sign-in succeeds"]
 ```
 
-## Three passkey sign-in paths
+## Three passkey sign-in paths \{#three-passkey-sign-in-paths}
 
-### 1. Show "Continue with passkey" button enabled
+### 1. Show "Continue with passkey" button enabled \{#1-show-continue-with-passkey-button-enabled}
 
 When `Show "Continue with passkey" button` option is enabled, the sign-in page shows a `Continue with passkey` button at the bottom of the first screen.
 
@@ -50,7 +50,7 @@ The user flow is:
 
 This is the most direct path. It is best for users who already know they have a saved passkey and want a one-step login experience.
 
-### 2. Show "Continue with passkey" button disabled
+### 2. Show "Continue with passkey" button disabled \{#2-show-continue-with-passkey-button-disabled}
 
 When `Show "Continue with passkey" button` option is disabled, Logto switches to an identifier-first experience on the first screen. The page only asks for the user's identifier first.
 
@@ -76,7 +76,7 @@ flowchart LR
     I --> G
 ```
 
-### 3. Allow prompting and autofill
+### 3. Allow prompting and autofill \{#3-allow-prompting-and-autofill}
 
 When `Allow prompting and autofill` option is enabled, compatible browsers can show the pre-saved passkeys directly from the identifier input field.
 
@@ -90,7 +90,7 @@ The user flow is:
 
 This flow is especially useful on devices where passkeys are already synced by the platform, because users can sign in without manually moving to a second page or tapping a dedicated passkey button.
 
-## Sign-up and passkey binding flow
+## Sign-up and passkey binding flow \{#sign-up-and-passkey-binding-flow}
 
 Passkey sign-in is not only a sign-in entry point. It also affects what happens after registration, because the same WebAuthn credential can later be reused for both sign-in and MFA.
 
@@ -120,9 +120,9 @@ flowchart LR
     M --> H
 ```
 
-## Relationship between passkey sign-in and MFA
+## Relationship between passkey sign-in and MFA \{#relationship-between-passkey-sign-in-and-mfa}
 
-### Passkey sign-in automatically skips MFA verification
+### Passkey sign-in automatically skips MFA verification \{#passkey-sign-in-automatically-skips-mfa-verification}
 
 A passkey used for passkey sign-in is backed by a WebAuthn credential, and that credential is also treated as a WebAuthn MFA factor. Because of that, passkey sign-in and WebAuthn MFA are effectively equivalent from the credential perspective.
 
@@ -133,7 +133,7 @@ That leads to two important behaviors:
 
 In other words, a successful passkey sign-in already satisfies the WebAuthn-based identity verification that would otherwise be required during MFA.
 
-### Binding a passkey does not automatically force MFA for user-controlled tenants
+### Binding a passkey does not automatically force MFA for user-controlled tenants \{#binding-a-passkey-does-not-automatically-force-mfa-for-user-controlled-tenants}
 
 For users in tenants where MFA is not mandatory, binding a passkey during sign-up or account setup does not automatically turn on MFA for the account.
 
@@ -146,25 +146,25 @@ On that page, the user can:
 
 If the user chooses to enable MFA, Logto then continues with the normal MFA setup flow and may ask the user to bind additional factors, depending on the tenant's MFA configuration. For example, if other MFA factors are enabled for the tenant, Logto can continue with binding another factor or backup codes.
 
-### What happens when passkey sign-in is disabled later
+### What happens when passkey sign-in is disabled later \{#what-happens-when-passkey-sign-in-is-disabled-later}
 
 If passkey sign-in is turned off later, the previously bound passkey is still a WebAuthn credential. That means it can continue to work as an MFA factor as long as WebAuthn MFA remains available for the tenant.
 
 Disabling passkey sign-in removes the passkey as a direct sign-in entry point, but it does not invalidate the underlying WebAuthn MFA credential.
 
-## Limitations and compatibility
+## Limitations and compatibility \{#limitations-and-compatibility}
 
 - Passkey sign-in is not available for Enterprise SSO users.
 - Passkey sign-in depends on browser and platform WebAuthn support.
 - "Allow prompting and autofill" only works in browsers and environments that support passkey autofill / conditional UI.
 - Passkeys are origin-bound. A passkey registered for one domain cannot be used on another domain.
 
-## Q&A
+## Q&A \{#q-a}
 
 <details>
   <summary>
 
-### Does passkey sign-in still require MFA verification?
+### Does passkey sign-in still require MFA verification? \{#does-passkey-sign-in-still-require-mfa-verification}
 
   </summary>
 
@@ -175,7 +175,7 @@ No. A successful passkey sign-in already satisfies the WebAuthn-based verificati
 <details>
   <summary>
 
-### Can a passkey bound for passkey sign-in still be used as an MFA factor after passkey sign-in is disabled?
+### Can a passkey bound for passkey sign-in still be used as an MFA factor after passkey sign-in is disabled? \{#can-a-passkey-bound-for-passkey-sign-in-still-be-used-as-an-mfa-factor-after-passkey-sign-in-is-disabled}
 
   </summary>
 
@@ -186,7 +186,7 @@ Yes. Passkey sign-in and WebAuthn MFA are backed by the same underlying credenti
 <details>
   <summary>
 
-### Can Enterprise SSO users use passkey sign-in?
+### Can Enterprise SSO users use passkey sign-in? \{#can-enterprise-sso-users-use-passkey-sign-in}
 
   </summary>
 
@@ -197,7 +197,7 @@ No. Enterprise SSO users are not eligible for passkey sign-in.
 <details>
   <summary>
 
-### Does passkey sign-in still require CAPTCHA?
+### Does passkey sign-in still require CAPTCHA? \{#does-passkey-sign-in-still-require-captcha}
 
   </summary>