style alignment pass, proofs & edits (#2686)

* style alignment pass, proofs & edits

* indentation fix

* standardization round

* sentence casing for navs

* qa over prev

* qa over prev

* qa over prev

* qa over prev

* restore config to retrigger bot moaning

* Update embedded-wallets/features/wallet-pregeneration.mdx

Co-authored-by: Yashovardhan Agrawal <yashovardhan.agrawal@gmail.com>

---------

Co-authored-by: Yashovardhan Agrawal <yashovardhan.agrawal@gmail.com>

Author: m4sterbunny

embedded-wallets/authentication/README.mdx

@@ -21,7 +21,7 @@ The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plu
 
 Embedded Wallets supports a wide range of authentication options, enabling developers to meet the needs of diverse user bases and platform requirements.
 
-### Native email & SMS login
+### Native email and SMS login
 
 Provides passwordless log in via one-time passcodes (OTP)/ magic links sent to the user's [email address](/embedded-wallets/authentication/basic-logins/email-passwordless) or [phone number](/embedded-wallets/authentication/basic-logins/sms-otp). This method is widely accessible and especially useful for onboarding users unfamiliar with Web3 or crypto wallets.
 

embedded-wallets/authentication/basic-logins/email-passwordless.mdx

@@ -1,6 +1,6 @@
 ---
-title: Email Passwordless Login with Embedded Wallets
-sidebar_label: Email Passwordless
+title: Email passwordless Login with Embedded Wallets
+sidebar_label: Email passwordless
 description: 'Email Passwordless Login with Embedded Wallets | Embedded Wallets'
 ---
 
@@ -29,7 +29,7 @@ Embedded Wallets provides built-in support for email and SMS-based authenticatio
 
 To use this feature, developers must first enable **Email Passwordless** from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
-> By default, Web3Auth uses its own pre-configured credentials for email login.
+By default, Web3Auth uses its own pre-configured credentials for email login.
 
 :::
 
@@ -96,4 +96,6 @@ const web3AuthContextConfig: Web3AuthContextConfig = {
 export default web3AuthContextConfig
 ```
 
+## Next steps
+
 Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.

embedded-wallets/authentication/basic-logins/external-wallets.mdx

@@ -1,6 +1,6 @@
 ---
-title: External Wallets Login with Embedded Wallets
-sidebar_label: External Wallets
+title: External wallets login with Embedded Wallets
+sidebar_label: External wallets
 description: 'External Wallets Login with Embedded Wallets | Embedded Wallets'
 ---
 

embedded-wallets/authentication/basic-logins/sms-otp.mdx

@@ -1,5 +1,5 @@
 ---
-title: SMS OTP Login with Embedded Wallets
+title: SMS OTP login with Embedded Wallets
 sidebar_label: SMS OTP
 description: 'SMS OTP Login with Embedded Wallets | Embedded Wallets'
 ---
@@ -28,7 +28,7 @@ Web3Auth provides built-in support for email and SMS-based authentication, allow
 
 To use this feature, developers must first enable **SMS OTP** from the **Social Connections** section in the [dashboard](https://dashboard.web3auth.io).
 
-> By default, Web3Auth uses its own pre-configured credentials for SMS OTP login.
+By default, Web3Auth uses its own pre-configured credentials for SMS OTP login.
 
 :::
 
@@ -95,5 +95,6 @@ const web3AuthContextConfig: Web3AuthContextConfig = {
 
 export default web3AuthContextConfig
 ```
+## Next steps
 
 Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.

embedded-wallets/authentication/custom-connections/auth0.mdx

@@ -112,9 +112,13 @@ Follow these steps to create an Auth0 connection:
 
 ## Usage
 
-Since, the `Auth0 Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since the **Auth0 Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
 
-> Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+:::tip
+
+Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+
+:::
 
 ### Web
 

embedded-wallets/authentication/custom-connections/aws-cognito.mdx

@@ -44,9 +44,9 @@ Follow these steps to create a AWS Cognito connection:
 
 1. Visit the [dashboard](https://dashboard.web3auth.io).
 1. Go to the **Custom Connections** section.
-1. Click on the **Settings** icon near the `AWS Cognito` connection.
-1. Enter the `Cognito Connection ID`.
-1. Paste `https://cognito-idp.{REGION}.amazonaws.com/{USER_POOL_ID}/.well-known/jwks.json` as `JWKS Endpoint`.
+1. Click on the **Settings** icon near the **AWS Cognito** connection.
+1. Enter the **Cognito Connection ID**.
+1. Paste `https://cognito-idp.{REGION}.amazonaws.com/{USER_POOL_ID}/.well-known/jwks.json` as **JWKS Endpoint**.
 1. Paste a sample JWT Token to auto populate the best **JWT validations** possible.
 1. Select the **JWT user identifier**: `email`, `sub` or `custom`.
 1. (Optional) Toggle the case sensitivity of **User Identifier**.
@@ -55,7 +55,11 @@ Follow these steps to create a AWS Cognito connection:
    1. Next, type aud as a field and `APP_CLIENT_ID` as a value.
 1. Click on the **Add Connection** button to save the settings.
 
-> Note: Replace the `REGION`, `USER_POOL_ID` and `APP_CLIENT_ID` with your Cognito specific details.
+:::note
+
+Replace the `REGION`, `USER_POOL_ID`, and `APP_CLIENT_ID` with your Cognito-specific details.
+
+:::
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -71,9 +75,13 @@ Follow these steps to create a AWS Cognito connection:
 
 ## Usage
 
-Since, the `AWS Cognito Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since the **AWS Cognito Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
 
-> Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+:::tip
+
+Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+
+:::
 
 ### Log in with AWS Cognito
 

embedded-wallets/authentication/custom-connections/custom-jwt.mdx

@@ -40,13 +40,13 @@ To use this feature, developers must go to the **Custom Connections** tab in the
 
 Follow these steps to create a custom JWT connection:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+1. Visit the [Embedded Wallets dashboard](https://dashboard.web3auth.io).
 1. Go to the **Custom Connections** section.
 1. Click on the **Settings** icon near the **Custom Connection**.
-1. Enter the `Auth Connection ID`.
-1. Paste the `JWKS Endpoint`.
-1. Paste a sample `JWT Token` to auto populate the best **JWT validations** possible.
-1. Select the `JWT user identifier`: `email`, `sub` or `custom`.
+1. Enter the **Auth Connection ID**.
+1. Paste the **JWKS Endpoint**.
+1. Paste a sample **JWT Token** to auto populate the best **JWT validations** possible.
+1. Select the **JWT user identifier**: `email`, `sub` or `custom`.
 1. (Optional) Toggle the case sensitivity of `User Identifier`. 
 1. Click on **Add Custom Validations** to add validations manually.
    1. Type iss as a field and `your-issuer` as a value.
@@ -223,7 +223,7 @@ const jwt = await new jose.SignJWT({ 'urn:example:claim': true })
 console.log(jwt)
 
 // Verifying the JWT using Remote JWK Set.
-// This is just to show how the Verify works, look above to set-up custom jwt verifier on the Embedded Wallets Dashboard.
+// This is just to show how the Verify works, look above to set-up custom jwt verifier on the Embedded Wallets dashboard.
 // Check the steps below to see how once can generate the JWKS
 const JWKS = jose.createRemoteJWKSet(new URL('https://my-authz-server/.well-known/jwks.json'))
 
@@ -247,17 +247,21 @@ Check out the [troubleshooting page](/embedded-wallets/troubleshooting/jwt-error
 
 ## Usage
 
-Since, the **Custom Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since the **Custom Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
 
-> Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+:::tip
+
+Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+
+:::
 
 ### Log in with JWT
 
 <JwtLoginCustom />
 
 ## What are JWKS?
 
-JWKS stands for JSON Web Key Set. It is a set of keys containing the public keys that should be used to verify any JSON Web Token (JWT) issued by the authorization server and signed using the RS256 signing algorithm.
+JWKS stands for JSON Web Key Set. It's a set of keys containing the public keys that should be used to verify any JSON Web Token (JWT) issued by the authorization server and signed using the RS256 signing algorithm.
 
 ### How to create JWKS?
 
@@ -269,7 +273,7 @@ JWKS stands for JSON Web Key Set. It is a set of keys containing the public keys
 
 - If you are using your own custom JWT, you will need to convert your PEM file to JWKS.
 
-### How to convert PEM to JWKS?
+### How to convert PEM to JWKS
 
 If you're using `jose` or `jsonwebtoken` library, you can use the following steps to convert your PEM file to JWKS.
 
@@ -303,4 +307,4 @@ If you're using `jose` or `jsonwebtoken` library, you can use the following step
 
 4. To complete the process, you need to save the output as a `.json` file, host it on your server, and make sure it's publicly accessible.
 
-   This will give you the `JWKS Endpoint`, which is required when setting up a **Custom JWT Verifier** on the Embedded Wallets Dashboard.
+   This will give you the `JWKS Endpoint`, which is required when setting up a **Custom JWT Verifier** on the Embedded Wallets dashboard.

embedded-wallets/authentication/custom-connections/firebase.mdx

@@ -115,9 +115,13 @@ Follow these steps to create a Firebase connection:
 
 ## Usage
 
-Since, the **Firebase Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since the **Firebase Connection** details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
 
-> Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+:::tip 
+
+Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+
+:::
 
 ### Web
 

embedded-wallets/authentication/group-connections.mdx

@@ -1,6 +1,6 @@
 ---
-title: Group Connections
-sidebar_label: Group Connections
+title: Group connections
+sidebar_label: Group connections
 description: 'Group Connections | Embedded Wallets'
 image: 'img/metamaskog.jpg'
 ---
@@ -17,7 +17,7 @@ import GroupConnectionAuth0Implicit from '../sdk/react/advanced/_custom-authenti
 import GroupConnectionAuth0JWT from '../sdk/react/advanced/_custom-authentication-snippets/_grouped_auth_jwt_auth0.mdx'
 import GroupModal from '../sdk/react/advanced/_custom-authentication-snippets/_grouped_modal_connections.mdx'
 
-Group connections enable multiple login methods to be linked to the same on-chain user identity. This means that users logging in with different authentication providers (for example, **_Google and Email Passwordless_**) can still access the **same wallet address**—ensuring a unified user experience.
+Group connections enable multiple login methods to be linked to the same onchain user identity. This means that users logging in with different authentication providers (for example, **_Google and email passwordless_**) can still access the **same wallet address**—ensuring a unified user experience.
 
 :::note
 
@@ -80,9 +80,13 @@ Follow these steps:
 
 ## Usage
 
-Since, the group connections details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since the group connections details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
 
-> Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+:::tip
+
+Follow our [quickstart](/quickstart/?product=EMBEDDED_WALLETS&walletAggregatorOnly=NO&framework=REACT&stepIndex=0) to set up the basic flow.
+
+:::
 
 <Tabs>
   <TabItem value="modal" label="Modal Connection">

embedded-wallets/authentication/id-token.mdx

@@ -1,16 +1,16 @@
 ---
-title: Web3Auth Identity Token
-sidebar_label: Web3Auth Identity Token
+title: Embedded Wallets identity token
+sidebar_label: Web3Auth identity token
 image: 'img/metamaskog.jpg'
 description: 'Identity Token | Embedded Wallets'
 ---
 
 import TabItem from '@theme/TabItem'
 import Tabs from '@theme/Tabs'
 
-The **Identity Token** (ID Token) issued by Web3Auth is a JSON Web Token (JWT) that contains verified identity claims about the authenticated user. This token is signed using Web3Auth's private key and cannot be spoofed, allowing developers to trust the identity information presented by the client.
+The **Identity Token** (ID Token) issued by Embedded Wallets is a JSON Web Token (JWT) that contains verified identity claims about the authenticated user. This token is signed using Embedded Wallets' private key and cannot be spoofed, allowing developers to trust the identity information presented by the client.
 
-Once a user successfully authenticates via Web3Auth, the platform issues an ID token which can then be used to authorize client-to-server requests or verify ownership of associated wallet addresses.
+Once a user successfully authenticates via Embedded Wallets, the platform issues an ID token which can then be used to authorize client-to-server requests or verify ownership of associated wallet addresses.
 
 #### Purpose of the ID token
 
@@ -22,7 +22,7 @@ When making a backend request from the frontend, the client must include this ID
 
 ## ID token format
 
-Web3Auth tokens are ES256-signed JWTs containing various identity claims about the user.
+Embedded Wallets (previously Web3Auth) issues tokens as ES256-signed JWTs containing various identity claims about the user.
 
 A sample decoded token is shown below:
 
@@ -59,7 +59,7 @@ A sample decoded token is shown below:
 
 :::warning NOTE
 
-If the `Return user data in identity token` setting is disabled on the dashboard, personally identifiable information (PII) such as **email**, **name**, and **profileImage** will be omitted from the token.
+If the **Return user data in identity token** setting is disabled on the dashboard, personally identifiable information (PII) such as **email**, **name**, and **profileImage** will be omitted from the token.
 
 :::
 
@@ -373,7 +373,11 @@ try {
 }
 ```
 
-> The replace operation above ensures that any instances of '\n' in the stringified public key are replaced with actual newlines, per the PEM-encoded format.
+:::note
+
+The replace operation above ensures that any instances of '\n' in the stringified public key are replaced with actual newlines, per the PEM-encoded format.
+
+:::
 
 </TabItem>
 </Tabs>
@@ -384,7 +388,7 @@ If the token is valid, the payload will contain identity claims (such as, userId
 
 :::
 
-## Things to remember
+## Troubleshooting
 
 - The `iss` field in the token must be `https://api-auth.web3auth.io`.
 - The `aud` field must match your **Project Client ID**.