chore: merge pull request #1363 from logto-io/rany-sie-update

chore: update sign-up and account name

Author: Rany

docs/connectors/email-connectors/README.mdx

@@ -187,10 +187,10 @@ To ensure the stability of your service, Cloud users can create a [dev tenant](/
 
 Once you add and configure the email connector, you can enable email-based authentication flows:
 
-- [**Set sign-up methods**](/end-user-flows/sign-up-and-sign-in/sign-up): Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Sign-in experience > Sign-up and sign-in</CloudLink>. In the sign-up section, add "Email address" or "Email address or phone number" as the identifier. Note: Email address verification is mandatory during sign-up.
+- [**Set sign-up methods**](/end-user-flows/sign-up-and-sign-in/sign-up): Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Sign-in & account > Sign-up and sign-in</CloudLink>. In the sign-up section, add "Email address" or "Email address or phone number" as the identifier. Note: Email address verification is mandatory during sign-up.
 - [**Set sign-in methods**](/end-user-flows/sign-up-and-sign-in/sign-in): In the sign-in section, add "Email address" as a sign-in method. Choose between password and email verification code for authentication. Click "Add another" for additional options.
 - [**Set up forgot password**](/end-user-flows/sign-up-and-sign-in/reset-password): In the sign-in section, if password sign-in is enabled, you'll see the "Forgot password" setting. Enable "Email verification code" to allow password resets via email.
-- [**Set up email for MFA**](/end-user-flows/mfa/email-mfa): Go to <CloudLink to="/mfa">Sign-in experience > Multi-factor auth</CloudLink>. Enable "Email verification code" as a second factor for enhanced security.
+- [**Set up email for MFA**](/end-user-flows/mfa/email-mfa): Go to <CloudLink to="/mfa">Console > Multi-factor auth</CloudLink>. Enable "Email verification code" as a second factor for enhanced security.
 - [**Set up account settings**](/end-user-flows/account-settings/by-account-api#update-or-link-new-email): Use the [Account API](/end-user-flows/account-settings/by-account-api) to customize your Account Center and allow users to manage their email addresses.
 
 :::warning

docs/connectors/email-connectors/email-templates.mdx

@@ -316,7 +316,7 @@ Language preference is resolved in the following order:
 
 1. If the OIDC authentication request includes `ui_locales`, Logto selects the first tag in `ui_locales` that is supported by your tenant's language library. See [ui_locales](/end-user-flows/authentication-parameters/ui-locales) for details.
 2. Otherwise, for client-side [Experience APIs](/end-user-flows/sign-up-and-sign-in) and [User Account APIs](/end-user-flows/account-settings/by-account-api), Logto uses the `Accept-Language` header. For Management APIs (such as [Organization Invitation](/end-user-flows/organization-experience/invite-organization-members)), you can specify language via the `locale` field in `messagePayload`.
-3. If neither is provided, Logto falls back to the tenant's default language configured in the Sign-in Experience. Check [Localized languages](/customization/localized-languages#customization-steps-in-logto-console) for configuration details.
+3. If neither is provided, Logto falls back to the tenant's default language configured in the Sign-in & account > Content. Check [Localized languages](/customization/localized-languages#customization-steps-in-logto-console) for configuration details.
 
 Template selection:
 

docs/connectors/enterprise-connectors.mdx

@@ -100,7 +100,7 @@ Please note the following settings:
   :::note
   It's important to note that after configuring relevant email domains in an SSO connector, users signing-in with emails belonging to those domains will be forced to use [SSO sign-in](/end-user-flows/enterprise-sso).
 
-  In other words, only emails from domains that are NOT configured in the SSO connectors can use "email + verification code" or "email + password" sign-in (provided that these two sign-in methods are enabled in the sign-in experience).
+  In other words, only emails from domains that are NOT configured in the SSO connectors can use "email + verification code" or "email + password" sign-in (provided that these two sign-in methods are enabled in the Sign-up and sign-in).
   :::
 
 - **Sync user profiles**: Choose when to synchronize user profile information (e.g., avatar, name). The default behavior is "Only sync at first sign-in". "Always sync at each sign-in" is another choice for this field, but may lead to custom user data overwriting.
@@ -109,7 +109,7 @@ Please note the following settings:
 
 ## Enabling enterprise SSO \{#enabling-enterprise-sso}
 
-1. Navigate to: <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in experience > Sign-up and sign-in</CloudLink>.
+1. Navigate to: <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in & account > Sign-up and sign-in</CloudLink>.
 2. Enable the "Enterprise SSO" toggle.
 3. Save changes.
 

docs/connectors/sms-connectors/README.mdx

@@ -134,10 +134,10 @@ To ensure the stability of your service, Cloud users can create a [dev tenant](/
 
 Once you add and configure the SMS connector, you can enable phone-based authentication flows:
 
-- [**Set sign-up methods**](/end-user-flows/sign-up-and-sign-in/sign-up): Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Sign-in experience > Sign-up and sign-in</CloudLink>. In the sign-up section, add "Phone number" or "Email address or phone number" as the identifier. Note: Phone number verification is mandatory during sign-up.
+- [**Set sign-up methods**](/end-user-flows/sign-up-and-sign-in/sign-up): Go to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Sign-in & account > Sign-up and sign-in</CloudLink>. In the sign-up section, add "Phone number" or "Email address or phone number" as the identifier. Note: Phone number verification is mandatory during sign-up.
 - [**Set sign-in methods**](/end-user-flows/sign-up-and-sign-in/sign-in): In the sign-in section, add "Phone number" as a sign-in method. Choose between password and SMS verification code for authentication. Click "Add another" for additional options.
 - [**Set up forgot password**](/end-user-flows/sign-up-and-sign-in/reset-password): In the sign-in section, if password sign-in is enabled, you'll see the "Forgot password" setting. Enable "Phone verification code" to allow password resets via SMS.
-- [**Set up SMS for MFA**](/end-user-flows/mfa/sms-mfa): Go to <CloudLink to="/mfa">Sign-in experience > Multi-factor auth</CloudLink>. Enable "SMS verification code" as a second factor for enhanced security.
+- [**Set up SMS for MFA**](/end-user-flows/mfa/sms-mfa): Go to <CloudLink to="/mfa">Console &gt; Multi-factor auth</CloudLink>. Enable "SMS verification code" as a second factor for enhanced security.
 - [**Set up account settings**](/end-user-flows/account-settings/by-account-api#manage-phone): Use the [Account API](/end-user-flows/account-settings/by-account-api) to customize your Account Center and allow users to manage their phone numbers.
 
 :::warning

docs/connectors/social.mdx

@@ -137,9 +137,9 @@ Please note the following settings:
 
 ## Enable social sign-in \{#enable-social-sign-in}
 
-Once you create a social connector successfully, you can enable it as a Social login button (e.g., Continue with Google) in Sign-in Experience.
+Once you create a social connector successfully, you can enable it as a Social login button (e.g., Continue with Google) in Sign-up and sign-in.
 
-1. Navigate to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in experience > Sign-up and sign-in</CloudLink>.
+1. Navigate to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in & account > Sign-up and sign-in</CloudLink>.
 2. (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
 3. Add configured social connectors to the "Social sign-in" section.
 4. Reorder connectors as needed.

docs/customization/README.mdx

@@ -23,7 +23,7 @@ Start with our pre-built UI components and customize essential brand elements. C
       label: 'Match your brand',
       href: '/customization/match-your-brand',
       description:
-        'Learn how to customize the basic brand elements for a ready-to-use sign-in experience.',
+        'Learn how to customize the basic brand elements for a ready-to-use sign-in experience and account center.',
       customProps: {
         icon: <CustomizationIcon />,
       },

docs/customization/bring-your-ui/README.mdx

@@ -50,7 +50,7 @@ Proceed with caution when using this feature in production, since it will immedi
 
 :::
 
-1. Navigate to <CloudLink to="/sign-in-experience/branding">Console > Sign-in experience > Brandin > Bring your UI</CloudLink>.
+1. Navigate to <CloudLink to="/sign-in-experience/branding">Console > Sign-in & account > Branding > Bring your UI</CloudLink>.
 2. Click to select or drag and drop your zip file created in the previous step, and the upload process will start automatically.
 3. Once the upload is complete, save the changes, and your custom UI will be served immediately.
 4. The "Sign-in preview" window will be disabled when you use your custom sign-in UI. However, you can still click the "[Live preview](/customization/live-preview)" button to test your custom sign-in page in a new opened browser tab.

docs/customization/bring-your-ui/debug-and-test-your-custom-ui-locally.mdx

@@ -7,7 +7,7 @@ import Tabs from '@theme/Tabs';
 
 # Debug and test your custom UI locally
 
-For Logto Cloud users, We've made it easy to let you "Bring your own UI" to Logto. Cloud users can now upload a zip file containing the custom UI assets in <CloudLink to="/sign-in-experience/branding">Console > Sign-in experience > Branding > Bring your UI</CloudLink> (Check out the [Bring your UI](/customization/bring-your-ui) page for more details.)
+For Logto Cloud users, we've made it easy to let you "Bring your own UI" to Logto. Cloud users can now upload a zip file containing the custom UI assets in <CloudLink to="/sign-in-experience/branding">Console > Sign-in & account > Branding > Bring your UI</CloudLink> (Check out the [Bring your UI](/customization/bring-your-ui) page for more details.)
 
 However, when developing such custom UI pages, users want to test and debug the code locally, before uploading to Logto Cloud. This CLI command helps you set up a local tunnel and connect the following 3 entities together:
 your Logto cloud auth endpoint, your application, and your custom sign-in UI.

docs/customization/custom-css.mdx

@@ -8,7 +8,7 @@ If our [fine-tuning UI](/customization/match-your-brand) doesn’t fully align w
 
 ## Custom CSS in Logto Console \{#custom-css-in-logto-console}
 
-1. Go to <CloudLink to="/sign-in-experience/branding">Console > Sign-in experience > Branding > Custom CSS</CloudLink>.
+1. Go to <CloudLink to="/sign-in-experience/branding">Console > Sign-in & account > Branding > Custom CSS</CloudLink>.
 2. Editing CSS code in the left editor, it will render lively in the right preview modal immediately. Note: the code editor only supports the CSS code so far. Not HTML or Javascript.
 3. Saving changes.
 4. Don’t forget to click the “[Live Preview](/customization/live-preview)” button to check the changes on all pages.

docs/customization/live-preview.mdx

@@ -9,7 +9,7 @@ You can use the **Live preview** feature for convenient testing of your sign-in
 
 ## Live preview \{#live-preview}
 
-Navigating to <CloudLink to="/sign-in-experience">Console > Sign-in experience</CloudLink>" and clicking the "Live preview" button in the top right corner will open a new browser tab with a fully functional demo of Logto's capabilities. This demo showcases our experience design approach for sign-in and sign-up flows. It is highly customizable and can be seamlessly integrated into your application.
+Navigating to <CloudLink to="/sign-in-experience/sign-up-and-sign-in">Console > Sign-in & account > Sign-up and sign-in</CloudLink>" and clicking the "Live preview" button in the top right corner will open a new browser tab with a fully functional demo of Logto's capabilities. This demo showcases our experience design approach for sign-in and sign-up flows. It is highly customizable and can be seamlessly integrated into your application.
 
 :::note