chore: update translations and generated content

Author: Rany0101

docs/end-user-flows/account-settings/README.mdx

@@ -10,7 +10,7 @@ import GearIcon from '@site/src/assets/gear.svg';
 
 Logto provides a two collection of account settings APIs to allow users to manage their account and profiles stored in Logto.
 
-## Use Account APIs (Recommended)
+## Use Account APIs (Recommended) \{#use-account-apis-recommended}
 
 Logto’s Account APIs are ready-to-use, front-end endpoints that let end users securely view and update their own information with built-in permission checks. Simply embed them in your client application to power a polished, self-service account settings page.
 
@@ -36,7 +36,7 @@ Key features:
   ]}
 />
 
-## Use Management APIs
+## Use Management APIs \{#use-management-apis}
 
 The Management APIs form Logto’s core administrative interface, accessible only to admins or back-end services. They deliver maximum flexibility and full CRUD control over every user account and allow you to build custom management tools. If you need a fully custom self-service portal or nonstandard user-management features, you can expose selected Management API endpoints behind your own “Account API” layer and secure them with your business’s auth logic.
 
@@ -61,7 +61,7 @@ Key features:
   ]}
 />
 
-## Account API vs. Management API
+## Account API vs. Management API \{#account-api-vs-management-api}
 
 | Feature                | Account APIs                                                                                        | Management APIs                                                                                                                      |
 | ---------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |

docs/end-user-flows/security-verification/README.mdx

@@ -8,7 +8,7 @@ When authenticated users attempt sensitive or high-risk actions—such as changi
 
 This process, known as _security verification_, requires users to re-verify their identity to confirm they are the authorized account holder. By implementing security verification, the system reinforces protection against unauthorized access, adding a critical layer of security for high-risk actions and helping safeguard sensitive data.
 
-## Implement security verification by Account API
+## Implement security verification by Account API \{#implement-security-verification-by-account-api}
 
 :::note
 Remember to [enable Account API](/end-user-flows/account-settings/by-account-api) first, and get the `access_token` for the user.

docs/end-user-flows/sign-out.mdx

@@ -181,7 +181,7 @@ If you are integrating Logto with your client application using Logto's SDKs:
 For native applications that does not support sessionless webview or does not recognize the `emphasized` settings(Android app using **React Native** or **Flutter** SDK), you may force the user prompt to sign in again by passing the `prompt=login` parameter in the authorization request.
 :::
 
-## Enforce re-authentication on every access
+## Enforce re-authentication on every access \{#enforce-re-authentication-on-every-access}
 
 In high-security scenarios—such as verifying a user's identity before sensitive actions—you may want to require the user to re-authenticate on every access. To enforce this behavior, include `prompt=login` in your authentication request.
 

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

@@ -7,7 +7,7 @@ sidebar_label: Disable user registration
 
 In some circumstances, you may want to restrict user registration for your application. Logto allows you to disable anonymous user registration and restrict user sign-in to only users invited by an administrator.
 
-## Disable user registration
+## Disable user registration \{#disable-user-registration}
 
 To disable end-user registration, follow these steps:
 
@@ -25,7 +25,7 @@ Once user registration is disabled:
 
 Logto does not provide a built-in invitation flow. However, you can easily implement an invite-only sign-up flow by utilizing the users Management API in Logto.
 
-### Option 1: Invite user with magic link (Recommended)
+### Option 1: Invite user with magic link (Recommended) \{#option-1-invite-user-with-magic-link-recommended}
 
 1. Disable user registration in the <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in-experience</CloudLink>.
 2. Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in-experience</CloudLink>, and toggle off "Enable user registration" to close public registration.
@@ -49,7 +49,7 @@ Logto does not provide a built-in invitation flow. However, you can easily imple
 
    When users click "Accept the invitation", they will automatically register for your service, even with public registration disabled. This is referred to as "Targeted user invitation".
 
-### Option 2: Invite and create users via management API
+### Option 2: Invite and create users via management API \{#option-2-invite-and-create-users-via-management-api}
 
 1. Disable user registration in the <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in-experience</CloudLink>.
 2. Create a custom invitation-based user registration form in your application.
@@ -64,7 +64,7 @@ Logto does not provide a built-in invitation flow. However, you can easily imple
 3. Notify users via email that their account has been created.
 4. Redirect users to the Logto sign-in or reset-password page to complete registration. See [Authentication parameters](/end-user-flows/authentication-parameters/) for guidance on customizing the first-screen and pre-filling the user’s email to streamline the sign-in process.
 
-## User experience for pre-registered accounts
+## User experience for pre-registered accounts \{#user-experience-for-pre-registered-accounts}
 
 Pre-registered accounts (also known as provisioned users). In both Option 2 and Option 3, user accounts are created in advance via the Management API. The end users then sign in to your product for the first time.
 

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

@@ -18,7 +18,7 @@ By default, Logto will show a generic error page (e.g., a 404 “unknown session
 - **Unknown session redirect URL**: A fallback URL to send users to when their session is not found.
 - **Support email & Support website**: Contact information shown on error pages.
 
-## Unknown session redirect URL
+## Unknown session redirect URL \{#unknown-session-redirect-url}
 
 Logto uses the [OpenID Connect (OIDC)](https://auth.wiki/openid-connect) flow for authentication. A valid OIDC authorization flow must be initiated by your application, e.g, clicking your app’s “Sign in” button sends an OIDC authorization request to Logto, which then sets up a secure session (cookie).
 
@@ -35,7 +35,7 @@ How to set it up:
 1. Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in experience > Sign-up and sign-in > Advanced settings</CloudLink>
 2. Set the "Unknown session redirect URL" to your service address or product’s homepage. E.g., Logto Cloud will set "https://cloud.logto.io".
 
-## Support contact info
+## Support contact info \{#support-contact-info}
 
 If other errors occur (such as visiting an invalid path, a social callback with no session, or opening an expired magic link), Logto will show a default error page. To help users, you can display contact information on these unavoidable error pages.
 

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

@@ -29,7 +29,7 @@ Not seeing the "Forgot password" link? Make sure you have a valid **Email** or *
 
 For authenticated users, they can update their password by visiting the account settings page. Check the [account settings](/end-user-flows/account-settings/) to learn more about implementing a user account settings page.
 
-## Custom password policy
+## Custom password policy \{#custom-password-policy}
 
 Customize password length, character requirements, and word restrictions to meet your business's security needs while providing a good user experience. These settings can be configured in the **Security** section. Check the [password policy](/security/password-policy) to learn more.
 

docs/integrate-logto/README.mdx

@@ -14,7 +14,7 @@ Logto provides comprehensive authentication solutions for web, mobile and deskto
 
 Start your integration by selecting the solution that best matches your needs:
 
-## Add authentication for your applications
+## Add authentication for your applications \{#add-authentication-for-your-applications}
 
 Whether you're building user-facing applications (like web, mobile, or desktop apps) or machine-to-machine (M2M) applications for service-to-service communication, you can quickly implement comprehensive [authentication](/end-user-flows) and [user management](/user-management) features by integrating Logto.
 
@@ -50,7 +50,7 @@ Or try a no-code integration solution via Protected App when you’re using Logt
   ]}
 />
 
-## Add SAML apps
+## Add SAML apps \{#add-saml-apps}
 
 Logto (as an Identity Provider) supports integration with SAML protocol-based applications (as a Service Provider). Through SAML app integration, you can provide enterprise users with a secure, standardized Single Sign-On (SSO) experience.
 
@@ -69,7 +69,7 @@ Logto (as an Identity Provider) supports integration with SAML protocol-based ap
   ]}
 />
 
-## Add OIDC/OAuth apps
+## Add OIDC/OAuth apps \{#add-oidc-oauth-apps}
 
 When you want to enable third-party applications to authenticate with your Logto identity system, you can configure Logto as an [Identity Provider (IdP)](https://auth.wiki/identity-provider).
 

docs/integrate-logto/third-party-applications/README.mdx

@@ -82,12 +82,12 @@ These requested permissions will be granted to the third-party applications only
   ]}
 />
 
-## FAQs
+## FAQs \{#faqs}
 
 <details>
   <summary>
 
-### How do we ensure users can only grant permissions they actually have on the consent screen?
+### How do we ensure users can only grant permissions they actually have on the consent screen? \{#how-do-we-ensure-users-can-only-grant-permissions-they-actually-have-on-the-consent-screen}
 
 </summary>
 

docs/integrate-logto/third-party-applications/permission-management.mdx

@@ -86,7 +86,7 @@ You can define your own organization scopes under the organization template sett
 Organization scopes that are not enabled to the third-party applications will be ignored when sending an authorization request. It won't be displayed on the user consent screen and won't be granted by Logto.
 :::
 
-### Default OIDC permissions
+### Default OIDC permissions \{#default-oidc-permissions}
 
 Core OIDC permissions are automatically configured for your app. These scopes are required for OIDC authentication and will **not** appear on the user consent screen. OAuth apps can choose not to request them if OIDC authentication isn’t needed.
 

docs/logto-cloud/tenant-settings.mdx

@@ -80,13 +80,13 @@ However, there are certain limitations that apply to development tenants:
 
 The production tenant is where end-users access the live app and you might need a [paid subscription](https://logto.io/pricing). You can subscribe to the Free plan or Pro plan to create a production tenant. If you subscribe to the Free plan, you can only create up to 10 tenants.
 
-## Enable MFA
+## Enable MFA \{#enable-mfa}
 
 Enhance your workspace security by requiring Multi-Factor Authentication (MFA) for all members in your Logto Pro/Enterprise tenant.
 
 Since self-service is not yet available, please [contact us](https://logto.io/contact) to enable this feature.
 
-## Enable Enterprise SSO
+## Enable Enterprise SSO \{#enable-enterprise-sso}
 
 Logto Cloud supports enterprise Single Sign-On integration for paid tenants, including providers like Google Workspace, Okta, Azure AD, and more.