From 7454d20b2bbf2d822468e0c37d97e5797929c8d6 Mon Sep 17 00:00:00 2001
From: m4sterbunny <harrie.bickle-ext@consensys.net>
Date: Wed, 3 Dec 2025 15:24:22 +0000
Subject: [PATCH 1/3] style updates

---
 .../custom-connections/auth0.mdx              |   4 +-
 .../custom-connections/aws-cognito.mdx        |   2 +-
 .../custom-connections/custom-jwt.mdx         |   6 +-
 .../custom-connections/firebase.mdx           |   4 +-
 .../authentication/social-logins/discord.mdx  |   2 +-
 .../authentication/social-logins/facebook.mdx |   4 +-
 .../authentication/social-logins/google.mdx   |   2 +-
 .../authentication/social-logins/oauth.mdx    |  18 +-
 .../authentication/social-logins/twitch.mdx   |   2 +-
 embedded-wallets/connect-blockchain/README.md |   6 +-
 .../_initialize-web3auth-other-pnp.mdx        |   2 +-
 .../_evm-interaction.mdx                      |   3 +-
 .../_solana-provider-setup.mdx                |   2 +-
 .../connect-blockchain/evm/README.mdx         |   4 +-
 .../connect-blockchain/other/xrpl.mdx         |   6 +-
 .../connect-blockchain/solana/README.mdx      |   6 +-
 .../connect-blockchain/solana/react.mdx       |  10 +-
 .../connect-blockchain/solana/unity.mdx       |   8 +-
 .../connect-blockchain/solana/vue.mdx         |   8 +-
 embedded-wallets/dashboard/README.mdx         |  55 ++---
 .../dashboard/advanced/custom-chains.mdx      |   8 +-
 .../dashboard/advanced/key-export.mdx         | 155 +++++++-------
 .../dashboard/advanced/session-management.mdx | 196 ++++++++++--------
 .../dashboard/advanced/test-accounts.mdx      |  88 ++++----
 .../dashboard/advanced/user-details.mdx       |  54 ++---
 embedded-wallets/dashboard/analytics.mdx      |   4 +-
 embedded-wallets/dashboard/authentication.mdx |  36 ++--
 .../dashboard/chains-and-networks.mdx         |  20 +-
 embedded-wallets/dashboard/customization.mdx  |  52 ++---
 .../dashboard/project-settings.mdx            | 131 ++++++------
 .../dashboard/wallet-services.mdx             |  45 ++--
 embedded-wallets/dashboard/whitelist.mdx      | 161 ++++++++------
 32 files changed, 577 insertions(+), 527 deletions(-)

diff --git a/embedded-wallets/authentication/custom-connections/auth0.mdx b/embedded-wallets/authentication/custom-connections/auth0.mdx
index 9b38dc52da3..e5b8859dfb3 100644
--- a/embedded-wallets/authentication/custom-connections/auth0.mdx
+++ b/embedded-wallets/authentication/custom-connections/auth0.mdx
@@ -112,7 +112,7 @@ Follow these steps to create an Auth0 connection:
 
 ## Usage
 
-Since, the `Auth0 Connection` details are available from 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.
 
@@ -140,7 +140,7 @@ In your activity, create a `Web3Auth` instance with your Web3Auth project's conf
 web3Auth = Web3Auth(
   Web3AuthOptions(
     context = this,
-    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Developer Dashboard
+    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Web3Auth Dashboard
     network = Network.SAPPHIRE_MAINNET
     redirectUrl = Uri.parse("{YOUR_APP_PACKAGE_NAME}://auth"), // your app's redirect URL
     // focus-start
diff --git a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
index b7b3e35e26d..3e4d0e14a81 100644
--- a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
+++ b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
@@ -71,7 +71,7 @@ Follow these steps to create a AWS Cognito connection:
 
 ## Usage
 
-Since, the `AWS Cognito Connection` details are available from 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.
 
diff --git a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
index 7e5d9a84985..367be2fc5a1 100644
--- a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
+++ b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
@@ -65,7 +65,7 @@ Follow these steps to create a custom JWT connection:
   />
 </div>
 
-## Create JWT
+## Create a JWT
 
 To generate the JWT, developers may use a package of their choice. Web3Auth provides documentation and examples using both the `jsonwebtoken` and `jose` libraries.
 
@@ -123,7 +123,7 @@ npm i jsonwebtoken
 npm i jose
 ```
 
-### Generate JWT
+### Generate a JWT
 
 <Tabs
 defaultValue="jsonwebtoken"
@@ -247,7 +247,7 @@ Check out [**this troubleshooting page to fix those.**](/embedded-wallets/troubl
 
 ## Usage
 
-Since, the `Custom Connection` details are available from 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.
 
diff --git a/embedded-wallets/authentication/custom-connections/firebase.mdx b/embedded-wallets/authentication/custom-connections/firebase.mdx
index 2da918a032f..6a653220253 100644
--- a/embedded-wallets/authentication/custom-connections/firebase.mdx
+++ b/embedded-wallets/authentication/custom-connections/firebase.mdx
@@ -112,7 +112,7 @@ Follow these steps to create a Firebase connection:
 
 ## Usage
 
-Since, the `Firebase Connection` details are available from 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.
 
@@ -130,7 +130,7 @@ In your activity, create a `Web3Auth` instance with your Web3Auth project's conf
 web3Auth = Web3Auth(
   Web3AuthOptions(
     context = this,
-    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Developer Dashboard
+    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Web3Auth Dashboard
     network = Network.SAPPHIRE_MAINNET
     redirectUrl = Uri.parse("{YOUR_APP_PACKAGE_NAME}://auth"), // your app's redirect URL
     // focus-start
diff --git a/embedded-wallets/authentication/social-logins/discord.mdx b/embedded-wallets/authentication/social-logins/discord.mdx
index be2de0718e1..f2dcb90a1f7 100644
--- a/embedded-wallets/authentication/social-logins/discord.mdx
+++ b/embedded-wallets/authentication/social-logins/discord.mdx
@@ -71,7 +71,7 @@ Follow these steps to create a Discord connection:
 
 ## Usage
 
-Since, the `Discord Connection` details are available from Dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the `Discord 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.
 
diff --git a/embedded-wallets/authentication/social-logins/facebook.mdx b/embedded-wallets/authentication/social-logins/facebook.mdx
index b06ef9b03b1..5fa40fcbee5 100644
--- a/embedded-wallets/authentication/social-logins/facebook.mdx
+++ b/embedded-wallets/authentication/social-logins/facebook.mdx
@@ -76,10 +76,10 @@ Follow these steps to create a Facebook connection:
 
 ## Usage
 
-Since, the `Facebook Connection` details are available from Dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the `Facebook 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.
 
-### Implicit Login with Facebook
+### Implicit login with Facebook
 
 <ImplicitLoginFacebook />
diff --git a/embedded-wallets/authentication/social-logins/google.mdx b/embedded-wallets/authentication/social-logins/google.mdx
index 51972f71b1d..4dbeaad145c 100644
--- a/embedded-wallets/authentication/social-logins/google.mdx
+++ b/embedded-wallets/authentication/social-logins/google.mdx
@@ -71,7 +71,7 @@ Follow these steps to create a Google connection:
 
 ## Usage
 
-Since, the `Google Connection` details are available from Dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the `Google 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.
 
diff --git a/embedded-wallets/authentication/social-logins/oauth.mdx b/embedded-wallets/authentication/social-logins/oauth.mdx
index b02081b7f41..f67ae9f954d 100644
--- a/embedded-wallets/authentication/social-logins/oauth.mdx
+++ b/embedded-wallets/authentication/social-logins/oauth.mdx
@@ -34,7 +34,7 @@ To use this feature, please enable `X(Twitter)`, `Farcaster`, `Apple`, `GitHub`,
 
 ### Log in with X
 
-> Don't forget to enable X(Twitter) on the Dashboard.
+> Don't forget to enable X(Twitter) on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -63,7 +63,7 @@ function CustomConnectors() {
 
 ### Log in with Farcaster
 
-> Don't forget to enable Farcaster on the Dashboard.
+> Don't forget to enable Farcaster on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -92,7 +92,7 @@ function CustomConnectors() {
 
 ### Log in with Apple
 
-> Don't forget to enable Apple on the Dashboard.
+> Don't forget to enable Apple on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -121,7 +121,7 @@ function CustomConnectors() {
 
 ### Log in with GitHub
 
-> Don't forget to enable GitHub on the Dashboard.
+> Don't forget to enable GitHub on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -150,7 +150,7 @@ function CustomConnectors() {
 
 ### Log in with Reddit
 
-> Don't forget to enable Reddit on the Dashboard.
+> Don't forget to enable Reddit on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -179,7 +179,7 @@ function CustomConnectors() {
 
 ### Log in with Line
 
-> Don't forget to enable Line on the Dashboard.
+> Don't forget to enable Line on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -208,7 +208,7 @@ function CustomConnectors() {
 
 ### Log in with Kakao
 
-> Don't forget to enable Kakao on the Dashboard.
+> Don't forget to enable Kakao on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -237,7 +237,7 @@ function CustomConnectors() {
 
 ### Log in with LinkedIn
 
-> Don't forget to enable LinkedIn on the Dashboard.
+> Don't forget to enable LinkedIn on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
@@ -266,7 +266,7 @@ function CustomConnectors() {
 
 ### Log in with WeChat
 
-> Don't forget to enable WeChat on the Dashboard.
+> Don't forget to enable WeChat on the dashboard.
 
 ```tsx title="App.tsx"
 import { useWeb3AuthConnect } from '@web3auth/modal/react'
diff --git a/embedded-wallets/authentication/social-logins/twitch.mdx b/embedded-wallets/authentication/social-logins/twitch.mdx
index c1de7970a47..1b1d3443345 100644
--- a/embedded-wallets/authentication/social-logins/twitch.mdx
+++ b/embedded-wallets/authentication/social-logins/twitch.mdx
@@ -74,7 +74,7 @@ Follow these steps to create a Twitch connection:
 
 ## Usage
 
-Since, the `Twitch Connection` details are available from Dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the `Twitch 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.
 
diff --git a/embedded-wallets/connect-blockchain/README.md b/embedded-wallets/connect-blockchain/README.md
index 7f62cee73fa..edd99f471d4 100644
--- a/embedded-wallets/connect-blockchain/README.md
+++ b/embedded-wallets/connect-blockchain/README.md
@@ -24,15 +24,15 @@ The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plu
 
 ## Dashboard configuration
 
-The Embedded Wallets Web SDK (`@web3auth/modal`) from v10 onwards does not need any additional setup on the code side for blockchain connections. All of it is handled on the Dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
+The Embedded Wallets Web SDK (`@web3auth/modal`) from v10 onwards does not need any additional setup on the code side for blockchain connections. All of it is handled on the dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
 
 ![Chains on Dashboard](https://i.ibb.co/4nCD2GTJ/chains.gif)
 
-## Reference Guides for Blockchain Connections
+## Reference guides for blockchain connections
 
 You can check out the following guides we've written for certain blockchains. We have covered a wide variety of EVM and EVM Chains, supported by multiple Embedded Wallets providers.
 
-### Non EVM Chain guides
+### Non-EVM chain guides
 
 <OtherChains />
 
diff --git a/embedded-wallets/connect-blockchain/_initialize-web3auth-other-pnp.mdx b/embedded-wallets/connect-blockchain/_initialize-web3auth-other-pnp.mdx
index 7ef55616057..8990f265342 100644
--- a/embedded-wallets/connect-blockchain/_initialize-web3auth-other-pnp.mdx
+++ b/embedded-wallets/connect-blockchain/_initialize-web3auth-other-pnp.mdx
@@ -1,5 +1,5 @@
 Post v10 release, Web3Auth Web SDK does not need any additional setup on the code side for other
-chains: everything is handled on the Dashboard.
+chains: everything is handled on the dashboard.
 
 ```tsx
 import { Web3Auth, WEB3AUTH_NETWORK } from "@web3auth/modal";
diff --git a/embedded-wallets/connect-blockchain/_ios-connect-blockchain/_evm-interaction.mdx b/embedded-wallets/connect-blockchain/_ios-connect-blockchain/_evm-interaction.mdx
index d63dea6b8d6..15942f915c9 100644
--- a/embedded-wallets/connect-blockchain/_ios-connect-blockchain/_evm-interaction.mdx
+++ b/embedded-wallets/connect-blockchain/_ios-connect-blockchain/_evm-interaction.mdx
@@ -7,7 +7,8 @@ import SendTransactionSnippet from './_evm-send-transaction.mdx'
 
 ## Prerequisites
 
-This doc assumes you have already setup your project in Web3Auth Dashboard, and have integrated Web3Auth in your iOS app. If you haven't done that yet, you can learn how to [integrate Web3Auth in your iOS app](/embedded-wallets/sdk/ios/).
+- Project is set up in the Web3Auth dashboard
+- Web3Auth is [integrated in your iOS app](/embedded-wallets/sdk/ios/)
 
 ## Installation
 
diff --git a/embedded-wallets/connect-blockchain/_solana-provider-setup.mdx b/embedded-wallets/connect-blockchain/_solana-provider-setup.mdx
index 654f66fe3d3..1cb16edda22 100644
--- a/embedded-wallets/connect-blockchain/_solana-provider-setup.mdx
+++ b/embedded-wallets/connect-blockchain/_solana-provider-setup.mdx
@@ -46,7 +46,7 @@ import Tabs from "@theme/Tabs";
 ### Initializing and instantiating the Web3Auth SDK
 
 Post V10 release, Web3Auth Web SDK does not need any additional setup on the code side for
-Solana. All is handled on the Dashboard.
+Solana. All is handled on the dashboard.
 
 ```tsx
 import { Web3Auth, WEB3AUTH_NETWORK } from "@web3auth/modal";
diff --git a/embedded-wallets/connect-blockchain/evm/README.mdx b/embedded-wallets/connect-blockchain/evm/README.mdx
index 0928812c196..8bf2ff74f6f 100644
--- a/embedded-wallets/connect-blockchain/evm/README.mdx
+++ b/embedded-wallets/connect-blockchain/evm/README.mdx
@@ -18,10 +18,10 @@ You can check out the following guides we've written for selected blockchains. W
 
 ::::info
 
-With Embedded Wallets v10 onward, chains are already added to the Dashboard. You can use any chain from the extensive list of predefined chains and add more if needed by toggling them on. See our guide to [add custom chains](/embedded-wallets/dashboard/chains-and-networks/#adding-custom-networks) for more details.
+With Embedded Wallets v10 onward, chains are already added to the dashboard. You can use any chain from the extensive list of predefined chains and add more if needed by toggling them on. See our guide to [add custom chains](/embedded-wallets/dashboard/chains-and-networks/#adding-custom-networks) for more details.
 
 ::::
 
-The Embedded Wallets Web SDK(`@web3auth/modal`) from v10 onward does not need any additional setup on the code side for blockchain connections. All of it is handled on the Dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
+The Embedded Wallets Web SDK(`@web3auth/modal`) from v10 onward does not need any additional setup on the code side for blockchain connections. All of it is handled on the dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
 
 ![Chains on Dashboard](https://i.ibb.co/4nCD2GTJ/chains.gif)
diff --git a/embedded-wallets/connect-blockchain/other/xrpl.mdx b/embedded-wallets/connect-blockchain/other/xrpl.mdx
index 2c76aaf259f..1503d4507c5 100644
--- a/embedded-wallets/connect-blockchain/other/xrpl.mdx
+++ b/embedded-wallets/connect-blockchain/other/xrpl.mdx
@@ -82,7 +82,7 @@ npm install --save @web3auth/xrpl-provider
 ## Initializing provider
 
 Post V10 release, Web3Auth Web SDK does not need any additional setup on the code side for XRPL.
-All is handled on the Dashboard.
+All is handled on the dashboard.
 
 ```tsx
 import { Web3Auth, WEB3AUTH_NETWORK } from '@web3auth/modal'
@@ -136,7 +136,7 @@ try {
 }
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 ```tsx
 try {
@@ -196,7 +196,7 @@ try {
 }
 ```
 
-## Sign Message
+## Sign a message
 
 ```tsx
 try {
diff --git a/embedded-wallets/connect-blockchain/solana/README.mdx b/embedded-wallets/connect-blockchain/solana/README.mdx
index 76c97e77fbb..88485974a75 100644
--- a/embedded-wallets/connect-blockchain/solana/README.mdx
+++ b/embedded-wallets/connect-blockchain/solana/README.mdx
@@ -16,7 +16,7 @@ The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plu
 
 ::::
 
-## Platform Guides
+## Platform guides
 
 You can check out the following guides we've written for Solana across platforms.
 
@@ -89,10 +89,10 @@ export const Solana = [
 
 :::::info
 
-With Embedded Wallets v10 onwards, chains are already added to the Dashboard. You can use any chain from the extensive list of predefined chains and add more if needed by toggling them on. See our guide to [add custom chains](/embedded-wallets/dashboard/chains-and-networks/#adding-custom-networks) for more details.
+With Embedded Wallets v10 onwards, chains are already added to the dashboard. You can use any chain from the extensive list of predefined chains and add more if needed by toggling them on. See our guide to [add custom chains](/embedded-wallets/dashboard/chains-and-networks/#adding-custom-networks) for more details.
 
 :::::
 
-The Embedded Wallets Web SDK(`@web3auth/modal`) from v10 onwards does not need any additional setup on the code side for blockchain connections. All of it is handled on the Dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
+The Embedded Wallets Web SDK(`@web3auth/modal`) from v10 onwards does not need any additional setup on the code side for blockchain connections. All of it is handled on the dashboard. We can use any chain from the extensive list of predefined chains and add more if we need.
 
 ![Chains on Dashboard](https://i.ibb.co/4nCD2GTJ/chains.gif)
diff --git a/embedded-wallets/connect-blockchain/solana/react.mdx b/embedded-wallets/connect-blockchain/solana/react.mdx
index 68cece646d2..8c3beef626f 100644
--- a/embedded-wallets/connect-blockchain/solana/react.mdx
+++ b/embedded-wallets/connect-blockchain/solana/react.mdx
@@ -85,9 +85,9 @@ npm install @solana/web3.js
 | `useSignTransaction`        | Sign a Solana transaction (without sending). |
 | `useSolanaWallet`           | Access Solana wallet state and utilities.    |
 
-## Hook Usage Examples
+## Hook usage examples
 
-### Get Solana Wallet
+### Get Solana wallet
 
 ```tsx
 import { useSolanaWallet } from '@web3auth/modal/react/solana'
@@ -105,7 +105,7 @@ function SolanaWallet() {
 }
 ```
 
-### Sign Message
+### Sign a message
 
 ```tsx
 import { useSignMessage } from '@web3auth/modal/react/solana'
@@ -135,7 +135,7 @@ function SignMessage() {
 }
 ```
 
-### Sign Transaction
+### Sign a transaction
 
 ```tsx
 import { useSignTransaction } from '@web3auth/modal/react/solana'
@@ -174,7 +174,7 @@ function SignTransaction() {
 }
 ```
 
-### Sign and Send Transaction
+### Sign and send a transaction
 
 ```tsx
 import { useSignAndSendTransaction } from '@web3auth/modal/react/solana'
diff --git a/embedded-wallets/connect-blockchain/solana/unity.mdx b/embedded-wallets/connect-blockchain/solana/unity.mdx
index 8eff42f3131..33bb31c50f2 100644
--- a/embedded-wallets/connect-blockchain/solana/unity.mdx
+++ b/embedded-wallets/connect-blockchain/solana/unity.mdx
@@ -100,7 +100,7 @@ public class SolanaIntegration : MonoBehaviour
 }
 ```
 
-## Get Ed25519 Private Key
+## Get Ed25519 private key
 
 ```csharp
 // After successful Web3Auth login
@@ -110,7 +110,7 @@ string ed25519PrivateKey = await web3auth.GetEd25519PrivKey();
 byte[] privateKeyBytes = Convert.FromHexString(ed25519PrivateKey);
 ```
 
-## Create Solana Keypair
+## Create a Solana keypair
 
 Using the Magicblock Solana Unity SDK, you can create a keypair from the private key:
 
@@ -142,7 +142,7 @@ var balanceInSOL = balance.Result.Value / 1_000_000_000.0; // Convert lamports t
 Debug.Log($"Balance: {balanceInSOL} SOL");
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 ```csharp
 using Solana.Unity.Rpc.Models;
@@ -182,7 +182,7 @@ else
 }
 ```
 
-## Sign Message
+## Sign a message
 
 ```csharp
 // Sign a message with the private key
diff --git a/embedded-wallets/connect-blockchain/solana/vue.mdx b/embedded-wallets/connect-blockchain/solana/vue.mdx
index df5651305fd..864ce19d9bf 100644
--- a/embedded-wallets/connect-blockchain/solana/vue.mdx
+++ b/embedded-wallets/connect-blockchain/solana/vue.mdx
@@ -85,9 +85,9 @@ npm install @solana/web3.js
 | `useSignTransaction`        | Sign a Solana transaction (without sending). |
 | `useSolanaWallet`           | Access Solana wallet state and utilities.    |
 
-## Composable Usage Examples
+## Composable usage examples
 
-### Get Solana Wallet
+### Get Solana wallet
 
 ```vue
 <template>
@@ -105,7 +105,7 @@ npm install @solana/web3.js
 </script>
 ```
 
-### Sign Message
+### Sign a message
 
 ```vue
 <template>
@@ -135,7 +135,7 @@ npm install @solana/web3.js
 </script>
 ```
 
-### Sign Transaction
+### Sign a transaction
 
 ```vue
 <template>
diff --git a/embedded-wallets/dashboard/README.mdx b/embedded-wallets/dashboard/README.mdx
index bbe58f65152..18125f9932c 100644
--- a/embedded-wallets/dashboard/README.mdx
+++ b/embedded-wallets/dashboard/README.mdx
@@ -1,15 +1,15 @@
 ---
-title: Create a new project in the Dashboard
+title: Create a new project in the dashboard
 sidebar_label: Create a new project
 image: 'img/metamaskog.jpg'
-description: 'Create a new project in the Dashboard | MetaMask Embedded Wallets'
+description: 'Create a new project in the dashboard | MetaMask Embedded Wallets'
 ---
 
 import DashboardSignUpPage from '@site/static/img/embedded-wallets/w3a-dashboard/dashboard-signup.gif'
 
-To get started, visit the [Web3Auth Dashboard](https://dashboard.web3auth.io), log in using one of your social accounts or use your email address. You can use the Dashboard to manage your projects, configurations, wallet UI, and more for MetaMask Embedded Wallets (formerly Web3Auth).
+To get started, visit the [Web3Auth dashboard](https://dashboard.web3auth.io), log in using one of your social accounts or email address. You can use the dashboard to manage your projects, configurations, wallet UI, and more for MetaMask Embedded Wallets.
 
-While setting up your account, Web3Auth will prompt you to share some basic information about your organization.
+While setting up your account, you will be prompted to share some basic information about your organization.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -19,45 +19,48 @@ While setting up your account, Web3Auth will prompt you to share some basic info
   />
 </div>
 
-Once you've set up your account, you can use the Dashboard to manage your **projects** and **team**.
+Once you've set up your account, you can use the dashboard to manage your projects and team.
 
 :::tip
 
-Use the [Projects](https://dashboard.web3auth.io/organization) page of the Dashboard to create and manage new projects for your account. Resources, including wallets, authentication methods, and more are scoped to individual projects.
+Use the [projects](https://dashboard.web3auth.io/organization) page of the dashboard to create and manage new projects for your account. Resources, including wallets, authentication methods, and more are scoped to individual projects.
 
 :::
 
 ## Create a new project
 
-Before implementing any Embedded Wallet SDK, developers must create a new project in the Dashboard. This process generates a Client ID required for SDK integration.
+Before implementing any Embedded Wallet SDK, developers must create a new project in the Web3Auth Dashboard. This process generates a Client ID required for SDK integration.
 
-:::success Note
+:::important
 
-It is recommended to maintain separate projects for different environments (e.g., development, staging, production) to ensure optimal security of credentials.
+To ensure optimal security of credentials, it's recommended to maintain separate projects for different environments (such as development, staging, production).
 
 :::
 
-Login to the [Web3Auth Dashboard](https://dashboard.web3auth.io) and create a new project if you haven't already.
+Log in to the [Web3Auth Dashboard](https://dashboard.web3auth.io) and create a new project if you haven't already.
 
-## Get the Client ID
+## Get the client ID
 
-After creating a project, navigate to **Project Settings** and select the **General** tab to obtain the `Client ID`.
+After creating a project:
 
-The project comes pre-configured with default connections, chains and networks to facilitate faster integration with the SDKs.
+1. Navigate to **Project Settings**.
+2. Select the **General** tab to obtain the `Client ID`.
 
-## Dashboard Configuration
+The project comes pre-configured with default connections, chains, and networks to facilitate faster integration with the SDKs.
+
+## Dashboard configuration
 
 Once your project is created, you can configure various aspects of your integration through the dashboard:
 
-- **[Project Settings](./project-settings)** - Basic project information, credentials, and token verification
-- **[Whitelist Settings](./whitelist)** - Domain and URL authorization for enhanced security
-- **[Advanced Project Settings](./advanced/session-management)** - Advanced configuration options
-  - **[Session Management](./advanced/session-management)** - Session duration and behavior
-  - **[Test Accounts](./advanced/test-accounts)** - Development testing environment
-  - **[User Details in ID Token](./advanced/user-details)** - JWT token user data configuration
-  - **[Key Export Settings](./advanced/key-export)** - Private key export permissions
-- **[Chains and Networks](./chains-and-networks)** - Manage blockchain networks and custom chain configurations
-- **[Authentication](./authentication)** - Configure login methods, social connections, and custom authentication
-- **[Wallet Services](./wallet-services)** - Customize wallet UI and configure wallet features
-- **[Customization](./customization)** - Brand your login flow and customize the user experience
-- **[Analytics](./analytics)** - Monitor project usage and user engagement metrics
+- [Project settings](./project-settings) - Basic project information, credentials, and token verification
+- [Allowlist settings](./whitelist) - Domain and URL authorization for enhanced security
+- [Advanced project settings](./advanced/session-management) - Advanced configuration options
+  - [Session management](./advanced/session-management) - Session duration and behavior
+  - [Test accounts](./advanced/test-accounts) - Development testing environment
+  - [User details in ID Token](./advanced/user-details) - JWT token user data configuration
+  - [Key export settings](./advanced/key-export) - Private key export permissions
+- [Chains and networks](./chains-and-networks) - Manage blockchain networks and custom chain configurations
+- [Authentication](./authentication) - Configure login methods, social connections, and custom authentication
+- [Wallet services](./wallet-services) - Customize wallet UI and configure wallet features
+- [Customization](./customization) - Brand your login flow and customize the user experience
+- [Analytics](./analytics) - Monitor project usage and user engagement metrics
diff --git a/embedded-wallets/dashboard/advanced/custom-chains.mdx b/embedded-wallets/dashboard/advanced/custom-chains.mdx
index a4e1219b169..e982fde1686 100644
--- a/embedded-wallets/dashboard/advanced/custom-chains.mdx
+++ b/embedded-wallets/dashboard/advanced/custom-chains.mdx
@@ -1,6 +1,6 @@
 ---
-title: Add Custom Chains to the Dashboard
-sidebar_label: Add Custom Chains to the Dashboard
+title: Add Custom Chains to the dashboard
+sidebar_label: Add Custom Chains to the dashboard
 image: 'img/metamaskog.jpg'
 description: 'Add Custom Chains | Embedded Wallets'
 ---
@@ -15,7 +15,7 @@ The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plu
 
 ![Chains on Dashboard](https://i.ibb.co/4nCD2GTJ/chains.gif)
 
-## Add Custom Chains
+## Add custom chains
 
 To add a custom chain, we need to follow these steps:
 
@@ -27,7 +27,7 @@ To add a custom chain, we need to follow these steps:
 
 ![Adding Custom Chain](/img/embedded-wallets/connect-blockchain/add-a-chain-dashboard-v2.png)
 
-## Add Chains in Code (Web SDK)
+## Add chains in code (Web SDK)
 
 While chains can be configured through the dashboard, you can also override these settings in your code by specifying custom chains during SDK initialization.
 
diff --git a/embedded-wallets/dashboard/advanced/key-export.mdx b/embedded-wallets/dashboard/advanced/key-export.mdx
index f2c2da407f0..f5ad47f6431 100644
--- a/embedded-wallets/dashboard/advanced/key-export.mdx
+++ b/embedded-wallets/dashboard/advanced/key-export.mdx
@@ -7,7 +7,7 @@ description: 'Configure private key export permissions in Web3Auth Dashboard | E
 
 import ProjectSettingsAdvanced from '@site/static/img/embedded-wallets/w3a-dashboard/project-settings-advanced.png'
 
-The **Key Export Settings** allow you to control whether users can programmatically export their private keys using the Web3Auth SDK. This setting provides flexibility for advanced use cases while maintaining security control over sensitive cryptographic material.
+The key export settings allow you to control whether users can programmatically export their private keys using the Web3Auth SDK. This setting provides flexibility for advanced use cases while maintaining security control over sensitive cryptographic material.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -17,36 +17,37 @@ The **Key Export Settings** allow you to control whether users can programmatica
   />
 </div>
 
-## Key Export Overview
+## Key export overview
 
 Private key export functionality allows applications to retrieve users' private keys programmatically through the Web3Auth SDK. This capability enables advanced use cases such as wallet migration, multi-platform support, and integration with external services, while requiring careful consideration of security implications.
 
-### Export Methods
+### Export methods
 
-**Programmatic Export (Configurable):**
+Manual export is always supported to ensure that users retain autonomy over their keys while programmatic export may be configured.
 
-- Access via `private_key` JSON-RPC method
-- Requires explicit user consent
-- Can be enabled/disabled per project
-- Controlled through dashboard settings
+#### Manual export
 
-**Manual Export (Always Available):**
-
-- Built-in Web3Auth wallet interface
+- **Can't be disabled**
+- Built into the Web3Auth wallet interface
 - User-initiated through wallet UI
-- Cannot be disabled
-- Provides user autonomy over their keys
 
-## Configuring Key Export
+### Programmatic export
+
+Programmatic export is configurable, providing: 
+
+- Access via the `private_key` JSON-RPC method
+- Requires explicit user consent
+- Can be enabled/disabled per project
+- Controlled through dashboard settings
 
-### Enabling Programmatic Export
+#### Enabling programmatic key export
 
-1. **Navigate to Project Settings** → **Advanced** → **Key Export**
-2. **Locate "Enable Key Export"** toggle
-3. **Enable the setting** to allow programmatic access
-4. **Save configuration** to apply changes
+1. Navigate to **Project Settings** → **Advanced** → **Key Export**.
+2. Locate **Enable Key Export** toggle.
+3. Enable the setting to allow programmatic access.
+4. Save configuration to apply changes.
 
-### Disabling Programmatic Export
+#### Disabling programmatic export
 
 When disabled:
 
@@ -55,11 +56,11 @@ When disabled:
 - Enhanced security for applications that don't require key access
 - Recommended for most consumer applications
 
-## Implementation Guide
+## Implementation guide
 
-### Programmatic Key Retrieval
+### Programmatic key retrieval
 
-**Basic Implementation:**
+Basic Implementation:
 
 ```javascript
 // Ensure user is authenticated
@@ -83,7 +84,7 @@ try {
 }
 ```
 
-**Secure Implementation Pattern:**
+Secure Implementation Pattern:
 
 ```javascript
 class SecureKeyManager {
@@ -118,9 +119,9 @@ class SecureKeyManager {
 }
 ```
 
-### User Consent Flow
+### User consent flow
 
-**Best Practices for User Consent:**
+Best Practices for User Consent:
 
 ```javascript
 async function requestKeyExport() {
@@ -147,11 +148,11 @@ async function requestKeyExport() {
 }
 ```
 
-## Use Cases for Key Export
+## Use cases for key export
 
-### Wallet Migration
+### Wallet migration
 
-**Cross-Platform Migration:**
+Cross-Platform Migration:
 
 ```javascript
 // Export from Web3Auth for import into other wallets
@@ -174,9 +175,9 @@ async function migrateToExternalWallet() {
 }
 ```
 
-### Multi-Chain Support
+### Multi-chain support
 
-**Cross-Chain Key Derivation:**
+Cross-chain key derivation:
 
 ```javascript
 async function deriveKeysForMultipleChains() {
@@ -194,9 +195,9 @@ async function deriveKeysForMultipleChains() {
 }
 ```
 
-### Advanced Integrations
+### Advanced integrations
 
-**DeFi Protocol Integration:**
+DeFi protocol integration:
 
 ```javascript
 async function integrateDeFiProtocol() {
@@ -214,9 +215,9 @@ async function integrateDeFiProtocol() {
 }
 ```
 
-### Backup and Recovery
+### Backup and recovery
 
-**Secure Backup Creation:**
+Secure backup creation:
 
 ```javascript
 async function createSecureBackup() {
@@ -233,19 +234,19 @@ async function createSecureBackup() {
 }
 ```
 
-## Security Considerations
+## Security considerations
 
-### Application Security
+### Application security
 
-**Key Handling Best Practices:**
+Key handling best practices:
 
-- **Minimize Exposure**: Retrieve keys only when necessary
-- **Secure Transmission**: Use HTTPS and encrypted channels
-- **Memory Management**: Clear private keys from memory immediately after use
-- **No Persistent Storage**: Never store private keys in databases or local storage
-- **Audit Logging**: Log key export events for security monitoring
+- Minimize exposure: Retrieve keys only when necessary
+- Secure transmission: Use HTTPS and encrypted channels
+- Memory management: Clear private keys from memory immediately after use
+- No persistent storage: **Never** store private keys in databases or local storage
+- Audit logging: Log key export events for security monitoring
 
-**Implementation Security:**
+#### Implementation security
 
 ```javascript
 class SecureKeyHandler {
@@ -278,16 +279,16 @@ class SecureKeyHandler {
 }
 ```
 
-### User Education
+### User education
 
-**Security Awareness:**
+Security awareness is vital:
 
 - Educate users about private key security
 - Explain the implications of key export
 - Provide secure storage recommendations
 - Warn against sharing private keys
 
-**User Interface Guidelines:**
+#### User interface guidelines
 
 ```javascript
 const securityWarnings = {
@@ -307,20 +308,22 @@ const securityWarnings = {
 }
 ```
 
-### Regulatory Compliance
+### Regulatory compliance
 
-**Compliance Considerations:**
+It's vital to comply with regulations, always consider:
 
-- **Data Protection**: Ensure key export complies with privacy regulations
-- **Audit Requirements**: Maintain records of key export events
-- **User Consent**: Obtain explicit consent for key export operations
-- **Jurisdictional Laws**: Consider local regulations regarding cryptographic material
+- Data protection: Ensure key export complies with privacy regulations
+- Audit requirements: Maintain records of key export events
+- User consent: Obtain explicit consent for key export operations
+- Jurisdictional laws: Consider local regulations regarding cryptographic material
 
-## Monitoring and Analytics
+## Monitoring and analytics
 
-### Export Event Tracking
+### Export event tracking
 
-**Analytics Implementation:**
+#### Analytics implementation
+
+Consider sending a structured analytics event whenever a user exports a private key:
 
 ```javascript
 async function trackKeyExport(userId, exportReason) {
@@ -335,7 +338,9 @@ async function trackKeyExport(userId, exportReason) {
 }
 ```
 
-**Security Monitoring:**
+#### Security monitoring
+
+Consider monitoring key export attempts to flag suspicious patterns such as repeated exports:
 
 ```javascript
 class KeyExportMonitor {
@@ -365,27 +370,27 @@ class KeyExportMonitor {
 }
 ```
 
-## Alternative Approaches
+## Alternative approaches
 
-### When to Disable Key Export
+### Disable key export
 
-**Recommended for:**
+Consider disabling key export for:
 
 - Consumer-facing applications
 - Applications handling high-value assets
 - Regulated financial services
 - Applications with strict security requirements
 
-**Alternative Solutions:**
+These alternative approaches can be leveraged to enable users to sign transactions without exposing or exporting private keys:
 
-- Use Web3Auth's built-in wallet interface
-- Implement transaction signing without key exposure
+- Web3Auth's built-in wallet interface
 - Use multi-signature schemes
 - Leverage Web3Auth's session-based authentication
+- Implement transaction signing without key exposure (see example below)
 
-### Transaction-Only Access
+### Transaction-only access
 
-**Secure Transaction Pattern:**
+Use `web3auth.provider.request` to sign transactions directly through Embedded Wallets without exposing the private key:
 
 ```javascript
 // Sign transactions without exposing private key
@@ -402,29 +407,27 @@ async function signTransaction(transactionData) {
 
 ## Troubleshooting
 
-### Common Issues
-
-**Key Export Disabled:**
+### Key export disabled
 
 - Verify setting is enabled in dashboard
 - Check project configuration
 - Confirm user permissions
 
-**Export Method Not Available:**
+### Export method not available
 
 - Ensure Web3Auth SDK is properly initialized
 - Verify user is authenticated
 - Check for browser compatibility issues
 
-**User Consent Failures:**
+### User consent failures
 
 - Implement proper consent flow
 - Provide clear security information
 - Handle user rejection gracefully
 
-### Error Handling
+### Error handling
 
-**Robust Error Management:**
+Troubleshooting is more quickly resolved with robust error management:
 
 ```javascript
 async function safeKeyExport() {
@@ -445,8 +448,8 @@ async function safeKeyExport() {
 }
 ```
 
-## Next Steps
+## Next steps
 
-- **[User Details in ID Token](../user-details)** - Configure user data in JWT tokens
-- **[Session Management](../session-management)** - Control session duration and behavior
-- **[Project Settings](../../project-settings)** - Configure basic project information
+- [User details in ID token](../user-details): Configure user data in JWT tokens
+- [Session management](../session-management): Control session duration and behavior
+- [Project settings](../../project-settings): Configure basic project information
diff --git a/embedded-wallets/dashboard/advanced/session-management.mdx b/embedded-wallets/dashboard/advanced/session-management.mdx
index c6da76ca9e5..88138697e26 100644
--- a/embedded-wallets/dashboard/advanced/session-management.mdx
+++ b/embedded-wallets/dashboard/advanced/session-management.mdx
@@ -6,8 +6,10 @@ description: 'Configure session duration and behavior in Web3Auth Dashboard | Em
 ---
 
 import ProjectSettingsAdvanced from '@site/static/img/embedded-wallets/w3a-dashboard/project-settings-advanced.png'
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
 
-The **Session Management** settings allow you to customize session lifetime and behavior for your Web3Auth integration. These settings determine how long user sessions remain active before requiring re-authentication, providing flexibility to balance security requirements with user experience.
+The session management settings allow you to customize session lifetime and behavior for your Web3Auth integration. These settings determine how long user sessions remain active before requiring re-authentication, providing flexibility to balance security requirements with user experience.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -17,198 +19,208 @@ The **Session Management** settings allow you to customize session lifetime and
   />
 </div>
 
-## Session Duration Overview
+## Session duration overview
 
 Session duration controls how long a user's authentication session remains valid before automatic expiration. This setting directly impacts both security posture and user convenience, making it a critical configuration for production applications.
 
-### Default Configuration
+### Default configuration
 
-- **Default Duration**: 1 day (24 hours)
-- **Minimum Duration**: 1 second
-- **Maximum Duration**: 30 days (720 hours)
-- **Granularity**: Configurable down to the second
+You may configure the session duration down to the second:
 
-## Configuring Session Duration
+- Default duration: 1 day (24 hours)
+- Minimum duration: 1 second
+- Maximum duration: 30 days (720 hours)
 
-### Setting Session Lifetime
+## Configuring session duration
 
-1. **Navigate to Project Settings** → **Advanced** → **Session Management**
-2. **Locate Session Duration** setting
-3. **Enter desired duration** in the provided format
-4. **Save configuration** to apply changes
+### Setting session lifetime
 
-### Duration Format Options
+1. Navigate to **Project Settings** → **Advanced** → **Session Management**.
+2. At the **Session Duration** setting, enter the desired duration in the provided format:
 
-**Time Units Supported:**
+<Tabs>
+<TabItem value="time-units" label="Supported time units">
 
-- **Seconds**: 1s, 30s, 60s
-- **Minutes**: 1m, 30m, 60m
-- **Hours**: 1h, 12h, 24h
-- **Days**: 1d, 7d, 30d
+- Seconds: 1s, 30s, 60s
+- Minutes: 1m, 30m, 60m
+- Hours: 1h, 12h, 24h
+- Days: 1d, 7d, 30d
 
-**Example Configurations:**
+</TabItem>
+<TabItem value="examples" label="Example configurations">
 
 ```
 30m    # 30 minutes
 2h     # 2 hours
 1d     # 1 day (default)
 7d     # 7 days
-30d    # 30 days (maximum)
+30d     # 30 days (maximum)
 ```
 
-## Security Considerations
+</TabItem>
+</Tabs>
 
-### Short Session Durations
+3. Save the configuration to apply your changes.
 
-**Benefits:**
+## Security considerations
 
-- **Enhanced Security**: Reduced exposure window if credentials are compromised
-- **Compliance**: Meets strict security requirements for sensitive applications
-- **Risk Mitigation**: Limits potential damage from unauthorized access
-- **Regular Validation**: Ensures users are actively using the application
+### Short session durations
 
-**Use Cases:**
+Maintaining short sessions supports:
 
-- Financial applications
-- Healthcare systems
-- Administrative interfaces
-- High-security environments
+- Enhanced security: Reduced exposure window if credentials are compromised
+- Compliance: Meets strict security requirements for sensitive applications
+- Risk mitigation: Limits potential damage from unauthorized access
+- Regular validation: Ensures users are actively using the application
 
-**Recommended Durations:**
+The following durations are typical for the stated use cases:
 
-- **High Security**: 30m - 2h
-- **Financial Apps**: 1h - 4h
-- **Admin Panels**: 2h - 8h
+- High security: 30m-2h
+- Financial apps: 1-4h
+- Admin panels: 2-8h
 
-### Long Session Durations
+### Long session durations
 
-**Benefits:**
+In some use cases longer session durations can benefit the user:
 
-- **Improved UX**: Reduces authentication friction for users
-- **Productivity**: Minimizes workflow interruptions
-- **User Retention**: Decreases abandonment due to re-authentication
-- **Convenience**: Better for applications with frequent usage
+- Improved UX: Reduces authentication friction for users
+- Productivity: Minimizes workflow interruptions
+- Retention: Decreases abandonment due to re-authentication
+- Convenience: Better for applications with frequent usage
 
-**Use Cases:**
+The following durations are typical for the stated use cases:
 
-- Consumer applications
-- Gaming platforms
-- Content consumption apps
-- Productivity tools
+- Consumer Apps: 7-30d
+- Gaming: 14-30d
+- Content apps: 7-30d
 
-**Recommended Durations:**
+#### Application-specific recommendations
 
-- **Consumer Apps**: 7d - 30d
-- **Gaming**: 14d - 30d
-- **Content Apps**: 7d - 30d
+##### Web applications
 
-## Application-Specific Recommendations
-
-### Web Applications
-
-**Standard Web Apps:**
+<Tabs>
+<TabItem value="standard" label="Standard web apps">
 
 ```
-Session Duration: 1d - 7d
+Session Duration: 1-7d
 Rationale: Balance between security and convenience
 ```
 
-**Single Page Applications (SPAs):**
+</TabItem>
+<TabItem value="spa" label="Single page applications (SPAs)">
 
 ```
-Session Duration: 4h - 1d
+Session Duration: 4h-1d
 Rationale: Active browsing sessions with automatic renewal
 ```
 
-**Progressive Web Apps (PWAs):**
+</TabItem>
+<TabItem value="pwa" label="Progressive web apps (PWAs)">
 
 ```
-Session Duration: 7d - 30d
+Session Duration: 7-30d
 Rationale: App-like experience with persistent sessions
 ```
 
-### Mobile Applications
+</TabItem>
+</Tabs>
+
+##### Mobile applications
 
-**Native Mobile Apps:**
+<Tabs>
+<TabItem value="native" label="Native mobile apps">
 
 ```
-Session Duration: 14d - 30d
+Session Duration: 14-30d
 Rationale: Device-based security with biometric re-authentication
 ```
 
-**Mobile Games:**
+</TabItem>
+<TabItem value="mobile-games" label="Mobile games">
 
 ```
 Session Duration: 30d
 Rationale: Seamless gaming experience with maximum convenience
 ```
 
-**Financial Mobile Apps:**
+</TabItem>
+<TabItem value="financial" label="Financial mobile apps">
 
 ```
-Session Duration: 1h - 4h
+Session Duration: 1-4h
 Rationale: High security requirements with biometric backup
 ```
 
-### Gaming Applications
+</TabItem>
+</Tabs>
 
-**Casual Games:**
+##### Gaming applications
+
+<Tabs>
+<TabItem value="casual" label="Casual games">
 
 ```
 Session Duration: 30d
 Rationale: Minimal friction for entertainment applications
 ```
 
-**Competitive Games:**
+</TabItem>
+<TabItem value="competitive" label="Competitive games">
 
 ```
-Session Duration: 14d - 30d
+Session Duration: 14-30d
 Rationale: Balance between convenience and account security
 ```
 
-**Gaming Platforms:**
+</TabItem>
+<TabItem value="platforms" label="Gaming platforms">
 
 ```
-Session Duration: 7d - 30d
+Session Duration: 7-30d
 Rationale: Platform-level access with game-specific security
 ```
 
-## Advanced Session Behaviors
+</TabItem>
+</Tabs>
+
+## Advanced session behaviors
 
-### Session Renewal
+### Session renewal
 
 Web3Auth sessions can be renewed through various mechanisms:
 
-**Automatic Renewal:**
+#### Automatic Renewal
 
 - Sessions automatically extend on user activity
 - Background refresh maintains active sessions
 - Seamless experience without user intervention
 
-**Manual Renewal:**
+#### Manual Renewal
 
 - Explicit user action required for session extension
 - Greater control over session lifecycle
 - Suitable for high-security environments
 
-### Session Termination
+### Session termination
+
+Sessions may be terminated automatically, or manually. 
 
-**Automatic Termination Events:**
+#### Automatic Termination Events
 
 - Session duration expiry
 - Extended inactivity periods
 - Security-triggered logout
 - Device/browser changes
 
-**Manual Termination:**
+#### Manual Termination
 
 - User-initiated logout
 - Administrative session termination
 - Forced logout from dashboard
 
-## Implementation Considerations
+## Implementation considerations
 
-### Frontend Integration
+### Frontend integration
 
 **Session Status Monitoring:**
 
@@ -236,7 +248,7 @@ setInterval(async () => {
 }, 60000) // Check every minute
 ```
 
-### Backend Validation
+### Backend validation
 
 **Token Validation:**
 
@@ -261,13 +273,13 @@ function validateSession(token) {
 }
 ```
 
-## Security Best Practices
+## Security best practices
 
-### Session Security Guidelines
+### Session security guidelines
 
 **Token Management:**
 
-- Store session tokens securely (HttpOnly cookies for web)
+- Store session tokens securely (HTTPOnly cookies for web)
 - Implement proper token rotation
 - Use secure transmission (HTTPS only)
 - Clear tokens on logout
@@ -286,7 +298,7 @@ function validateSession(token) {
 - Provide session management UI
 - Enable remote session termination
 
-### Compliance Requirements
+### Compliance requirements
 
 **Industry Standards:**
 
@@ -304,9 +316,9 @@ function validateSession(token) {
 | Medium     | 1-7 days             | Weekly            |
 | Low        | 7-30 days            | Monthly           |
 
-## Troubleshooting Session Issues
+## Troubleshooting session issues
 
-### Common Session Problems
+### Common session problems
 
 **Premature Session Expiry:**
 
@@ -329,7 +341,7 @@ function validateSession(token) {
 - Review session renewal logic
 - Test different browser/app configurations
 
-### Debugging Tools
+### Debugging tools
 
 **Session Inspection:**
 
@@ -353,7 +365,7 @@ console.log('Issued At:', new Date(decoded.payload.iat * 1000))
 console.log('Expires At:', new Date(decoded.payload.exp * 1000))
 ```
 
-## Next Steps
+## Next steps
 
 - **[Key Export Settings](../key-export)** - Configure private key export permissions
 - **[User Details in ID Token](../user-details)** - Manage user data in JWT tokens
diff --git a/embedded-wallets/dashboard/advanced/test-accounts.mdx b/embedded-wallets/dashboard/advanced/test-accounts.mdx
index b1e047f9e33..64e658f9fd2 100644
--- a/embedded-wallets/dashboard/advanced/test-accounts.mdx
+++ b/embedded-wallets/dashboard/advanced/test-accounts.mdx
@@ -24,79 +24,79 @@ Enabling this option permits login through the provided email, OTP code, or phon
   />
 </div>
 
-## Enabling Test Accounts
+## Enabling test accounts
 
-Test Accounts can be enabled through the Web3Auth Dashboard:
+Test Accounts can be enabled through the Web3Auth dashboard:
 
-1. Navigate to your project in the [Web3Auth Dashboard](https://dashboard.web3auth.io)
-2. Go to **Project Settings** > **Advanced**
-3. Locate the **Test Accounts** section
-4. Toggle the **Enable Test Accounts** option
+1. Navigate to your project in the [Web3Auth dashboard](https://dashboard.web3auth.io).
+2. Click **Project Settings** then **Advanced**.
+3. Locate the **Test Accounts** section.
+4. Toggle the **Enable Test Accounts** option.
 
-## Test Account Types
+## Test account types
 
-### Email Authentication
+### Email authentication
 
 When Test Accounts are enabled, each test account is assigned a unique email address in the format `test_account_XXXX@example.com`, where `XXXX` represents a randomly generated number. You can use these test email addresses to authenticate using email passwordless OTP login.
 
-### Phone Number Authentication
+### Phone number authentication
 
 When Test Accounts are enabled, each test account is assigned a unique phone number in the format `+1 (555) XXX-XXXX`, where `XXX-XXXX` represents a randomly generated number. You can use these test phone numbers to authenticate using SMS OTP login.
 
-### Static OTP Code
+### Static OTP code
 
 When using Test Accounts, a static OTP verification code is generated and displayed in your project dashboard. This code remains constant for both email and phone number test accounts.
 
-## Usage in Development
+## Usage in development
 
-### Email + OTP Flow
+### Email and OTP flow
 
-1. Enter a test email (e.g., `test_account_XXXX@example.com`)
-2. Click "Send Code" or equivalent button
-3. Enter the static OTP: `XXXXXX`
-4. Complete the authentication flow
+1. Enter a test email (such as `test_account_XXXX@example.com`).
+2. Click "Send Code" or equivalent button.
+3. Enter the static OTP: `XXXXXX`.
+4. Complete the authentication flow.
 
-### SMS + OTP Flow
+### SMS and OTP flow
 
-1. Enter a test phone number (e.g., `+1 (555) XXX-XXXX`)
-2. Click "Send Code" or equivalent button
-3. Enter the static OTP: `XXXXXX`
-4. Complete the authentication flow
+1. Enter a test phone number (such as `+1 (555) XXX-XXXX`).
+2. Click "Send Code" or equivalent button.
+3. Enter the static OTP: `XXXXXX`.
+4. Complete the authentication flow.
 
-## Benefits for Development
+## Benefits for development
 
-### Consistent Testing Experience
+### Consistent testing experience
 
-- **Predictable Credentials**: Same OTP code (`XXXXXX`) works every time
-- **No External Dependencies**: No need to access email or SMS during testing
-- **Faster Iteration**: Streamlined testing without waiting for delivery of verification codes
+- Predictable Credentials: Same OTP code (`XXXXXX`) works every time
+- No External Dependencies: No need to access email or SMS during testing
+- Faster Iteration: Streamlined testing without waiting for delivery of verification codes
 
-### Team Collaboration
+### Team collaboration
 
-- **Shared Test Accounts**: Team members can use the same test credentials
-- **Standardized Testing**: Consistent testing experience across the development team
-- **Demo-Friendly**: Reliable for demonstrations and presentations
+- Shared Test Accounts: Team members can use the same test credentials
+- Standardized Testing: Consistent testing experience across the development team
+- Demo-Friendly: Reliable for demonstrations and presentations
 
-### CI/CD Integration
+### CICD integration
 
-- **Automated Testing**: Enables automated tests that require authentication flows
-- **E2E Testing**: Facilitates end-to-end testing scenarios
-- **Staging Validation**: Supports testing in staging environments
+- Automated Testing: Enables automated tests that require authentication flows
+- E2E Testing: Facilitates end-to-end testing scenarios
+- Staging Validation: Supports testing in staging environments
 
-## Security Considerations
+## Security considerations
 
-### Best Practices
+### Best practices
 
-- **Never use Test Accounts in production** - they are designed for testing only and could expose your application to security vulnerabilities if used in production
-- **Disable before going live** - ensure Test Accounts are turned off before production deployment
-- **Use separate projects** - maintain separate projects for development and production environments
-- **Document test credentials** - clearly document which credentials are for testing only
+- Never use Test Accounts in production: they are designed for testing only and could expose your application to security vulnerabilities if used in production
+- Disable before going live: ensure Test Accounts are turned off before production deployment
+- Use separate projects: maintain separate projects for development and production environments
+- Document test credentials: clearly document which credentials are for testing only
 
 ### Troubleshooting
 
 If Test Accounts are not functioning as expected:
 
-1. **Verify Environment**: Ensure you're using your particular Sapphire Devnet or Sapphire Mainnet environment where test accounts are enabled.
-2. **Check Project Settings**: Confirm Test Accounts are enabled in Project Settings > Advanced
-3. **Email or Phone**: Ensure test email or phone number is correct as mentioned in the dashboard, you can refresh the credentials by clicking on the refresh button.
-4. **OTP Code**: Always use `XXXXXX` as the verification code as mentioned in the dashboard
+1. Verify Environment: Ensure you're using your particular Sapphire Devnet or Sapphire Mainnet environment where test accounts are enabled.
+2. Check Project Settings: Confirm Test Accounts are enabled in Project Settings > Advanced
+3. Email or Phone: Ensure test email or phone number is correct as mentioned in the dashboard, you can refresh the credentials by clicking on the refresh button.
+4. OTP Code: Always use `XXXXXX` as the verification code as mentioned in the dashboard.
diff --git a/embedded-wallets/dashboard/advanced/user-details.mdx b/embedded-wallets/dashboard/advanced/user-details.mdx
index d5692628dca..bfb3ca5ad0d 100644
--- a/embedded-wallets/dashboard/advanced/user-details.mdx
+++ b/embedded-wallets/dashboard/advanced/user-details.mdx
@@ -17,11 +17,11 @@ The **User Details in ID Token** setting determines whether Personally Identifia
   />
 </div>
 
-## User Data Overview
+## User data overview
 
 JWT identity tokens can include various types of user information, ranging from minimal identifiers to comprehensive profile data. The configuration of this setting impacts both functionality and privacy considerations for your application.
 
-### Available User Data Types
+### Available user data types
 
 **Basic Identifier Information:**
 
@@ -37,9 +37,9 @@ JWT identity tokens can include various types of user information, ranging from
 - Social login provider data
 - Custom user metadata
 
-## Configuration Options
+## Configuration options
 
-### Enable User Data in Tokens
+### Enable user data in tokens
 
 When **enabled**, the identity token includes comprehensive user profile information:
 
@@ -62,7 +62,7 @@ When **enabled**, the identity token includes comprehensive user profile informa
 }
 ```
 
-### Disable User Data in Tokens
+### Disable user data in tokens
 
 When **disabled**, the identity token contains only essential identification information:
 
@@ -77,7 +77,7 @@ When **disabled**, the identity token contains only essential identification inf
 }
 ```
 
-### Email-Only Mode
+### Email-only mode
 
 When **userIdentifier is set to email**, only the user's email is included in the token:
 
@@ -93,9 +93,9 @@ When **userIdentifier is set to email**, only the user's email is included in th
 }
 ```
 
-## Implementation Patterns
+## Implementation patterns
 
-### Token Parsing and Validation
+### Token parsing and validation
 
 **Complete Token Processing:**
 
@@ -161,7 +161,7 @@ function extractUserData(decodedToken) {
 }
 ```
 
-### Frontend Integration
+### Frontend integration
 
 **React Implementation:**
 
@@ -239,9 +239,9 @@ function UserProfile() {
 </script>
 ```
 
-## Use Cases and Benefits
+## Use cases and benefits
 
-### Streamlined User Onboarding
+### Streamlined user onboarding
 
 **Profile Pre-population:**
 
@@ -266,7 +266,7 @@ async function setupUserAccount(idToken) {
 }
 ```
 
-### Personalized User Experience
+### Personalized user experience
 
 **Dynamic UI Customization:**
 
@@ -290,7 +290,7 @@ function personalizeInterface(userProfile) {
 }
 ```
 
-### Session Management
+### Session management
 
 **Enhanced Session Context:**
 
@@ -327,9 +327,9 @@ class SessionManager {
 }
 ```
 
-## Privacy and Compliance Considerations
+## Privacy and compliance considerations
 
-### Data Minimization Principles
+### Data minimization principles
 
 **GDPR Compliance:**
 
@@ -363,7 +363,7 @@ class PrivacyCompliantTokenHandler {
 }
 ```
 
-### Regional Compliance
+### Regional compliance
 
 **Multi-Jurisdictional Considerations:**
 
@@ -394,9 +394,9 @@ function getRegionSpecificTokenHandling(userRegion) {
 }
 ```
 
-## Security Considerations
+## Security considerations
 
-### Token Security Best Practices
+### Token security best practices
 
 **Secure Token Handling:**
 
@@ -445,7 +445,7 @@ class SecureTokenProcessor {
 }
 ```
 
-### Data Validation
+### Data validation
 
 **Input Validation and Sanitization:**
 
@@ -482,9 +482,9 @@ function validateUserData(userData) {
 }
 ```
 
-## Performance Considerations
+## Performance considerations
 
-### Token Size Management
+### Token size management
 
 **Optimizing Token Size:**
 
@@ -523,7 +523,7 @@ function analyzeTokenSize(idToken) {
 }
 ```
 
-### Caching Strategies
+### Caching strategies
 
 **Efficient User Data Caching:**
 
@@ -568,9 +568,9 @@ class UserDataCache {
 }
 ```
 
-## Decision Framework
+## Decision framework
 
-### When to Enable User Data in Tokens
+### When to enable user data in tokens
 
 **Recommended for:**
 
@@ -586,7 +586,7 @@ class UserDataCache {
 - Session management benefits from user context
 - Reduced API calls for user data improve performance
 
-### When to Disable User Data in Tokens
+### When to disable user data in tokens
 
 **Recommended for:**
 
@@ -602,7 +602,7 @@ class UserDataCache {
 - User data is managed separately
 - Security requirements prefer minimal token content
 
-### Email-Only Configuration
+### Email-only configuration
 
 **Optimal for:**
 
@@ -611,7 +611,7 @@ class UserDataCache {
 - Privacy-focused applications
 - Minimal PII exposure scenarios
 
-## Next Steps
+## Next steps
 
 - **[Session Management](../session-management)** - Configure session duration and behavior
 - **[Key Export Settings](../key-export)** - Control private key export permissions
diff --git a/embedded-wallets/dashboard/analytics.mdx b/embedded-wallets/dashboard/analytics.mdx
index 24cf07ce266..4193974c432 100644
--- a/embedded-wallets/dashboard/analytics.mdx
+++ b/embedded-wallets/dashboard/analytics.mdx
@@ -7,7 +7,7 @@ description: 'Monitor project analytics in Web3Auth Dashboard | Embedded Wallets
 
 import DashboardAnalytics from '@site/static/img/embedded-wallets/w3a-dashboard/dashboard-analytics.png'
 
-The project analytics section in the Web3Auth Dashboard provides developers with a comprehensive overview of user activity and project engagement. This analytics system gathers and visualizes key data points to help developers monitor authentication trends, evaluate project performance, and make informed decisions to enhance user experience.
+The project analytics section in the Web3Auth dashboard provides developers with a comprehensive overview of user activity and project engagement. This analytics system gathers and visualizes key data points to help developers monitor authentication trends, evaluate project performance, and make informed decisions to enhance user experience.
 
 By offering visibility into user behavior and system usage, analytics empowers teams to optimize authentication flows, track growth, and ensure the platform's reliability at scale.
 
@@ -71,4 +71,4 @@ Lists the types of authentication connections utilized across the project—such
 :::note
 
 Project analytics offers high-level visibility as well as drill-down insights, making it a powerful tool for both technical teams and product managers looking to refine onboarding and user authentication strategies.
-:::
\ No newline at end of file
+:::
diff --git a/embedded-wallets/dashboard/authentication.mdx b/embedded-wallets/dashboard/authentication.mdx
index 854748bd054..4aea24a9316 100644
--- a/embedded-wallets/dashboard/authentication.mdx
+++ b/embedded-wallets/dashboard/authentication.mdx
@@ -188,7 +188,7 @@ A thoughtfully configured set of login options improves accessibility, enhances
 
 :::
 
-## Social Connections
+## Social connections
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -198,7 +198,7 @@ A thoughtfully configured set of login options improves accessibility, enhances
   />
 </div>
 
-### Basic Logins
+### Basic logins
 
 Basic Logins refer to standard authentication methods such as passwordless email or phone number login. These options are particularly useful for users who may not wish to use social accounts or external wallets.
 
@@ -206,15 +206,15 @@ For most applications, it is recommended to either pair Basic Logins with altern
 
 <Tiles tileGroups={tileGroupsDataBasic} />
 
-### Social Logins
+### Social logins
 
-Social Logins allow users to authenticate using their existing accounts from widely adopted platforms, offering a seamless and familiar experience. Web3Auth supports a wide range of social identity providers, including:
+Social logins allow users to authenticate using their existing accounts from widely adopted platforms, offering a seamless and familiar experience. Web3Auth supports a wide range of social identity providers, including:
 
-Each social login method can be configured individually through the Web3Auth Dashboard. Developers can follow platform-specific guides to obtain necessary credentials (e.g., client IDs, secrets) and enable the desired providers.
+Each social login method can be configured individually through the Web3Auth Dashboard. Developers can follow platform-specific guides to obtain necessary credentials (such as client IDs, secrets), and enable the desired providers.
 
 <Tiles tileGroups={tileGroupsDataSocial} />
 
-## Custom Connections
+## Custom connections
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -224,23 +224,23 @@ Each social login method can be configured individually through the Web3Auth Das
   />
 </div>
 
-Custom Connections allow developers to integrate Web3Auth with third-party or self-hosted identity providers. Supported platforms include:
+Custom connections allow developers to integrate Web3Auth with third-party or self-hosted identity providers. Supported platforms include:
 
 <Tiles tileGroups={tileGroupsDataCustom} />
 
 These integrations offer advanced flexibility, enabling projects to maintain existing identity infrastructure while benefiting from Web3Auth's non-custodial key management. Developers can authenticate users using their preferred systems while still supporting seamless blockchain wallet access.
 
-:::note TIP
+:::tip
 
 Custom connections are ideal for enterprises or apps with an existing authentication backend who want to integrate Web3 capabilities without compromising on their current identity solutions.
 
 :::
 
-## Group Connections
+## Group connections
 
-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 (e.g., **_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 on-chain user identity. They are especially useful in scenarios where users may switch or alternate between login methods, allowing for continuous access to the same digital identity without fragmentation. This means that users logging in with different authentication providers (such as **_Google and Email Passwordless_**) can still access the same wallet address—ensuring a unified user experience.
 
-Before setting up a group connection, developers must first configure individual login connections that are eligible to be grouped. Once eligible connections are established, they can be grouped together under a single Group Connection.
+Before setting up a group connection, developers must first configure individual login connections that are eligible to be grouped. Once eligible connections are established, they can be grouped together under a single group connection.
 
 <Tiles tileGroups={tileGroupsDataGroup} />
 
@@ -254,26 +254,24 @@ Before setting up a group connection, developers must first configure individual
 
 :::note
 
-Group Keys differ from standard individual connection keys. Ensure that each login method intended for grouping is properly configured beforehand.
+Group keys differ from standard individual connection keys. Ensure that each login method intended for grouping is properly configured beforehand.
 
 :::
 
-> Group Connections are especially useful in scenarios where users may switch or alternate between login methods, allowing for continuous access to the same digital identity without fragmentation.
+## Security considerations
 
-## Security Considerations
-
-### Domain Whitelisting
+### Domain allowlisting
 
 Ensure authentication is restricted to authorized domains for enhanced security.
 
-### Connection Verification
+### Connection verification
 
 Verify OAuth credentials and callback URLs for all social login providers.
 
-### Rate Limiting
+### Rate limiting
 
 Configure appropriate rate limits for authentication attempts to prevent abuse.
 
-### Multi-Factor Authentication
+### Multi-factor authentication
 
 Enable additional security layers where supported by the authentication provider.
diff --git a/embedded-wallets/dashboard/chains-and-networks.mdx b/embedded-wallets/dashboard/chains-and-networks.mdx
index dc5527b0238..939e66f5b28 100644
--- a/embedded-wallets/dashboard/chains-and-networks.mdx
+++ b/embedded-wallets/dashboard/chains-and-networks.mdx
@@ -21,7 +21,7 @@ This intuitive setup ensures seamless integration and flexibility, allowing deve
   />
 </div>
 
-## Supported Networks
+## Supported networks
 
 The dashboard provides pre-configured support for major blockchain networks including:
 
@@ -39,15 +39,15 @@ And many more...
 
 For networks not included in the pre-configured list, developers can add custom blockchain networks by providing:
 
-- **Chain ID**: The unique identifier for the blockchain network
-- **Currency symbol**: The native token symbol (e.g., ETH, MATIC, AVAX)
-- **Block explorer URL**: The base URL for the network's block explorer
-- **Namespace**: The blockchain namespace (typically "eip155" for EVM-compatible chains)
-- **RPC URL**: The endpoint for interacting with the blockchain network
+- Chain ID: The unique identifier for the blockchain network
+- Currency Symbol: The native token symbol (such as ETH, MATIC, AVAX)
+- Block Explorer URL: The base URL for the network's block explorer
+- Namespace: The blockchain namespace (typically "eip155" for EVM-compatible chains)
+- RPC URL: The endpoint for interacting with the blockchain network
 
 ## Network configuration benefits
 
-- **No SDK changes required**: Network configurations are handled entirely through the dashboard
-- **Instant updates**: Changes take effect immediately without requiring code deployments
-- **Environment-specific settings**: Different network configurations for development and production
-- **Testnet support**: Easy switching between mainnet and testnet environments for development
+- No SDK changes required: Network configurations are handled entirely through the dashboard
+- Instant updates: Changes take effect immediately without requiring code deployments
+- Environment-specific settings: Different network configurations for development and production
+- Testnet support: Easy switching between mainnet and testnet environments for development
diff --git a/embedded-wallets/dashboard/customization.mdx b/embedded-wallets/dashboard/customization.mdx
index 8ce92024fc6..b46819b3cee 100644
--- a/embedded-wallets/dashboard/customization.mdx
+++ b/embedded-wallets/dashboard/customization.mdx
@@ -10,13 +10,14 @@ import CustomizationLoginModal from '@site/static/img/embedded-wallets/w3a-dashb
 
 ## Branding
 
-The branding tab under the customization section of the Web3Auth Dashboard allows developers to personalize the visual identity of their application across multiple user interfaces. This includes the login screens, Multi-Factor Authentication (MFA) screens, wallet UI, and login modals.
+The branding page under the customization section of the Web3Auth dashboard allows developers to personalize the visual identity of their application across multiple user interfaces. This includes the login screens, Multi-Factor Authentication (MFA) screens, wallet UI, and login modals.
 
 Effective branding ensures a seamless and recognizable user experience, helping users feel confident that they are interacting with your application—even when interacting with Web3Auth-hosted interfaces.
 
-:::note 
+:::note
+
+All changes made within the branding page can be previewed in real-time. However, to reflect updates in production, developers must click the **Save & Publish** button after making changes.
 
-All changes made within the Branding tab can be previewed in real-time. However, to reflect updates in production, developers must click the Save & Publish button after making changes.
 :::
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
@@ -37,9 +38,9 @@ Upload a logo to personalize the user interface and email templates. For optimal
 
 Developers have the option to display the uploaded logo as the loading spinner across the Web3Auth login flow. This small detail enhances brand consistency and gives users a familiar visual cue during authentication.
 
-#### Custom terms & conditions and privacy policy
+#### Custom terms and conditions/privacy policy
 
-Link to your application's Terms of Service and Privacy Policy. These links will be displayed during user onboarding and consent flows, ensuring legal compliance and improving transparency.
+Link to your application's terms of service and/or privacy policy. These links will be displayed during user onboarding and consent flows, ensuring legal compliance and improving transparency.
 
 #### Application name
 
@@ -83,13 +84,16 @@ Defines the primary brand color used across interactive elements such as:
 
 #### On primary color
 
-Specifies the color applied to text and icons that appear on top of primary color backgrounds (e.g., button labels or iconography). This ensures sufficient contrast for readability and accessibility.
+Specifies the color applied to text and icons that appear on top of primary color backgrounds (such as button labels or iconography). This ensures sufficient contrast for readability and accessibility.
 
-> Tip: Choose color combinations that meet accessibility guidelines (e.g., [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/)) to provide an inclusive experience for all users.
+:::tip
+
+Choose color combinations that meet accessibility guidelines (such as [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/)) to provide an inclusive experience for all users.
+:::
 
 ## Login modal
 
-The Login modal tab within the Customization section of the Web3Auth Dashboard provides developers with granular control over the appearance and behavior of the Web3Auth login flow.
+The login modal page within the customization section of the Web3Auth dashboard provides developers with granular control over the appearance and behavior of the Web3Auth login flow.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -101,35 +105,35 @@ The Login modal tab within the Customization section of the Web3Auth Dashboard p
 
 ### Design
 
-The Design section offers layout and styling options to customize how the login modal is presented to users.
+The design section offers layout and styling options to customize how the login modal is presented to users.
 
 #### Login modal appearance
 
 Developers can choose between two display modes for the login interface:
 
-- **Embedded widget**: The login UI is embedded directly within the application's layout. This option is ideal for single-page applications or flows that require a fully integrated experience.
-- **Modal widget**: The login interface opens as a pop-up modal overlay. This provides a more traditional Web3 wallet experience, where authentication occurs in a floating layer over the existing content.
+- Embedded widget: The login UI is embedded directly within the application's layout. This option is ideal for single-page applications or flows that require a fully integrated experience.
+- Modal widget: The login interface opens as a pop-up modal overlay. This provides a more traditional Web3 wallet experience, where authentication occurs in a floating layer over the existing content.
 
 #### Logo alignment
 
 Configure how the application logo is aligned within the login modal:
 
-- **Center-Aligned**: Displays the logo at the top center, suitable for balanced layouts.
-- **Left-Aligned**: Positions the logo to the top-left, often preferred for enterprise or dashboard-style applications.
+- Center-aligned: Displays the logo at the top center, suitable for balanced layouts.
+- Left-Aligned: Positions the logo to the top-left, often preferred for enterprise or dashboard-style applications.
 
 #### Border radius
 
 Adjust the corner curvature of the modal interface:
 
-- **Small**, **Medium**, or **Large** radius options allow for stylistic variations that better match your app's design system.
+- Small, medium, or large radius options allow for stylistic variations that better match your app's design system.
 
 #### Border radius type
 
 Refine the shape of buttons and input fields within the modal by selecting:
 
-- **Pill**: Fully rounded ends for a modern, soft appearance.
-- **Rounded**: Gently curved corners for a subtle aesthetic.
-- **Square**: Sharp 90° corners for a more technical or minimalist look.
+- Pill: Fully rounded ends for a modern, soft appearance.
+- Rounded: Gently curved corners for a subtle aesthetic.
+- Square: Sharp 90° corners for a more technical or minimalist look.
 
 These design customizations allow developers to ensure the login experience feels native to the application, enhancing user trust and engagement.
 
@@ -137,12 +141,12 @@ These design customizations allow developers to ensure the login experience feel
 
 The Authentication section provides flexibility in how login options are presented within the modal.
 
-#### Arrange Login Order
+#### Arrange login order
 
 When multiple login methods (such as, social, email/phone, external wallets) are available, developers can define the order in which these options appear.
 
-- Simply drag and drop the login methods to rearrange their position.
-- This order determines the priority and placement of login options shown to users during authentication.
+- Drag and drop the logi n methods to rearrange their position.
+- Order determines the priority and placement of login options shown to users during authentication.
 
 :::note
 
@@ -152,14 +156,14 @@ This customization improves user experience by surfacing the most relevant login
 
 ### External wallets
 
-The **External Wallets** settings provide additional configuration for displaying third-party wallet options such as MetaMask, WalletConnect, and others.
+The external wallet settings let you configure how third-party wallets—such as MetaMask or any wallet connected through WalletConnect—are displayed in your application.
 
 #### Show installed external wallets
 
-Enable this option to automatically detect and display any compatible wallets already installed in the user's browser or device (such as, MetaMask or Phantom). This improves onboarding by surfacing options users are already familiar with.
+Enable this to automatically detect and display any compatible wallets already installed in the user's browser or device (such as MetaMask). This improves onboarding by surfacing options users are already familiar with.
 
-#### Show number of external wallets
+#### Select number of external wallets
 
-Choose how many external wallet options are displayed at once. Developers can limit or expand this list based on the target user base and the types of wallets they are likely to use.
+Choose how many external wallet options are displayed at once. Developers can limit or expand this list based on the target user base and the types of wallets they're likely to use.
 
 These settings ensure wallet integrations are both comprehensive and context-aware, adapting to the environment and user preferences for seamless onboarding.
diff --git a/embedded-wallets/dashboard/project-settings.mdx b/embedded-wallets/dashboard/project-settings.mdx
index 5a0f8b97a6d..2ad5eb1c011 100644
--- a/embedded-wallets/dashboard/project-settings.mdx
+++ b/embedded-wallets/dashboard/project-settings.mdx
@@ -7,7 +7,7 @@ description: 'Configure project settings in Web3Auth Dashboard | Embedded Wallet
 
 import ProjectSettingsGeneral from '@site/static/img/embedded-wallets/w3a-dashboard/project-settings-general.png'
 
-The project settings section of the Web3Auth Dashboard allows developers to manage core configuration options for each project. These settings determine how the project integrates with the Web3Auth SDK and how it behaves across different environments.
+The project settings section of the Web3Auth dashboard allows developers to manage core configuration options for each project. These settings determine how the project integrates with the Web3Auth SDK and how it behaves across different environments.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -21,69 +21,66 @@ The project settings section of the Web3Auth Dashboard allows developers to mana
 
 ### Project name
 
-This is the name of the project that will be displayed to users during the Web3Auth login flow and in any related email communication. The project name serves as your application's identity in the Web3Auth ecosystem.
+This is the name of the project that will be displayed to users during the Web3Auth login flow and in any related email communication. The project name serves as your application's identity in the Web3Auth ecosystem. It can be modified at any time after project creation.
 
-**Key Features:**
+The name appears in:
 
-- **User-Facing Display**: Appears in login modals and authentication flows
-- **Email Communications**: Used in Web3Auth-generated emails to users
-- **Dashboard Identification**: Helps you identify projects in your dashboard
-- **Updateable**: Can be modified at any time after project creation
+- User-facing displays: Appears in login modals and authentication flows
+- Email communications: Used in Web3Auth-generated emails to users
+- Dashboard identification: Helps you identify projects in your dashboard 
 
-**Best Practices:**
+:::tip Naming Best Practices
 
 - Use a clear, recognizable name that matches your application
 - Keep it concise but descriptive
 - Avoid special characters that might cause display issues
 - Consider how it will appear to end users
+:::
 
 ### Environment
 
-This indicates the Web3Auth environment selected during project creation. The environment determines the infrastructure tier and security level of your project.
-
-**Available Environments:**
+This indicates the Web3Auth environment selected during project creation. The environment determines the infrastructure tier and security level of your project. Two globally distributed and highly scalable environments are available:
 
-- **Sapphire Devnet**: Development environment for testing and integration
-- **Sapphire Mainnet**: Production environment for live applications
+- Sapphire Devnet: Development environment for testing and integration
+- Sapphire Mainnet: Production environment for live applications
 
-**Important Notes:**
+:::important
 
-- Environments are globally distributed and highly scalable
 - **Cannot be modified** after project creation
 - Each environment has separate user bases and data isolation
 - Production applications should use Sapphire Mainnet
+:::
 
 ### Project platform
 
-Developers can select from a wide range of platform options depending on the nature of their application. This setting helps optimize the SDK behavior and available features for your specific platform.
+Developers can select from a wide range of platform options depending on the nature of their application. This setting helps optimize the SDK behavior and available features for the specific platform: 
 
-**Platform Options:**
+- Web: Browser-based applications (React, Vue, JavaScript)
+- Mobile: Native mobile applications (Android, iOS, React Native, Flutter)
+- Gaming: Game development platforms (Unity, Unreal Engine)
 
-- **Web**: Browser-based applications (React, Vue, JavaScript)
-- **Mobile**: Native mobile applications (Android, iOS, React Native, Flutter)
-- **Gaming**: Game development platforms (Unity, Unreal Engine)
+:::note 
 
-**Platform-Specific Features:**
+Each platform offers specific features:
 
 - Different SDK packages and integration methods
 - Platform-optimized authentication flows
 - Tailored documentation and examples
 - Specific security considerations
+:::
 
 ## Authentication credentials
 
 ### Client ID
 
-A unique identifier automatically generated for each project. This is the primary credential used to authenticate your application with Web3Auth services.
-
-**Characteristics:**
+A unique identifier automatically generated for each project. This is the primary credential used to authenticate your application with Web3Auth services. This ID is: 
 
-- **Publicly Safe**: Can be exposed in client-side code
-- **Required for Integration**: Essential for all SDK implementations
-- **Unique per Project**: Each project receives a distinct Client ID
-- **Immutable**: Cannot be changed after generation
+- Publicly safe: Can be exposed in client-side code
+- Required for integration: Essential for all SDK implementations
+- Unique per project: Each project receives a distinct Client ID
+- Immutable: Cannot be changed after generation
 
-**Usage Example:**
+**Implementation Example:**
 
 ```javascript
 import { Web3Auth } from '@web3auth/modal'
@@ -96,47 +93,45 @@ const web3auth = new Web3Auth({
 
 ### Client secret
 
-A confidential key used for authenticating server-side API requests and advanced integrations. This credential provides elevated access to Web3Auth services.
+A **confidential** key used for authenticating server-side API requests and advanced integrations. This credential provides elevated access to Web3Auth services.
+
+:::danger Security Warning
+
+The client secret must never be exposed in client-side code, mobile applications, or any publicly accessible environment. Exposure could compromise your project's security.
 
-**Security Requirements:**
+:::
 
-- **Never expose** in frontend code or client-side environments
-- **Server-side only**: Use exclusively in backend services
-- **Secure storage**: Store in environment variables or secure vaults
-- **Rotation capability**: Can be regenerated if compromised
+- Never expose in frontend code or client-side environments
+- Server-side only: Use exclusively in backend services
+- Secure storage: Store in environment variables or secure vaults
+- Rotation capability: Can be regenerated if compromised
 
-**Use Cases:**
+The client secret is used for:
 
 - Server-side user verification
 - Administrative operations
 - Webhook signature verification
 - Advanced API integrations
 
-:::danger Security Warning
+## Token verification
 
-The Client Secret must never be exposed in client-side code, mobile applications, or any publicly accessible environment. Exposure could compromise your project's security.
+### JWKS endpoint
 
-:::
+A public endpoint that exposes the JSON Web Key Set (JWKS) used by Web3Auth to sign JWTs. This endpoint enables you to verify the authenticity of identity tokens issued by Web3Auth, providing the following benefits:
 
-## Token Verification
+- Dynamic key rotation: Automatically receives updated signing keys
+- Industry standard: JWKS is a widely adopted standard for JWT verification
+- High availability: Backed by Web3Auth's global infrastructure
+- Real-time updates: Always provides current verification keys
 
-### JWKS endpoint
+#### Using the JWKS endpoint
 
-A public endpoint that exposes the JSON Web Key Set (JWKS) used by Web3Auth to sign JWTs. This endpoint enables you to verify the authenticity of identity tokens issued by Web3Auth.
-
-**Endpoint Format:**
+Pass the request to the JWKS endpoint with your project ID as the identifier:
 
 ```
-https://api.web3auth.io/jwks?project_id=YOUR_PROJECT_ID
+https://api.web3auth.io/jwks?project_id=<YOUR_PROJECT_ID>
 ```
 
-**Benefits:**
-
-- **Dynamic Key Rotation**: Automatically receives updated signing keys
-- **Industry Standard**: JWKS is a widely adopted standard for JWT verification
-- **High Availability**: Backed by Web3Auth's global infrastructure
-- **Real-time Updates**: Always provides current verification keys
-
 **Implementation Example:**
 
 ```javascript
@@ -166,16 +161,14 @@ jwt.verify(token, getKey, options, (err, decoded) => {
 
 ### Project verification key
 
-An alternative to using the JWKS endpoint, this static key allows for token verification without depending on external JWKS URL calls.
-
-**Advantages:**
+An alternative to using the JWKS endpoint, this static key allows for token verification without depending on external JWKS URL calls. While providing less security, this offers the following advantages:
 
-- **Offline Verification**: No external API calls required
-- **Reduced Latency**: Faster token verification process
-- **Network Independence**: Works in environments with limited connectivity
-- **Simplified Implementation**: Single key verification logic
+- Offline Verification: No external API calls required
+- Reduced Latency: Faster token verification process
+- Network Independence: Works in environments with limited connectivity
+- Simplified Implementation: Single key verification logic
 
-**When to Use:**
+The project verification key is suitable for:
 
 - Applications with strict latency requirements
 - Environments with limited internet access
@@ -205,14 +198,14 @@ jwt.verify(token, PROJECT_VERIFICATION_KEY, { algorithms: ['RS256'] }, (err, dec
 
 ### Archive project
 
-The Archive Project feature allows you to deactivate a project while preserving its configuration and data. This is useful for temporarily disabling projects or maintaining historical records.
+The archive project feature allows you to deactivate a project while preserving its configuration and data. This is useful for temporarily disabling projects or maintaining historical records.
 
 **Archive Effects:**
 
-- **Read-Only Mode**: Project becomes non-functional but viewable
-- **Authentication Disabled**: Users cannot log in to archived projects
-- **Data Preservation**: All configuration and user data is retained
-- **Reversible**: Projects can be restored from archived state
+- Read-Only Mode: Project becomes non-functional but viewable
+- Authentication Disabled: Users cannot log in to archived projects
+- Data Preservation: All configuration and user data is retained
+- Reversible: Projects can be restored from archived state
 
 **When to Archive:**
 
@@ -228,7 +221,7 @@ The Archive Project feature allows you to deactivate a project while preserving
 - User data and authentication flows resume normally
 - No data loss occurs during archive/restore cycles
 
-:::info Archive vs Delete
+:::info Archive vs. Delete
 
 Archiving preserves all project data and allows for restoration. If you need to permanently remove a project, contact Web3Auth support for assistance with proper data deletion procedures.
 
@@ -238,10 +231,10 @@ Archiving preserves all project data and allows for restoration. If you need to
 
 For comprehensive project configuration, explore these related settings:
 
-- **[Whitelist Settings](../whitelist)** - Configure domain and URL authorization for enhanced security
-- **[Advanced Project Settings](../advanced/session-management)** - Access session management, key export, user data, and testing configurations
+- [Whitelist settings](../whitelist) - Configure domain and URL authorization for enhanced security
+- [Advanced project settings](../advanced/session-management) - Access session management, key export, user data, and testing configurations
 
-### Quick start guide
+### Quickstart guide
 
 **Essential Configuration Steps:**
 
diff --git a/embedded-wallets/dashboard/wallet-services.mdx b/embedded-wallets/dashboard/wallet-services.mdx
index 6b05e3b8f27..b756bc8a3b0 100644
--- a/embedded-wallets/dashboard/wallet-services.mdx
+++ b/embedded-wallets/dashboard/wallet-services.mdx
@@ -7,7 +7,7 @@ description: 'Configure wallet services and UI in Web3Auth Dashboard | Embedded
 
 import WalletConfiguration from '@site/static/img/embedded-wallets/w3a-dashboard/wallet-configuration.png'
 
-The Wallet Configuration tab within the Web3Auth Dashboard enables developers to customize the wallet experience provided to users within their decentralized applications (dApps). These settings define the appearance, capabilities, and interactivity of the Web3Auth wallet interface.
+The wallet configuration tab within the Web3Auth dashboard enables developers to customize the wallet experience provided to users within their decentralized applications (dApps). These settings define the appearance, capabilities, and interactivity of the Web3Auth wallet interface.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -17,61 +17,64 @@ The Wallet Configuration tab within the Web3Auth Dashboard enables developers to
   />
 </div>
 
-## Customize Wallet UI
+## Customize wallet UI
 
 The Wallet UI can be tailored to align with the application's user experience and branding preferences. The following customization options are available:
 
-### Portfolio Widget
+### Portfolio widget
 
 Enable or disable the portfolio widget that displays token balances, transaction history, and wallet analytics. This provides users with a clear overview of their holdings directly within the dApp.
 
-### Widget Placement
+### Widget placement
 
 Choose the position of the wallet widget on the application interface. Available positions include:
 
-- **Bottom Right**
-- **Bottom Left**
-- **Top Left**
-- **Top Right**
+- Bottom Right
+- Bottom Left
+- Top Left
+- Top Right
 
 This flexibility ensures seamless integration with your existing UI/UX design.
 
-### Token and NFT Display
+### Token and NFT display
 
 Configure whether users can view their token balances and NFTs within the wallet interface. Enabling these options enhances the wallet's functionality, offering users visibility into their digital assets without leaving the dApp.
 
-### Wallet Features
+### Wallet features
 
 Toggle individual wallet actions such as:
 
-- **Buy**: Allow users to purchase crypto assets via integrated on-ramps.
-- **Swap**: Enable in-wallet token swaps through supported liquidity protocols.
-- **Send / Receive**: Facilitate peer-to-peer asset transfers.
-- **WalletConnect**: Add interoperability by allowing users to connect with external dApps that support WalletConnect protocol.
+- Buy: Allow users to purchase crypto assets via integrated on-ramps.
+- Swap: Enable in-wallet token swaps through supported liquidity protocols.
+- Send/Receive: Facilitate peer-to-peer asset transfers.
+- WalletConnect: Add interoperability by allowing users to connect with external dApps that support the WalletConnect protocol.
 
-### Transaction Confirmation Modal
+### Transaction confirmation modal
 
-When enabled, users will be prompted to approve each transaction via a confirmation modal. This mirrors the behavior of traditional external wallets (e.g., MetaMask), offering an additional layer of transparency and user control over on-chain interactions.
+When enabled, users will be prompted to approve each transaction via a confirmation modal. This mirrors the behavior of traditional external wallets (such as MetaMask), offering an additional layer of transparency and user control over onchain interactions.
 
-> Note: These wallet services are fully integrated and require no additional SDK logic—configuration through the dashboard is sufficient to apply changes across your application.
+:::note
 
-## Benefits of Wallet Customization
+These wallet services are fully integrated and require no additional SDK. Logic—configuration through the dashboard is sufficient to apply changes across your application.
+:::
+
+## Benefits of wallet customization
 
 These customization options ensure that developers can build a wallet experience that meets both usability and security expectations while maintaining consistency with their application's design.
 
-### Enhanced User Experience
+### Enhanced user experience
 
 - Seamless integration with your application's design language
 - Familiar wallet functionality without leaving your dApp
 - Customizable feature set based on your use case
 
-### Security & Control
+### Security and control
 
 - Transaction confirmation modals for user awareness
 - Granular control over available wallet features
 - Built-in security measures and best practices
 
-### Developer Efficiency
+### Developer efficiency
 
 - No additional SDK implementation required
 - Dashboard-based configuration with instant updates
diff --git a/embedded-wallets/dashboard/whitelist.mdx b/embedded-wallets/dashboard/whitelist.mdx
index 3896bd3290f..994725e401d 100644
--- a/embedded-wallets/dashboard/whitelist.mdx
+++ b/embedded-wallets/dashboard/whitelist.mdx
@@ -6,6 +6,8 @@ description: 'Configure domain whitelisting in Web3Auth Dashboard | Embedded Wal
 ---
 
 import ProjectSettingsDomain from '@site/static/img/embedded-wallets/w3a-dashboard/project-settings-domain.png'
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
 
 The **Whitelist Settings** section allows you to configure domain and URL authorization for enhanced security. Web3Auth requires explicit whitelisting of domains and URLs that are authorized to use your project's Web3Auth SDK, providing protection against unauthorized usage and potential security threats.
 
@@ -17,24 +19,25 @@ The **Whitelist Settings** section allows you to configure domain and URL author
   />
 </div>
 
-## Domain Authorization Overview
+## Domain authorization overview
 
 Domain whitelisting is a critical security feature that prevents unauthorized applications from using your Web3Auth project credentials. Only domains and URLs explicitly added to your whitelist can successfully authenticate users through your Web3Auth configuration.
 
-### Security Benefits
+### Security benefits
 
-- **Prevents Credential Theft**: Unauthorized sites cannot use your Client ID
-- **Protects User Data**: Ensures authentication flows only occur on approved domains
-- **Compliance Ready**: Meets security standards for production applications
-- **Fraud Prevention**: Blocks malicious sites from impersonating your application
+- **Prevents credential theft**: Unauthorized sites cannot use your Client ID
+- **Protects user data**: Ensures authentication flows only occur on approved domains
+- **Compliance ready**: Meets security standards for production applications
+- **Fraud prevention**: Blocks malicious sites from impersonating your application
 
-## Web Application Whitelisting
+## Web application whitelisting
 
-### Supported URL Formats
+### Supported URL formats
 
 Web3Auth supports various URL formats for comprehensive domain coverage:
 
-**Standard Domains:**
+<Tabs>
+<TabItem value="standard" label="Standard domains">
 
 ```
 https://myapp.com
@@ -42,7 +45,8 @@ https://www.myapp.com
 https://app.mycompany.com
 ```
 
-**Development Environments:**
+</TabItem>
+<TabItem value="development" label="Development environments">
 
 ```
 http://localhost:3000
@@ -51,14 +55,16 @@ https://dev.myapp.com
 https://staging.myapp.com
 ```
 
-**Subdomain Patterns:**
+</TabItem>
+<TabItem value="subdomain" label="Subdomain patterns">
 
 ```
 https://*.myapp.com (covers all subdomains)
 https://feature-*.myapp.com (wildcard patterns)
 ```
 
-**Port-Specific URLs:**
+</TabItem>
+<TabItem value="port" label="Port-specific URLs">
 
 ```
 https://myapp.com:8443
@@ -66,67 +72,83 @@ http://localhost:3000
 http://127.0.0.1:8080
 ```
 
-### Adding Web Domains
+</TabItem>
+</Tabs>
 
-1. **Navigate to Project Settings** → **Whitelist**
-2. **Click "Add Domain"** or similar button
-3. **Enter the complete URL** including protocol (http:// or https://)
-4. **Verify the domain** if required
-5. **Save the configuration**
+### Adding web domains
 
-**Best Practices:**
+1. Navigate to **Project Settings** → **Whitelist**.
+2. Click **Add Domain** or similar button.
+3. Enter the complete URL including protocol (http:// or https://).
+4. Verify the domain (if required).
+5. Save the configuration.
+
+:::tip Best Practices
 
 - Always use HTTPS for production domains
 - Include all necessary subdomains
 - Add development and staging environments
 - Test authentication after adding domains
 
-## Mobile Application Whitelisting
+:::
+
+## Mobile application whitelisting
 
-### Bundle Identifiers
+### Bundle identifiers
 
 For mobile applications, whitelist the app's bundle identifier or package name:
 
-**iOS Bundle IDs:**
+<Tabs>
+<TabItem value="ios" label="iOS Bundle IDs">
 
 ```
 com.yourcompany.yourapp
 com.yourcompany.yourapp.staging
 ```
 
-**Android Package Names:**
+</TabItem>
+<TabItem value="android" label="Android Package Names">
 
 ```
 com.yourcompany.yourapp
 com.yourcompany.yourapp.debug
 ```
 
-### Deep Link Schemes
+</TabItem>
+</Tabs>
+
+### Deep link schemes
 
-Mobile applications using deep links should whitelist their custom URL schemes:
+Mobile applications using deep links should allowlist their custom URL schemes:
 
-**Custom Schemes:**
+<Tabs>
+<TabItem value="custom" label="Custom schemes">
 
 ```
 yourapp://auth
 com.yourcompany.yourapp://callback
 ```
 
-**Universal Links (iOS):**
+</TabItem>
+<TabItem value="ios-links" label="iOS: universal links">
 
 ```
 https://yourapp.com/auth/callback
 ```
 
-**App Links (Android):**
+</TabItem>
+<TabItem value="android-links" label="Android: app links">
 
 ```
 https://yourapp.com/auth/callback
 ```
 
-## Environment-Specific Configuration
+</TabItem>
+</Tabs>
 
-### Development Environment
+## Environment-specific configuration
+
+### Development environment
 
 For development and testing:
 
@@ -145,7 +167,7 @@ https://staging.yourapp.com
 - Add staging and testing environments
 - Use HTTP for local development (HTTPS for staging)
 
-### Production Environment
+### Production environment
 
 :::warning Production Requirements
 
@@ -162,13 +184,14 @@ For Sapphire Mainnet projects, **at least one domain must be whitelisted** befor
 - ✅ Deep link schemes configured
 - ✅ Remove development URLs
 
-## Wildcard Domains
+## Wildcard domains
 
-### Subdomain Wildcards
+### Subdomain wildcards
 
 Use wildcard patterns to cover multiple subdomains efficiently:
 
-**Single-level wildcard:**
+<Tabs>
+<TabItem value="single" label="Single-level wildcard">
 
 ```
 https://*.myapp.com
@@ -176,7 +199,8 @@ https://*.myapp.com
 
 Covers: `https://api.myapp.com`, `https://admin.myapp.com`, `https://user.myapp.com`
 
-**Multi-level wildcards:**
+</TabItem>
+<TabItem value="multi" label="Multi-level wildcards">
 
 ```
 https://*.*.myapp.com
@@ -184,7 +208,10 @@ https://*.*.myapp.com
 
 Covers: `https://api.v1.myapp.com`, `https://admin.staging.myapp.com`
 
-### Dynamic Subdomains
+</TabItem>
+</Tabs>
+
+### Dynamic subdomains
 
 For applications with dynamic subdomains (multi-tenant apps):
 
@@ -194,9 +221,9 @@ https://tenant-*.myapp.com
 https://*.saas.myapp.com
 ```
 
-## Verification Process
+## Verification process
 
-### Domain Verification
+### Domain verification
 
 Some domains may require verification to ensure ownership:
 
@@ -204,7 +231,7 @@ Some domains may require verification to ensure ownership:
 2. **File Upload**: Upload a verification file to your web server
 3. **HTML Meta Tag**: Add a meta tag to your website's homepage
 
-### Verification Status
+### Verification status
 
 Monitor the verification status in your dashboard:
 
@@ -212,9 +239,9 @@ Monitor the verification status in your dashboard:
 - ⏳ **Pending**: Verification in progress
 - ❌ **Failed**: Verification unsuccessful, requires attention
 
-## Common Issues and Solutions
+## Common issues and solutions
 
-### Authentication Failures
+### Authentication failures
 
 **Problem**: Users cannot authenticate on your domain
 **Solutions:**
@@ -224,7 +251,7 @@ Monitor the verification status in your dashboard:
 - Ensure protocol (http/https) matches exactly
 - Confirm subdomain patterns are correct
 
-### Development Environment Issues
+### Development environment issues
 
 **Problem**: Local development not working
 **Solutions:**
@@ -234,7 +261,7 @@ Monitor the verification status in your dashboard:
 - Check if your development server uses a different port
 - Verify protocol matches (http vs https)
 
-### Mobile App Issues
+### Mobile app issues
 
 **Problem**: Mobile authentication failing
 **Solutions:**
@@ -244,32 +271,33 @@ Monitor the verification status in your dashboard:
 - Ensure URL schemes are properly whitelisted
 - Test with both debug and release builds
 
-## Security Best Practices
+## Security best practices
 
-### Regular Audits
+### Regular audits
 
-- **Monthly Reviews**: Check whitelist for unused domains
-- **Remove Stale Entries**: Delete old development or staging URLs
-- **Monitor Access**: Review authentication patterns for anomalies
-- **Update Documentation**: Keep domain lists current for your team
+- **Monthly reviews**: Check whitelist for unused domains
+- **Remove stale entries**: Delete old development or staging URLs
+- **Monitor access**: Review authentication patterns for anomalies
+- **Update documentation**: Keep domain lists current for your team
 
-### Principle of Least Privilege
+### Principle of least privilege
 
-- **Minimal Domains**: Only whitelist necessary domains
-- **Specific Patterns**: Avoid overly broad wildcard patterns
-- **Environment Separation**: Use different projects for dev/staging/prod
-- **Regular Cleanup**: Remove domains when no longer needed
+- **Minimal domains**: Only whitelist necessary domains
+- **Specific patterns**: Avoid overly broad wildcard patterns
+- **Environment separation**: Use different projects for dev/staging/prod
+- **Regular cleanup**: Remove domains when no longer needed
 
-### Compliance Considerations
+### Compliance considerations
 
-- **Data Residency**: Consider where authentication occurs
-- **Privacy Regulations**: Ensure whitelisted domains comply with privacy laws
-- **Security Standards**: Meet industry requirements for domain authorization
-- **Audit Trails**: Maintain records of domain modifications
+- **Data residency**: Consider where authentication occurs
+- **Privacy regulations**: Ensure whitelisted domains comply with privacy laws
+- **Security standards**: Meet industry requirements for domain authorization
+- **Audit trails**: Maintain records of domain modifications
 
-## Advanced Configuration
+## Advanced configuration
 
-### CDN and Load Balancer Support
+<Tabs>
+<TabItem value="cdn" label="CDN and load balancer support">
 
 For applications using CDNs or load balancers:
 
@@ -279,7 +307,8 @@ https://lb.myapp.com
 https://edge-*.myapp.com
 ```
 
-### Multi-Region Deployments
+</TabItem>
+<TabItem value="multi-region" label="Multi-region deployments">
 
 For global applications with regional domains:
 
@@ -290,7 +319,8 @@ https://asia.myapp.com
 https://*.global.myapp.com
 ```
 
-### API Gateway Integration
+</TabItem>
+<TabItem value="api-gateway" label="API gateway integration">
 
 For applications behind API gateways:
 
@@ -300,7 +330,10 @@ https://gateway.myapp.com
 https://*.api.myapp.com
 ```
 
-## Next Steps
+</TabItem>
+</Tabs>
+
+## Next steps
 
 - **[Project Settings](../project-settings)** - Configure basic project information
 - **[Advanced Project Settings](../advanced/session-management)** - Access advanced configuration options

From 981c8a3cf0d2cfbc67a49062520fa21932f68191 Mon Sep 17 00:00:00 2001
From: m4sterbunny <harrie.bickle-ext@consensys.net>
Date: Wed, 3 Dec 2025 17:26:35 +0000
Subject: [PATCH 2/3] further style alignment

---
 embedded-wallets/authentication/README.mdx    |  2 +-
 .../basic-logins/email-passwordless.mdx       | 14 +++++------
 .../basic-logins/external-wallets.mdx         |  8 +++----
 .../authentication/basic-logins/sms-otp.mdx   | 12 +++++-----
 .../custom-connections/auth0.mdx              | 20 ++++++++--------
 .../custom-connections/aws-cognito.mdx        | 18 +++++++-------
 .../custom-connections/custom-jwt.mdx         | 24 +++++++++----------
 .../custom-connections/firebase.mdx           | 23 ++++++++++--------
 .../authentication/group-connections.mdx      | 22 ++++++++++-------
 embedded-wallets/authentication/id-token.mdx  |  6 ++---
 .../authentication/social-logins/discord.mdx  | 22 ++++++++---------
 .../authentication/social-logins/facebook.mdx | 14 +++++------
 .../authentication/social-logins/google.mdx   | 18 +++++++-------
 .../authentication/social-logins/oauth.mdx    |  4 ++--
 .../authentication/social-logins/twitch.mdx   | 20 ++++++++--------
 .../_evm-interaction.mdx                      |  8 +++----
 .../connect-blockchain/evm/rpc-headers.mdx    | 16 ++++++-------
 .../connect-blockchain/evm/tron/web.mdx       |  2 +-
 .../connect-blockchain/other/README.mdx       |  2 +-
 .../connect-blockchain/other/algorand.mdx     |  2 +-
 .../connect-blockchain/other/aptos.mdx        | 12 +++++-----
 .../connect-blockchain/other/cosmos.mdx       |  2 +-
 .../connect-blockchain/other/immutablex.mdx   |  2 +-
 .../connect-blockchain/other/polymesh.mdx     |  6 ++---
 .../connect-blockchain/other/starkex.mdx      |  6 ++---
 .../connect-blockchain/other/starknet.mdx     |  2 +-
 .../connect-blockchain/other/tezos.mdx        |  2 +-
 .../connect-blockchain/solana/android.mdx     |  8 +++----
 .../connect-blockchain/solana/flutter.mdx     |  6 ++---
 .../connect-blockchain/solana/ios.mdx         |  6 ++---
 .../connect-blockchain/solana/javascript.mdx  |  8 +++----
 .../connect-blockchain/solana/node.mdx        |  2 +-
 .../solana/react-native.mdx                   |  4 ++--
 .../connect-blockchain/solana/react.mdx       |  2 +-
 .../connect-blockchain/solana/unity.mdx       |  2 +-
 .../connect-blockchain/solana/vue.mdx         |  2 +-
 .../dashboard/advanced/custom-chains.mdx      |  4 ++--
 .../dashboard/advanced/session-management.mdx |  8 +++----
 38 files changed, 174 insertions(+), 167 deletions(-)

diff --git a/embedded-wallets/authentication/README.mdx b/embedded-wallets/authentication/README.mdx
index 46179c5226b..4e3aa6691cc 100644
--- a/embedded-wallets/authentication/README.mdx
+++ b/embedded-wallets/authentication/README.mdx
@@ -27,7 +27,7 @@ Provides passwordless log in via one-time passcodes (OTP)/ magic links sent to t
 
 ### External wallets
 
-Users can also authenticate using [third-party wallets](/embedded-wallets/authentication/basic-logins/external-wallets) such as MetaMask and other WalletConnect supported wallets. Developers can select which wallets to display via the Embedded Wallets Dashboard, providing tailored options based on user preference or regional relevance.
+Users can also authenticate using [third-party wallets](/embedded-wallets/authentication/basic-logins/external-wallets) such as MetaMask and other WalletConnect supported wallets. Developers can select which wallets to display via the dashboard, providing tailored options based on user preference or regional relevance.
 
 ### OAuth and social login
 
diff --git a/embedded-wallets/authentication/basic-logins/email-passwordless.mdx b/embedded-wallets/authentication/basic-logins/email-passwordless.mdx
index c2a4511d7a1..a50ba03dbf3 100644
--- a/embedded-wallets/authentication/basic-logins/email-passwordless.mdx
+++ b/embedded-wallets/authentication/basic-logins/email-passwordless.mdx
@@ -8,7 +8,7 @@ import EmailPasswordlessToggle from '@site/static/img/embedded-wallets/w3a-dashb
 import EmailPasswordlessAddConnection from '@site/static/img/embedded-wallets/w3a-dashboard/email-passwordless-add-connection.png'
 import EmailPasswordlessOnboarding from '@site/static/img/embedded-wallets/w3a-dashboard/email-passwordless-onboarding.gif'
 
-Web3Auth provides built-in support for email and SMS-based authentication, allowing users to log in seamlessly using a one-time passcode (OTP) sent to their email address or phone number. This form of passwordless authentication simplifies the onboarding process, removes friction for end users, and expands accessibility—especially in regions where social login options may be limited.
+Embedded Wallets provides built-in support for email and SMS-based authentication, allowing users to log in seamlessly using a one-time passcode (OTP) sent to their email address or phone number. This form of passwordless authentication simplifies the onboarding process, removes friction for end users, and expands accessibility—especially in regions where social login options may be limited.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -25,9 +25,9 @@ Web3Auth provides built-in support for email and SMS-based authentication, allow
 
 ## Set up a custom email connection
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To use this feature, developers must first enable `Email Passwordless` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+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.
 
@@ -47,11 +47,11 @@ To use this feature, developers must first enable `Email Passwordless` from the
 
 For enhanced control and branding, developers are encouraged to configure a custom email connection. Follow these steps:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-2. Go to the `Social Connections` section.
-3. Click the `Settings` icon next to the toggle for `Email Passwordless`.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+2. Navigate to the **Social Connections** section.
+3. Click the **Settings** icon (next to the toggle for **Email Passwordless**.
 4. Enter your custom `Auth Connection ID`.
-5. Click `Add Connection` to complete the setup.
+5. Click **Add Connection** to complete the setup.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/basic-logins/external-wallets.mdx b/embedded-wallets/authentication/basic-logins/external-wallets.mdx
index 64e98d8c734..46cbba32174 100644
--- a/embedded-wallets/authentication/basic-logins/external-wallets.mdx
+++ b/embedded-wallets/authentication/basic-logins/external-wallets.mdx
@@ -11,9 +11,9 @@ Web3Auth provides built-in support for email and SMS-based authentication, allow
 
 ## Enable external wallets
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To enable this feature, developers must first activate `External Wallets` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To enable this feature, developers must first activate **External Wallets** from the **Social Connections** section in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -29,11 +29,11 @@ To enable this feature, developers must first activate `External Wallets` from t
   />
 </div>
 
-To choose which external wallets to enable, click the `Settings` icon next to the **External Wallets** toggle in the Social Connections section of the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To choose which external wallets to enable, click the **Settings** icon next to the **External Wallets** toggle in the Social Connections section of the [dashboard](https://dashboard.web3auth.io).
 
 :::note
 
-Metamask Wallet is enabled by default and cannot be disabled.
+MetamMask Wallet is enabled by default and cannot be disabled.
 
 :::
 
diff --git a/embedded-wallets/authentication/basic-logins/sms-otp.mdx b/embedded-wallets/authentication/basic-logins/sms-otp.mdx
index a66ffeb3631..9cda2c45fe9 100644
--- a/embedded-wallets/authentication/basic-logins/sms-otp.mdx
+++ b/embedded-wallets/authentication/basic-logins/sms-otp.mdx
@@ -24,9 +24,9 @@ Web3Auth provides built-in support for email and SMS-based authentication, allow
 
 ## Set up a custom SMS OTP connection
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To use this feature, developers must first enable `SMS OTP` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+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.
 
@@ -46,11 +46,11 @@ To use this feature, developers must first enable `SMS OTP` from the Social Conn
 
 For enhanced control and branding, developers are encouraged to configure a custom SMS OTP connection. Follow these steps:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-2. Go to the `Social Connections` section.
-3. Click the `Settings` icon next to the toggle for `SMS OTP`.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+2. Go to the **Social Connections** section.
+3. Click the **Settings** icon next to the toggle for `SMS OTP`.
 4. Enter your custom `Auth Connection ID`.
-5. Click `Add Connection` to complete the setup.
+5. Click **Add Connection** to complete the setup.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/custom-connections/auth0.mdx b/embedded-wallets/authentication/custom-connections/auth0.mdx
index e5b8859dfb3..1c84b17181a 100644
--- a/embedded-wallets/authentication/custom-connections/auth0.mdx
+++ b/embedded-wallets/authentication/custom-connections/auth0.mdx
@@ -17,11 +17,11 @@ import ImplicitLoginAuth0Spa from '../../sdk/react/advanced/_custom-authenticati
 
 [Auth0](https://auth0.com/docs/get-started/auth0-overview) is a powerful authentication and authorization platform that enables developers to securely manage user identities. Web3Auth offers native support for integrating Auth0 as a service provider, allowing projects to leverage Auth0’s robust authentication mechanisms within the Web3Auth ecosystem.
 
-[Take a look at the supported social logins on Auth0](https://marketplace.auth0.com/categories/social-login)
+Auth0 supports a [wide set of social logins](https://marketplace.auth0.com/categories/social-login).
 
 ## Create an Auth0 application
 
-To begin, developers must first create an Auth0 application specific to their project. This initial setup is essential before configuring the connection with Web3Auth. Once the Auth0 application is created, developers can proceed to establish an Auth0 connection within the Embedded Wallets Dashboard.
+To begin, developers must first create an Auth0 application specific to their project. This initial setup is essential before configuring the connection with Web3Auth. Once the Auth0 application is created, developers can proceed to establish an Auth0 connection within the [dashboard](https://dashboard.web3auth.io).
 
 This integration allows users to authenticate through Auth0, while still benefiting from Web3Auth’s key management and wallet abstraction features. For platform-specific implementation details or additional customization, developers are encouraged to refer to the [official Auth0 documentation](https://auth0.com/docs/quickstart/native#webapp).
 
@@ -68,9 +68,9 @@ export const Auth0Setup = [
 
 ## Create an Auth0 connection
 
-:::success Create Auth0 Connection on Dashboard
+:::success Connect Auth0
 
-To use this feature, developers must go to the `Custom Connections` tab in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, developers must go to the **Custom Connections** tab in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -88,15 +88,15 @@ To use this feature, developers must go to the `Custom Connections` tab in the [
 
 Follow these steps to create an Auth0 connection:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-2. Go to the `Custom Connections` section.
-3. Click on the `Settings` icon near the Auth0 connection.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+2. Go to the **Custom Connections** section.
+3. Click on the **Settings** icon near the Auth0 connection.
 4. Enter the `Auth Connection ID`.
-5. Select the `JWT user identifier`: `email`, `sub` or `custom`.
-6. Toggle the Case Sensitivity of `User Identifier`. (Optional)
+5. Select the **JWT user identifier**: `email`, `sub` or `custom`.
+6. (Optional) Toggle the case sensitivity of **User Identifier**.
 7. Enter `Auth0 Client ID`.
 8. Enter `Auth0 Domain`.
-9. Finally, click on the `Add Connection` button.
+9. Click on the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
index 3e4d0e14a81..e1b41248829 100644
--- a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
+++ b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
@@ -10,21 +10,21 @@ import ImplicitLoginCognito from '../../sdk/react/advanced/_custom-authenticatio
 
 [AWS Cognito](https://aws.amazon.com/cognito/) is a scalable authentication service provided by Amazon Web Services that enables developers to securely manage user sign-up, sign-in, and access control. Web3Auth supports AWS Cognito as a service provider, allowing seamless integration between AWS Cognito’s authentication capabilities and Web3Auth’s decentralized key management infrastructure.
 
-[Take a look at the supported social logins on AWS Cognito](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-social-idp.html)
+AWS Cognito [supports a wide set of social logins](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-social-idp.html).
 
 ## Create an AWS Cognito application
 
 To begin the integration process, developers must first create a new AWS Cognito application using the [AWS Management Console](https://console.aws.amazon.com/). This initial setup is required before configuring the connection within Web3Auth.
 
-Once the AWS Cognito application is created, developers can proceed to add it as a custom connection in the Embedded Wallets Dashboard.
+Once the AWS Cognito application is created, developers can proceed to add it as a custom connection in the dashboard.
 
 [Learn how to set up AWS Cognito](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-console).
 
 ## Create an AWS Cognito connection
 
-:::success Create AWS Cognito Connection on Dashboard
+:::success Create AWS Cognito Connection
 
-To use this feature, developers must go to the `Custom Connections` tab in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, developers must go to the **Custom Connections** tab in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -42,18 +42,18 @@ To use this feature, developers must go to the `Custom Connections` tab in the [
 
 Follow these steps to create a AWS Cognito connection:
 
-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 `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. Paste a sample `JWT Token` to auto populate the best **JWT validations** possible.
 1. Select the `JWT user identifier`: `email`, `sub` or `custom`.
 1. Toggle the Case Sensitivity of `User Identifier`. (Optional)
-1. Click on `Add Custom Validations` to add validations manually.
+1. Click on **Add Custom Validations** to add validations manually.
    1. Type iss as a field and `https://cognito-idp.{REGION}.amazonaws.com/{USER_POOL_ID}` as a value.
    1. Next, type aud as a field and `APP_CLIENT_ID` as a value.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 > Note: Replace the `REGION`, `USER_POOL_ID` and `APP_CLIENT_ID` with your Cognito specific details.
 
diff --git a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
index 367be2fc5a1..f7ea3e98ac3 100644
--- a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
+++ b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
@@ -12,17 +12,17 @@ import CustomConnectionOptions from '@site/static/img/embedded-wallets/w3a-dashb
 import CustomJWTConnection from '@site/static/img/embedded-wallets/w3a-dashboard/custom-connection.png'
 import JwtLoginCustom from '../../sdk/react/advanced/_custom-authentication-snippets/_jwt_login_custom.mdx'
 
-Web3Auth supports integration with custom login providers through [JWT-based](https://www.jwt.io/introduction#what-is-json-web-token) authentication schemes, allowing developers to maintain their existing authentication infrastructure while leveraging Web3Auth’s wallet and key management capabilities. Custom authentication can be implemented using industry-standard cryptographic algorithms such as RSA or ECDSA signatures.
+Embedded Wallets supports integration with custom login providers through [JWT-based](https://www.jwt.io/introduction#what-is-json-web-token) authentication schemes, allowing developers to maintain their existing authentication infrastructure while leveraging Web3Auth’s wallet and key management capabilities. Custom authentication can be implemented using industry-standard cryptographic algorithms such as RSA or ECDSA signatures.
 
 To use this feature, developers must ensure that their JWTs adhere to the [JWT specification](https://datatracker.ietf.org/doc/html/rfc7519). Each JWT must be signed using a private key, and its corresponding public key must be accessible via a [JWKS (JSON Web Key Set)](https://datatracker.ietf.org/doc/html/rfc7517) endpoint. Web3Auth will use this endpoint to verify the integrity and authenticity of incoming tokens during login.
 
-Once the custom JWT login is working, developers can proceed to add it as a custom connection in the Embedded Wallets Dashboard.
+Once the custom JWT login is working, developers can proceed to add it as a custom connection in the dashboard.
 
 ## Set up a custom JWT connection
 
-:::success Create Custom Connection on Dashboard
+:::success Create Custom Connection
 
-To use this feature, developers must go to the `Custom Connections` tab in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, developers must go to the **Custom Connections** tab in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -41,17 +41,17 @@ 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. Go to the `Custom Connections` section.
-1. Click on the `Settings` icon near the `Custom Connection`.
+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. Toggle the Case Sensitivity of `User Identifier`. (Optional)
-1. Click on `Add Custom Validations` to add validations manually.
+1. Click on **Add Custom Validations** to add validations manually.
    1. Type iss as a field and `your-issuer` as a value.
    1. Next, type aud as a field and `your-audience` as a value.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -241,13 +241,13 @@ console.log(payload)
 
 :::warning Facing issue with JWT?
 
-Check out [**this troubleshooting page to fix those.**](/embedded-wallets/troubleshooting/jwt-errors)
+Check out the [troubleshooting page](/embedded-wallets/troubleshooting/jwt-errors).
 
 :::
 
 ## 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.
 
@@ -297,10 +297,10 @@ If you're using `jose` or `jsonwebtoken` library, you can use the following step
      - Select Public Key Use: `Signing`
      - Key ID: `paste-yours` or leave it blank to generate a random one.
      - PEM encoded key: `{paste-the-publicKey-pem-file-s-content-here}`
-   - Click on the `Convert to JWK` button.
+   - Click on the **Convert to JWK** button.
 
      ![JWKS Convert Tool](https://web3auth.io/community/uploads/default/optimized/2X/3/3e58a3b7378b9778b0b2d646ec2a3cf47c56ee5e_2_690x448.jpeg)
 
 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.
diff --git a/embedded-wallets/authentication/custom-connections/firebase.mdx b/embedded-wallets/authentication/custom-connections/firebase.mdx
index 6a653220253..c75ac0b4eea 100644
--- a/embedded-wallets/authentication/custom-connections/firebase.mdx
+++ b/embedded-wallets/authentication/custom-connections/firebase.mdx
@@ -12,15 +12,18 @@ import JwtLoginFirebase from '../../sdk/react/advanced/_custom-authentication-sn
 
 [Firebase](https://firebase.google.com/) is a popular backend platform that enables developers to seamlessly integrate authentication, databases, and other services into their applications. Web3Auth supports Firebase as an authentication provider, allowing developers to leverage Firebase Authentication within the Web3Auth framework for secure user login and key management.
 
-[Take a look at the supported social logins on Firebase](https://firebase.google.com/docs/auth)
+Firebase [supports a wide set of social logins](https://firebase.google.com/docs/auth).
 
 ## Create a Firebase project
 
-To get started, developers must first create a Firebase project in the Firebase Console. This is a required step before integrating Firebase with Web3Auth. Once the Firebase project is set up, developers can proceed to configure a Firebase connection in the Embedded Wallets Dashboard.
+To get started, developers must first create a Firebase project in the Firebase Console. This is a required step before integrating Firebase with Web3Auth. Once the Firebase project is set up, developers can proceed to configure a Firebase connection in the dashboard.
 
 Web3Auth’s Firebase integration enables the use of Firebase-issued ID tokens to authenticate users, combining Firebase’s authentication flexibility with Web3Auth’s decentralized key infrastructure.
 
+:::tip
+
 For detailed implementation steps and platform-specific instructions, developers can follow the [Firebase documentation](https://firebase.google.com/docs).
+:::
 
 export const FirebaseSetup = [
   {
@@ -65,9 +68,9 @@ export const FirebaseSetup = [
 
 ## Create a Firebase connection
 
-:::success Create Firebase Connection on Dashboard
+:::success Create Firebase Connection
 
-To use this feature, developers must go to the `Custom Connections` tab in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, developers must go to the **Custom Connections** tab in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -85,18 +88,18 @@ To use this feature, developers must go to the `Custom Connections` tab in the [
 
 Follow these steps to create a Firebase connection:
 
-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 Firebase connection.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+1. Go to the **Custom Connections** section.
+1. Click on the **Settings** icon near the Firebase connection.
 1. Enter the `Firebase Connection ID`.
 1. Paste `https://www.googleapis.com/service_accounts/v1/jwk/securetoken@system.gserviceaccount.com` 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. Toggle the Case Sensitivity of `User Identifier`. (Optional)
-1. Click on `Add Custom Validations` to add validations manually.
+1. Click on **Add Custom Validations** to add validations manually.
    1. Type iss as a field and `https://securetoken.google.com/FIREBASE-PROJECT-ID` as a value.
    1. Next, type aud as a field and `FIREBASE-PROJECT-ID` as a value.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -112,7 +115,7 @@ 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.
 
diff --git a/embedded-wallets/authentication/group-connections.mdx b/embedded-wallets/authentication/group-connections.mdx
index d1eab022c9b..c3d1c5e2960 100644
--- a/embedded-wallets/authentication/group-connections.mdx
+++ b/embedded-wallets/authentication/group-connections.mdx
@@ -17,15 +17,19 @@ 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 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.
 
-> _Before setting up a group connection, developers must first configure individual login connections that are eligible._
+:::note
+
+Before setting up a group connection, developers must first configure individual login connections that are eligible.
+
+:::
 
 ## Set up a group connection
 
-:::success Create Group Connection on Dashboard
+:::success Create a group connection
 
-To use this feature, developers must go to the `Group Connections` tab in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, developers use the **Group Connections** tab in the [dashboard](https://dashboard.web3auth.io).
 
 :::
 
@@ -43,12 +47,12 @@ To use this feature, developers must go to the `Group Connections` tab in the [E
 
 Follow these steps:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-2. Go to the `Group Connections` section.
-3. Click on the `Create Group` button.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+2. Go to the **Group Connections** section.
+3. Click on the **Create Group** button.
 4. Enter your custom `Group Name`.
 5. Select `1st social connection` and `2nd social connection`.
-6. Click `Create Group`.
+6. Click **Create Group**.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -76,7 +80,7 @@ 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.
 
diff --git a/embedded-wallets/authentication/id-token.mdx b/embedded-wallets/authentication/id-token.mdx
index 1167d68f1a3..24b9cb78a64 100644
--- a/embedded-wallets/authentication/id-token.mdx
+++ b/embedded-wallets/authentication/id-token.mdx
@@ -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 Embedded Wallets 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.
 
 :::
 
@@ -320,7 +320,7 @@ const validateIdToken = async () => {
 
 ### Using the verification key
 
-To manually verify the token, use your **Verification Key** available on the **Project Settings** page in the Embedded Wallets Dashboard.
+To manually verify the token, use your **Verification Key** available on the **Project Settings** page in the dashboard.
 
 <Tabs
 defaultValue="jose"
@@ -380,7 +380,7 @@ try {
 
 :::info
 
-If the token is valid, the payload will contain identity claims (e.g., userId). If invalid, an error is thrown.
+If the token is valid, the payload will contain identity claims (such as, userId). If invalid, an error is thrown.
 
 :::
 
diff --git a/embedded-wallets/authentication/social-logins/discord.mdx b/embedded-wallets/authentication/social-logins/discord.mdx
index f2dcb90a1f7..1d001a2eeef 100644
--- a/embedded-wallets/authentication/social-logins/discord.mdx
+++ b/embedded-wallets/authentication/social-logins/discord.mdx
@@ -7,11 +7,11 @@ description: 'Discord Social Login with Embedded Wallets | Embedded Wallets'
 import DiscordToggle from '@site/static/img/embedded-wallets/w3a-dashboard/authentication-social-connections.png'
 import DiscordConnection from '@site/static/img/embedded-wallets/w3a-dashboard/discord-connection.png'
 
-[Discord Login](https://discord.com/developers/docs/topics/oauth2) is a social login provider that allows users to sign in using their Discord credentials. Web3Auth supports Discord as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Discord accounts.
+[Discord login](https://discord.com/developers/docs/topics/oauth2) is a social login provider that allows users to sign in using their Discord credentials. Embedded Wallets supports Discord as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Discord accounts.
 
 To integrate Discord with Web3Auth, developers must first create a Discord App via the [Discord Developer Portal](https://discord.com/developers/applications).
 
-## Create a Discord app
+## Step 1: Create a Discord app
 
 1. Create a Discord [API application](https://discord.com/developers/applications).
 
@@ -22,15 +22,15 @@ To integrate Discord with Web3Auth, developers must first create a Discord App v
 
 3. Don't forget to save your changes!
 
-4. Next, obtain the **"Client ID"** from here. We will use this in our Embedded Wallets Dashboard.
+4. Next, obtain the **Client ID** from here. We will use this in our Embedded Wallets Dashboard.
 
    ![Discord OAuth2.0 App Client ID and Secret](/img/embedded-wallets/authentication/discord/discord-clientid-secret.png)
 
-## Create a Discord connection
+## Step 2: Create a Discord connection
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To use this feature, please enable `Discord` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, please enable `Discord` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Discord login.
 
@@ -50,12 +50,12 @@ To use this feature, please enable `Discord` from the Social Connections section
 
 Follow these steps to create a Discord connection:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-1. Go to the `Social Connections` section.
-1. Click on the `Settings` icon near the Discord connection.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+1. Go to the **Social Connections** section.
+1. Click on the **Settings** icon near the Discord connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Discord Client ID`.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -71,7 +71,7 @@ Follow these steps to create a Discord connection:
 
 ## Usage
 
-Since, the `Discord Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the Discord 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.
 
diff --git a/embedded-wallets/authentication/social-logins/facebook.mdx b/embedded-wallets/authentication/social-logins/facebook.mdx
index 5fa40fcbee5..2602d42dea2 100644
--- a/embedded-wallets/authentication/social-logins/facebook.mdx
+++ b/embedded-wallets/authentication/social-logins/facebook.mdx
@@ -8,11 +8,11 @@ import FacebookToggle from '@site/static/img/embedded-wallets/w3a-dashboard/auth
 import FacebookConnection from '@site/static/img/embedded-wallets/w3a-dashboard/facebook-connection.png'
 import ImplicitLoginFacebook from '../../sdk/react/advanced/_custom-authentication-snippets/_implicit_login_facebook.mdx'
 
-[Facebook Login](https://developers.facebook.com/docs/facebook-login/) enables users to sign in using their Facebook credentials. Web3Auth supports Facebook as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Facebook accounts.
+[Facebook login](https://developers.facebook.com/docs/facebook-login/) enables users to sign in using their Facebook credentials. Embedded Wallets supports Facebook as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Facebook accounts.
 
 To integrate Facebook with Web3Auth, developers must first create a Facebook App via the [Meta for Developers Console](https://developers.facebook.com/).
 
-## Create a Facebook app
+## Step 1: Create a Facebook app
 
 1. Follow Facebook's instructions to [create a new app](https://developers.facebook.com/docs/development/create-an-app).
 2. When creating an app, make sure to select `Consumer` from this screen to use Facebook Login. ![Facebook OAuth2.0 App Dashboard](/img/embedded-wallets/authentication/facebook/facebook-app.png)
@@ -30,7 +30,7 @@ To integrate Facebook with Web3Auth, developers must first create a Facebook App
 
    ![Facebook OAuth2.0 App Dashboard](/img/embedded-wallets/authentication/facebook/facebook-app-id-secret.png)
 
-## Create a Facebook connection
+## Step 2: Create a Facebook connection
 
 :::success Enable on Dashboard
 
@@ -55,12 +55,12 @@ To use this feature, please enable `Facebook` from the Social Connections sectio
 Follow these steps to create a Facebook connection:
 
 1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-1. Go to the `Social Connections` section.
-1. Click on the `Settings` icon near the Facebook connection.
+1. Go to the **Social Connections** section.
+1. Click on the **Settings** icon near the Facebook connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Facebook App ID`.
 1. Enter the `Facebook App Secret`.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -76,7 +76,7 @@ Follow these steps to create a Facebook connection:
 
 ## Usage
 
-Since, the `Facebook Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the Facebook 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.
 
diff --git a/embedded-wallets/authentication/social-logins/google.mdx b/embedded-wallets/authentication/social-logins/google.mdx
index 4dbeaad145c..e0e67bfd45d 100644
--- a/embedded-wallets/authentication/social-logins/google.mdx
+++ b/embedded-wallets/authentication/social-logins/google.mdx
@@ -12,11 +12,11 @@ import GoogleConnection from '@site/static/img/embedded-wallets/w3a-dashboard/go
 import JwtLoginGoogle from '../../sdk/react/advanced/_custom-authentication-snippets/_jwt_login_google_one_tap.mdx'
 import ImplicitLoginGoogle from '../../sdk/react/advanced/_custom-authentication-snippets/_implicit_login_google.mdx'
 
-[Google Sign-In](https://developers.google.com/identity/sign-in/web/sign-in) is a widely adopted authentication method that allows users to log in using their existing Google accounts. Web3Auth supports Google as a social login provider, enabling seamless onboarding and authentication experiences for users with Google credentials.
+[Google Sign-In](https://developers.google.com/identity/sign-in/web/sign-in) is a widely adopted authentication method that allows users to log in using their existing Google accounts. Embedded Wallets supports Google as a social login provider, enabling seamless onboarding and authentication experiences for users with Google credentials.
 
-To integrate Google Sign-In with Web3Auth, developers must first configure a Google OAuth 2.0 Client ID in the Google Cloud Console.
+To integrate Google Sign-In with Embedded Wallets, developers must first configure a Google OAuth 2.0 Client ID in the Google Cloud Console.
 
-## Create a Google app
+## Step 1: Create a Google app
 
 1. Follow Google’s instructions to [set up an OAuth 2.0 app.](https://support.google.com/cloud/answer/6158849?hl=en)
 2. Paste the following URI as a redirect URI into the "Authorized redirect URIs" field.
@@ -26,11 +26,11 @@ To integrate Google Sign-In with Web3Auth, developers must first configure a Goo
 
 3. Obtain the OAuth `Client ID` from the [App on the Google Developer dashboard](https://console.developers.google.com/)
 
-## Create a Google connection
+## Step 2: Create a Google connection
 
 :::success Enable on Dashboard
 
-To use this feature, please enable `Google` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, please enable **Google** from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Google login.
 
@@ -51,11 +51,11 @@ To use this feature, please enable `Google` from the Social Connections section
 Follow these steps to create a Google connection:
 
 1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-1. Go to the `Social Connections` section.
-1. Click on the `Settings` icon near the Google connection.
+1. Go to the **Social Connections** section.
+1. Click on the **Settings** icon near the Google connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Google Client ID`.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -71,7 +71,7 @@ Follow these steps to create a Google connection:
 
 ## Usage
 
-Since, the `Google Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the Google 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.
 
diff --git a/embedded-wallets/authentication/social-logins/oauth.mdx b/embedded-wallets/authentication/social-logins/oauth.mdx
index f67ae9f954d..f29a4fb2c6b 100644
--- a/embedded-wallets/authentication/social-logins/oauth.mdx
+++ b/embedded-wallets/authentication/social-logins/oauth.mdx
@@ -8,9 +8,9 @@ import OAuthToggle from '@site/static/img/embedded-wallets/w3a-dashboard/authent
 
 [OAuth 2.0](https://oauth.net/2/) is a widely adopted standard that enables users to authenticate with third-party identity providers in a secure and user-friendly manner. Web3Auth offers native support for multiple OAuth 2.0 login options, allowing developers to integrate familiar authentication experiences directly into their applications.
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To use this feature, please enable `X(Twitter)`, `Farcaster`, `Apple`, `GitHub`, `Reddit`, `Line`, `Kakao`, `LinkedIn` or `Wechat` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, please enable X(Twitter), Farcaster, Apple, GitHub, Reddit, Line, Kakao, LinkedIn, or WeChat from the **Social Connections** section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for different social login providers.
 
diff --git a/embedded-wallets/authentication/social-logins/twitch.mdx b/embedded-wallets/authentication/social-logins/twitch.mdx
index 1b1d3443345..1136e9f48cc 100644
--- a/embedded-wallets/authentication/social-logins/twitch.mdx
+++ b/embedded-wallets/authentication/social-logins/twitch.mdx
@@ -7,13 +7,13 @@ description: 'Twitch Social Login with Embedded Wallets | Embedded Wallets'
 import TwitchToggle from '@site/static/img/embedded-wallets/w3a-dashboard/authentication-social-connections.png'
 import TwitchConnection from '@site/static/img/embedded-wallets/w3a-dashboard/twitch-connection.png'
 
-Twitch supports social login, allowing users to [sign in using their Twitch credentials](https://dev.twitch.tv/docs/authentication/#user-access-tokens). Web3Auth supports Twitch as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Twitch accounts.
+Twitch supports social login, allowing users to [sign in using their Twitch credentials](https://dev.twitch.tv/docs/authentication/#user-access-tokens). Embedded Wallets supports Twitch as a social login provider, allowing developers to offer a familiar and quick authentication method for users with Twitch accounts.
 
 ## Prerequisites
 
 - Registered [Twitch App](https://dev.twitch.tv/docs/authentication/#registration)
 
-## Create a Twitch app
+## Step 1: Create a Twitch app
 
 1. Follow Twitch's [registration instructions](https://dev.twitch.tv/docs/authentication/#registration) to [register your app](https://dev.twitch.tv/console/apps/create).
 2. Paste the following as a Redirect URI into the "OAuth Redirect URLs" field.
@@ -29,11 +29,11 @@ Twitch supports social login, allowing users to [sign in using their Twitch cred
 
    ![Twitch OAuth2.0 App Manage](/img/embedded-wallets/authentication/twitch/twitch-client-id.png)
 
-## Create a Twitch connection
+## Step 2: Create a Twitch connection
 
-:::success Enable on Dashboard
+:::success Enable on dashboard
 
-To use this feature, please enable `Twitch` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, please enable `Twitch` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Twitch login.
 
@@ -53,12 +53,12 @@ To use this feature, please enable `Twitch` from the Social Connections section
 
 Follow these steps to create a Twitch connection:
 
-1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
-1. Go to the `Social Connections` section.
-1. Click on the `Settings` icon near the Twitch connection.
+1. Visit the [dashboard](https://dashboard.web3auth.io).
+1. Go to the **Social Connections** section.
+1. Click on the **Settings** icon near the Twitch connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Twitch Client ID`.
-1. Finally, click on the `Add Connection` button.
+1. Finally, click on the **Add Connection** button.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -74,7 +74,7 @@ Follow these steps to create a Twitch connection:
 
 ## Usage
 
-Since, the `Twitch Connection` details are available from the dashboard, developers don't need to pass any additional parameters to the `Web3AuthProvider`.
+Since, the Twitch 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.
 
diff --git a/embedded-wallets/connect-blockchain/_flutter-connect-blockchain/_evm-interaction.mdx b/embedded-wallets/connect-blockchain/_flutter-connect-blockchain/_evm-interaction.mdx
index b521f67b0e1..3ee23d561cd 100644
--- a/embedded-wallets/connect-blockchain/_flutter-connect-blockchain/_evm-interaction.mdx
+++ b/embedded-wallets/connect-blockchain/_flutter-connect-blockchain/_evm-interaction.mdx
@@ -29,7 +29,7 @@ This doc assumes you have already setup your project in the Embedded Wallets Das
 
 <GetBalanceSnippet />
 
-## Sign Transaction
+## Sign a transaction
 
 <SignTransactionSnippet />
 
@@ -37,15 +37,15 @@ This doc assumes you have already setup your project in the Embedded Wallets Das
 
 <SendTransactionSnippet />
 
-## Smart Contract Interactions
+## Smart contract interactions
 
 <TestContractSnippet />
 
-### Deploy Contract
+### Deploy a contract
 
 <DeployContractSnippet />
 
-### Read From Contract
+### Read from contract
 
 <ReadContractSnippet />
 
diff --git a/embedded-wallets/connect-blockchain/evm/rpc-headers.mdx b/embedded-wallets/connect-blockchain/evm/rpc-headers.mdx
index ecc8f0ed113..c7498546736 100644
--- a/embedded-wallets/connect-blockchain/evm/rpc-headers.mdx
+++ b/embedded-wallets/connect-blockchain/evm/rpc-headers.mdx
@@ -6,7 +6,7 @@ image: 'img/metamaskog.jpg'
 description: 'How to securely attach API keys to blockchain RPC requests | Embedded Wallets'
 ---
 
-### Adding API Keys in RPC Headers
+### Adding API keys in RPC headers
 
 MetaMask Embedded Wallets allows you to specify the RPC endpoint URL, but it doesn't directly provide an option to set custom HTTP headers such as API keys required by certain blockchain providers. To accommodate blockchain APIs that require authentication headers, you need to manually intercept and attach these headers to your application's outgoing RPC requests.
 
@@ -24,16 +24,16 @@ If you're using TRON's mainnet RPC endpoint (`https://api.trongrid.io`), you may
 
 :::
 
-### Identifying RPC Host URL
+### Identifying the RPC host URL
 
 First, identify the hostname for your RPC provider by checking the network logs in your browser:
 
 1. Open your browser's Developer Tools (`Network` tab).
-2. Execute a blockchain-related action (e.g., fetching balance).
-3. Locate the RPC request URL (e.g., `https://api.trongrid.io/jsonrpc`).
-4. Note the hostname (e.g., `api.trongrid.io`).
+2. Execute a blockchain-related action (for example, fetching balance).
+3. Locate the RPC request URL (for example, `https://api.trongrid.io/jsonrpc`).
+4. Note the hostname (for example, `api.trongrid.io`).
 
-### Adding Headers via Global `fetch` Patch
+### Adding headers via global `fetch` patch
 
 Create a file named `globals.js` and include the following code snippet:
 
@@ -75,7 +75,7 @@ globalThis.fetch = (...args) => {
 
 Replace `"YOUR_TRON_API_KEY"` with the actual API key provided by your blockchain RPC provider.
 
-### Importing the Patch into Your Application
+### Importing the patch into your application
 
 Make sure to import this file at the very beginning of your application's entry point (`index.tsx` or `main.ts`):
 
@@ -89,7 +89,7 @@ Perform this operation with caution. Avoid exposing sensitive API keys within cl
 
 :::
 
-### Why This Approach Works
+### Why this approach works
 
 - MetaMask Embedded Wallets SDK uses the provided RPC URL configured via the developer dashboard.
 - Blockchain SDKs like `TronWeb` internally use the global `fetch` API.
diff --git a/embedded-wallets/connect-blockchain/evm/tron/web.mdx b/embedded-wallets/connect-blockchain/evm/tron/web.mdx
index 47bbfcf7ad4..0a62c9e5f40 100644
--- a/embedded-wallets/connect-blockchain/evm/tron/web.mdx
+++ b/embedded-wallets/connect-blockchain/evm/tron/web.mdx
@@ -114,7 +114,7 @@ Once logged in, Web3Auth provides a JWT token and access to the Tron provider.
 
 ---
 
-## Fetching User Info
+## Fetching user info
 
 After logging in, you can retrieve information about the user.
 
diff --git a/embedded-wallets/connect-blockchain/other/README.mdx b/embedded-wallets/connect-blockchain/other/README.mdx
index 6f55a21dfb7..0038dc70d06 100644
--- a/embedded-wallets/connect-blockchain/other/README.mdx
+++ b/embedded-wallets/connect-blockchain/other/README.mdx
@@ -129,7 +129,7 @@ export const OtherChains = [
 
 }, ];
 
-## Non EVM chain guides
+## Non-EVM chain guides
 
 You can checkout the following guides we've written for certain non EVM blockchains. The approach mentioned in this doc is very similar to the one followed in each one of them.
 
diff --git a/embedded-wallets/connect-blockchain/other/algorand.mdx b/embedded-wallets/connect-blockchain/other/algorand.mdx
index 0e7664ed72c..95d6569ca9c 100644
--- a/embedded-wallets/connect-blockchain/other/algorand.mdx
+++ b/embedded-wallets/connect-blockchain/other/algorand.mdx
@@ -172,7 +172,7 @@ let signedTxn = algosdk.signTransaction(txn, keyPair.sk)
 const txHash = await client.sendRawTransaction(signedTxn.blob).do()
 ```
 
-## Sign Message
+## Sign a message
 
 ```tsx
 import { IProvider } from '@web3auth/base'
diff --git a/embedded-wallets/connect-blockchain/other/aptos.mdx b/embedded-wallets/connect-blockchain/other/aptos.mdx
index f0ac893e3a1..7a731467bb5 100644
--- a/embedded-wallets/connect-blockchain/other/aptos.mdx
+++ b/embedded-wallets/connect-blockchain/other/aptos.mdx
@@ -11,7 +11,7 @@ import InitializeWeb3Auth from '../_initialize-web3auth-other-pnp.mdx'
 import TabItem from '@theme/TabItem'
 import Tabs from '@theme/Tabs'
 
-While using the Embedded Wallets Web SDK (formerly Web3Auth) for a non-EVM chain like [Aptos](https://aptos.dev/), you can obtain the user's private key from the provider. Using this private key, you can use the corresponding libraries of the blockchain to make calls like fetching the user's `account`, retrieving `balance`, `signing transactions`, `sending transactions`, or interacting with smart contracts. We will focus on Testnet for this guide.
+While using the Embedded Wallets Web SDK for a non-EVM chain like [Aptos](https://aptos.dev/), you can obtain the user's private key from the provider. Using this private key, you can use the corresponding libraries of the blockchain to make calls like fetching the user's `account`, retrieving `balance`, `signing transactions`, `sending transactions`, or interacting with smart contracts. We will focus on testnet for this guide.
 
 ::::note
 
@@ -19,9 +19,9 @@ The SDKs are now branded as MetaMask Embedded Wallet SDKs (formerly Web3Auth Plu
 
 ::::
 
-## Aptos Configuration and Enums
+## Aptos configuration and enums
 
-For configuring Aptos, we will use the `AptosConfig` class from the `@aptos-labs/ts-sdk` package. The network parameter in `AptosConfig` uses an enum, which allows us to select the network environment (e.g., **Testnet**).
+For configuring Aptos, we will use the `AptosConfig` class from the `@aptos-labs/ts-sdk` package. The network parameter in `AptosConfig` uses an enum, which allows us to select the network environment (such as, 'testnet').
 
 Here are the available networks in the enum:
 
@@ -93,7 +93,7 @@ npm install --save @aptos-labs/ts-sdk
 </TabItem>
 </Tabs>
 
-## Get account and Key
+## Get account and key
 
 Once a user logs in, the Embedded Wallets SDK returns a provider. Since there isn't a native provider for Aptos, we use the private key directly for making RPC calls.
 
@@ -179,7 +179,7 @@ const committedTxn = await aptos.transaction.submit.simple({
 await aptos.waitForTransaction({ transactionHash: committedTxn.hash })
 ```
 
-## Airdrop Request
+## Airdrop request
 
 You can request test tokens (Aptos coins) for your account by using the `getAirdrop` method in the testnet environment. This allows you to receive a certain amount of AptosCoin for testing purposes.
 
@@ -217,4 +217,4 @@ This method will provide your account with test APT from Aptos Testnet, which ca
 
 ## Conclusion
 
-With Web3Auth and Aptos integration, you can easily set up authentication for your Aptos dApps, get account information, check balances, and even send transactions.
+With Web3Auth and Aptos integration, you can easily set up authentication for your Aptos dapps, get account information, check balances, and even send transactions.
diff --git a/embedded-wallets/connect-blockchain/other/cosmos.mdx b/embedded-wallets/connect-blockchain/other/cosmos.mdx
index f41586ebb2a..69cef2ba04b 100644
--- a/embedded-wallets/connect-blockchain/other/cosmos.mdx
+++ b/embedded-wallets/connect-blockchain/other/cosmos.mdx
@@ -65,7 +65,7 @@ npm install --save @web3auth/no-modal @web3auth/auth-adapter @web3auth/base @cos
 </TabItem>
 </Tabs>
 
-## Get ChainID
+## Get Chain ID
 
 Once a user logs in, the Embedded Wallets SDK returns a provider. Since there isn't a native provider for Cosmos, we directly use the private key to make RPC calls.
 
diff --git a/embedded-wallets/connect-blockchain/other/immutablex.mdx b/embedded-wallets/connect-blockchain/other/immutablex.mdx
index 2c0b0288548..76f0f18a681 100644
--- a/embedded-wallets/connect-blockchain/other/immutablex.mdx
+++ b/embedded-wallets/connect-blockchain/other/immutablex.mdx
@@ -65,7 +65,7 @@ npm install --save @imtbl/core-sdk
 </TabItem>
 </Tabs>
 
-## Creating Layer 1 and Layer 2 Signers
+## Creating Layer 1 and Layer 2 signers
 
 Once a user logs in, the Embedded Wallets SDK returns a provider. ImmutableX is a layer 2 solution for Ethereum, so we’ll create an ETH signer using the provider (via ethers). Then we use the helper function `createStarkSigner` from `@imtbl/core-sdk` to create a Stark signer from the private key.
 
diff --git a/embedded-wallets/connect-blockchain/other/polymesh.mdx b/embedded-wallets/connect-blockchain/other/polymesh.mdx
index 6ef53a6f5b4..d8cdc7405cb 100644
--- a/embedded-wallets/connect-blockchain/other/polymesh.mdx
+++ b/embedded-wallets/connect-blockchain/other/polymesh.mdx
@@ -11,7 +11,7 @@ import InitializeWeb3Auth from '../_initialize-web3auth-other-pnp.mdx'
 import TabItem from '@theme/TabItem'
 import Tabs from '@theme/Tabs'
 
-While using the Embedded Wallets Web SDK (formerly Web3Auth) for a non-EVM chain like [Polymesh](https://www.polymesh.network/), you can get the user's private key from the provider. Using this private key, you can use the corresponding libraries of the blockchain to make blockchain calls like getting the user's public `signing key`, fetching `balance`, and `sign & send transaction`. We have highlighted a few methods here to get you started quickly.
+While using the Embedded Wallets Web SDK for a non-EVM chain like [Polymesh](https://www.polymesh.network/), you can get the user's private key from the provider. Using this private key, you can use the corresponding libraries of the blockchain to make blockchain calls like getting the user's public `signing key`, fetching `balance`, and `sign & send transaction`. We have highlighted a few methods here to get you started quickly.
 
 ::::note
 
@@ -91,7 +91,7 @@ const localSigningManager = await LocalSigningManager.create({
 })
 ```
 
-At this point if we were to query the public key derived from the private key by calling `localSigningManager.getAccounts()` the function would throw an error as a SS58 prefix for the chain has not been set. The SS58 prefix can be set manually by calling e.g. `localSigningManager.setSs58Format(12)`, or by attaching the signing manager to an instance of the Polymesh SDK which will automatically read the correct SS58 prefix from the chain and set it in the signing manager.
+At this point if we were to query the public key derived from the private key by calling `localSigningManager.getAccounts()` the function would throw an error as a SS58 prefix for the chain has not been set. The SS58 prefix can be set manually, for example, by calling `localSigningManager.setSs58Format(12)`, or by attaching the signing manager to an instance of the Polymesh SDK which will automatically read the correct SS58 prefix from the chain and set it in the signing manager.
 
 <Tabs
  groupId="chain"
@@ -159,7 +159,7 @@ console.log(`Public Key: ${signingAccount.address}`)
 const balance = await polymeshApi.accountManagement.getAccountBalance()
 ```
 
-## Get The Associated Identity ID
+## Get the associated identity ID
 
 Before a key on Polymesh can receive tokens or transact on chain it must be associated with an onchain identity. A new identity can be assigned by a permissioned Certified Due Diligence (CDD) provider or you can add the key to an existing identity. Individuals can onboard their key by visiting https://testnet-onboarding.polymesh.live/ or https://mainnet-onboarding.polymesh.network/.
 
diff --git a/embedded-wallets/connect-blockchain/other/starkex.mdx b/embedded-wallets/connect-blockchain/other/starkex.mdx
index 9501158161f..94fac7c1550 100644
--- a/embedded-wallets/connect-blockchain/other/starkex.mdx
+++ b/embedded-wallets/connect-blockchain/other/starkex.mdx
@@ -90,7 +90,7 @@ const account = starkwareCrypto.ec.keyFromPublic(keyPair.getPublic(true, 'hex'),
 const startKey = account.pub.getX().toString('hex')
 ```
 
-## Mint Request
+## Mint request
 
 ```tsx
 import StarkExAPI from '@starkware-industries/starkex-js/dist/browser'
@@ -126,7 +126,7 @@ const request = {
 const response = await starkExAPI.gateway.mint(request)
 ```
 
-## Deposit Request
+## Deposit request
 
 ```tsx
 import StarkExAPI from '@starkware-industries/starkex-js/dist/browser'
@@ -162,7 +162,7 @@ const request = {
 const response = await starkExAPI.gateway.deposit(request)
 ```
 
-## Withdraw Request
+## Withdraw request
 
 ```tsx
 import StarkExAPI from '@starkware-industries/starkex-js/dist/browser'
diff --git a/embedded-wallets/connect-blockchain/other/starknet.mdx b/embedded-wallets/connect-blockchain/other/starknet.mdx
index 51904d20923..7f8ede8b80f 100644
--- a/embedded-wallets/connect-blockchain/other/starknet.mdx
+++ b/embedded-wallets/connect-blockchain/other/starknet.mdx
@@ -93,7 +93,7 @@ const account = starkwareCrypto.ec.keyFromPublic(keyPair.getPublic(true, 'hex'),
 const startKey = account.pub.getX().toString('hex')
 ```
 
-## Deploy Account
+## Deploy an account
 
 ```tsx
 import { AddTransactionResponse, defaultProvider } from 'starknet'
diff --git a/embedded-wallets/connect-blockchain/other/tezos.mdx b/embedded-wallets/connect-blockchain/other/tezos.mdx
index 022e2691da7..23c2d2086b9 100644
--- a/embedded-wallets/connect-blockchain/other/tezos.mdx
+++ b/embedded-wallets/connect-blockchain/other/tezos.mdx
@@ -144,7 +144,7 @@ const op = await tezos.wallet
 const txRes = await op.confirmation()
 ```
 
-## Sign Message
+## Sign a message
 
 ```tsx
 import * as tezosCrypto from '@tezos-core-tools/crypto-utils'
diff --git a/embedded-wallets/connect-blockchain/solana/android.mdx b/embedded-wallets/connect-blockchain/solana/android.mdx
index 9bd296b40dd..d6c626f689f 100644
--- a/embedded-wallets/connect-blockchain/solana/android.mdx
+++ b/embedded-wallets/connect-blockchain/solana/android.mdx
@@ -106,7 +106,7 @@ dependencies {
 
 To Initialize the `Connection` we require rpc url. The `Connection` object will provide a gateway & protocol to interact with Solana cluster while sending requests and receving response.The `sol4k` SDK also provides `RpcUrl` constant for all the supported clusters. For this example, we are using `RpcUrl.DEVNET` for Devnet-beta. To interact with Testnet or Mainnet, you can simply change the `RpcUrl`.
 
-### Initializing Solana SDK
+### Initializing the Solana SDK
 
 In the below code block, we'll create the `Connection` instance using the Devnet-beta rpc.
 
@@ -117,7 +117,7 @@ import org.sol4k.RpcUrl
 val connection = Connection(RpcUrl.DEVNET)
 ```
 
-### Initializing Web3Auth SDK
+### Initializing the Web3Auth SDK
 
 In the below code block, we'll initialize the Web3Auth SDK and check whether the user has any Web3Auth session persisted or not. If the user is already authenticated, you can route them directly to `HomeScreen`, otherwise you can route them to `LoginScreen` for authentication purpose. For checking, if user is already authenticated, we can check whether private key is empty or not.
 
@@ -160,7 +160,7 @@ val solanaKeyPair = Keypair.fromSecretKey(ed25519PrivateKey.hexToByteArray())
 val userAccount = solanaKeyPair.publicKey.toBase58()
 ```
 
-## Get User Balance
+## Get user balance
 
 Once we have retrieved userAccount, we can use it to fetch user balance. We'll use `getBalance` method from `Connection` instance to interact with Solana cluster and fetch user balance. The response of `getBalance` is BigInteger, we will need to divide it by by 10^9, because Solana's token decimals is 9.
 
@@ -180,7 +180,7 @@ try {
 }
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 Let's now go through how can we sign the transaction. In the below codeblock, we'll create a new function `prepareSignedTransaction` which can be used to retrieve the Base58 signature as well as broadcast transaction to the cluster. We'll use `TransferInstruction` to create the transaction to self transfer 0.01 Sol and sign it.
 
diff --git a/embedded-wallets/connect-blockchain/solana/flutter.mdx b/embedded-wallets/connect-blockchain/solana/flutter.mdx
index 859ffb7073d..58bac919f7e 100644
--- a/embedded-wallets/connect-blockchain/solana/flutter.mdx
+++ b/embedded-wallets/connect-blockchain/solana/flutter.mdx
@@ -82,7 +82,7 @@ flutter pub add solana get_it hex
 
 To Initialize the `SolanaClient` we require `rpcUrl` and `websocketUrl`. The `rpcUrl` will provide a gateway & protocol to interact with Solana cluster while sending requests and receving response. For this example, we are using `rpcUrl` & `websocketUrl` for Devnet-beta. To interact with Testnet or Mainnet, you can simply change the `rpcUrl` and `websocketUrl`.
 
-### Initializing Solana SDK
+### Initializing the Solana SDK
 
 In the below code block, we'll initialize the `SolanaClient` using the Devnet-beta rpc and websocket urls. We'll also register the instance in GetIt for it to be accessed anywhere using service locator.
 
@@ -200,7 +200,7 @@ class _MainAppState extends State<MainApp> {
 
 We can use `getEd25519PrivKey` method in Web3Auth to retrive the priavte key for the Solana ecosystem. In the below code block, we'll use the Ed25519 private key to retive user's public address, and solana balance. We'll use `SolanaProvider` class to interact with Solana cluster and fetch user balance.
 
-### Setup Solana Provider
+### Set up Solana provider
 
 In the below code block, we'll create Solana provider to interact and perform solana operations.
 
@@ -337,7 +337,7 @@ class _HomeScreenState extends State<HomeScreen> {
 }
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 Let's now go through how can we sign the transaction. In the below code block, we'll add a new method inside `SolanaProvider` we setup earlier to help us sign a transfer transaction. After successful implementation, we can use the method in `HomeScreen`.
 
diff --git a/embedded-wallets/connect-blockchain/solana/ios.mdx b/embedded-wallets/connect-blockchain/solana/ios.mdx
index 3df4a7c5246..3afe33916e4 100644
--- a/embedded-wallets/connect-blockchain/solana/ios.mdx
+++ b/embedded-wallets/connect-blockchain/solana/ios.mdx
@@ -118,7 +118,7 @@ pod install
 
 To Initialize the `JSONRPCAPIClient` we require rpc url. The `JSONRPCAPIClient` instance will provide a gateway & protocol to interact with Solana cluster while sending requests and receving response. For this example, we are using rpc url for Devnet-beta. To interact with Testnet or Mainnet, you can simply change the rpc url.
 
-### Initializing Solana SDK
+### Initializing the Solana SDK
 
 In the below code block, we'll create the `JSONRPCAPIClient` instance using the Devnet-beta rpc.
 
@@ -134,7 +134,7 @@ let endpoint = APIEndPoint(
 let solanaJSONRPCClient = JSONRPCAPIClient(endpoint: endpoint)
 ```
 
-### Initializing Web3Auth SDK
+### Initializing the Web3Auth SDK
 
 In the below code block, we'll initialize the Web3Auth SDK and check whether the user has any Web3Auth session persisted or not. If the user is already authenticated, you can route them directly to home view, otherwise you can route them to login view for authentication purpose. For checking, if user is already authenticated, we can check whether `Web3Auth.state` is `nil` or not.
 
@@ -191,7 +191,7 @@ let balanceResponse = try await solanaJSONRPCClient.getBalance(
 let userBalance = return balanceResponse.convertToBalance(decimals: 9)
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 Let's now go through how can we sign the transaction. In the below codeblock, we'll create a new function `perpareTransaction` which can be used to retrive the Base58 signature as well as broadcast transaction to the cluster. We'll use `BlockchainClient.prepareSendingNativeSOL` to create the transaction to self transfer 0.01 Sol and sign it. You can also checkout `prepareSendingSPLTokens`, and `prepareTransaction` for other types of transaction.
 
diff --git a/embedded-wallets/connect-blockchain/solana/javascript.mdx b/embedded-wallets/connect-blockchain/solana/javascript.mdx
index 7095f596f0c..dd8f6ba04a4 100644
--- a/embedded-wallets/connect-blockchain/solana/javascript.mdx
+++ b/embedded-wallets/connect-blockchain/solana/javascript.mdx
@@ -135,7 +135,7 @@ const connection = new Connection(connectionConfig.rpcTarget)
 const balance = await connection.getBalance(new PublicKey(accounts[0]))
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 ```tsx
 import {
@@ -172,7 +172,7 @@ const signedTx = await solanaWallet.signTransaction(transaction)
 console.log(signedTx.signature)
 ```
 
-## Sign All Transactions
+## Sign all transactions
 
 ```tsx
 import {
@@ -260,7 +260,7 @@ const { signature } = await solanaWallet.signAndSendTransaction(transaction)
 console.log(signature)
 ```
 
-## Sign Message
+## Sign a message
 
 ```tsx
 import {
@@ -277,7 +277,7 @@ const result = await solanaWallet.signMessage(msg)
 console.log(result.toString())
 ```
 
-## Fetch User's Private Key
+## Fetch user's private key
 
 `solana_privateKey` is used to fetch the private key of the logged in user. It is only available for `in-app` adapters like `auth`.
 
diff --git a/embedded-wallets/connect-blockchain/solana/node.mdx b/embedded-wallets/connect-blockchain/solana/node.mdx
index a27eb21ed59..66678756d29 100644
--- a/embedded-wallets/connect-blockchain/solana/node.mdx
+++ b/embedded-wallets/connect-blockchain/solana/node.mdx
@@ -68,7 +68,7 @@ To interact with the Solana blockchain in Node.js, you need to install the requi
 npm install --save @solana/web3.js @solana/signers
 ```
 
-## Initializing Web3Auth Node SDK
+## Initializing the Web3Auth Node SDK
 
 The Web3Auth Node SDK provides a `TransactionSigner` for Solana when using the `SOLANA` chain namespace. Here's how to set it up:
 
diff --git a/embedded-wallets/connect-blockchain/solana/react-native.mdx b/embedded-wallets/connect-blockchain/solana/react-native.mdx
index 753887c6c81..85311994f3f 100644
--- a/embedded-wallets/connect-blockchain/solana/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/solana/react-native.mdx
@@ -141,7 +141,7 @@ const balanceInSOL = balance / LAMPORTS_PER_SOL
 console.log(`Balance: ${balanceInSOL} SOL`)
 ```
 
-## Sign Transaction
+## Sign a transaction
 
 ```tsx
 import {
@@ -222,7 +222,7 @@ const { signature } = await solanaWallet.signAndSendTransaction(transaction)
 console.log('Transaction signature', signature)
 ```
 
-## Sign Message
+## Sign a message
 
 ```tsx
 const solanaWallet = new SolanaWallet(web3auth.provider)
diff --git a/embedded-wallets/connect-blockchain/solana/react.mdx b/embedded-wallets/connect-blockchain/solana/react.mdx
index 8c3beef626f..0fbb62582d1 100644
--- a/embedded-wallets/connect-blockchain/solana/react.mdx
+++ b/embedded-wallets/connect-blockchain/solana/react.mdx
@@ -76,7 +76,7 @@ For advanced Solana features, you should use [`@solana/web3.js`](https://solana-
 npm install @solana/web3.js
 ```
 
-## Solana Hooks
+## Solana hooks
 
 | Hook Name                   | Description                                  |
 | --------------------------- | -------------------------------------------- |
diff --git a/embedded-wallets/connect-blockchain/solana/unity.mdx b/embedded-wallets/connect-blockchain/solana/unity.mdx
index 33bb31c50f2..b946083ca52 100644
--- a/embedded-wallets/connect-blockchain/solana/unity.mdx
+++ b/embedded-wallets/connect-blockchain/solana/unity.mdx
@@ -64,7 +64,7 @@ While using the Web3Auth Unity SDK, you can retrieve the Ed25519 private key wit
 
 For Unity Solana integration, we recommend using the **Solana Unity SDK by Magicblock**, which is available on the Unity Asset Store. This SDK provides comprehensive Solana functionality including JSON RPC API coverage, wallet management, transaction handling, and NFT operations.
 
-### Installing Solana Unity SDK
+### Installing the Solana Unity SDK
 
 1. Open Unity Asset Store in your Unity Editor
 2. Search for "Solana Unity SDK" by Magicblock
diff --git a/embedded-wallets/connect-blockchain/solana/vue.mdx b/embedded-wallets/connect-blockchain/solana/vue.mdx
index 864ce19d9bf..52305a29dab 100644
--- a/embedded-wallets/connect-blockchain/solana/vue.mdx
+++ b/embedded-wallets/connect-blockchain/solana/vue.mdx
@@ -76,7 +76,7 @@ For advanced Solana features, you should use [`@solana/web3.js`](https://solana-
 npm install @solana/web3.js
 ```
 
-## Solana Composables
+## Solana composables
 
 | Composable Name             | Description                                  |
 | --------------------------- | -------------------------------------------- |
diff --git a/embedded-wallets/dashboard/advanced/custom-chains.mdx b/embedded-wallets/dashboard/advanced/custom-chains.mdx
index e982fde1686..fd163dd43cd 100644
--- a/embedded-wallets/dashboard/advanced/custom-chains.mdx
+++ b/embedded-wallets/dashboard/advanced/custom-chains.mdx
@@ -1,6 +1,6 @@
 ---
-title: Add Custom Chains to the dashboard
-sidebar_label: Add Custom Chains to the dashboard
+title: Add Custom Chains to the Dashboard
+sidebar_label: Add Custom Chains to the Dashboard
 image: 'img/metamaskog.jpg'
 description: 'Add Custom Chains | Embedded Wallets'
 ---
diff --git a/embedded-wallets/dashboard/advanced/session-management.mdx b/embedded-wallets/dashboard/advanced/session-management.mdx
index 88138697e26..930e0830d50 100644
--- a/embedded-wallets/dashboard/advanced/session-management.mdx
+++ b/embedded-wallets/dashboard/advanced/session-management.mdx
@@ -189,13 +189,13 @@ Rationale: Platform-level access with game-specific security
 
 Web3Auth sessions can be renewed through various mechanisms:
 
-#### Automatic Renewal
+#### Automatic renewal
 
 - Sessions automatically extend on user activity
 - Background refresh maintains active sessions
 - Seamless experience without user intervention
 
-#### Manual Renewal
+#### Manual renewal
 
 - Explicit user action required for session extension
 - Greater control over session lifecycle
@@ -205,14 +205,14 @@ Web3Auth sessions can be renewed through various mechanisms:
 
 Sessions may be terminated automatically, or manually. 
 
-#### Automatic Termination Events
+#### Automatic termination events
 
 - Session duration expiry
 - Extended inactivity periods
 - Security-triggered logout
 - Device/browser changes
 
-#### Manual Termination
+#### Manual termination
 
 - User-initiated logout
 - Administrative session termination

From 963f818b8d45b452a7029dc945edffc89aba88c2 Mon Sep 17 00:00:00 2001
From: m4sterbunny <harrie.bickle-ext@consensys.net>
Date: Wed, 3 Dec 2025 18:38:36 +0000
Subject: [PATCH 3/3] review over pr state

---
 .../authentication/basic-logins/sms-otp.mdx   |  2 +-
 .../custom-connections/auth0.mdx              |  2 +-
 .../custom-connections/aws-cognito.mdx        | 10 ++--
 .../custom-connections/custom-jwt.mdx         |  6 +--
 .../custom-connections/firebase.mdx           | 12 ++---
 .../authentication/social-logins/discord.mdx  |  8 +--
 .../authentication/social-logins/facebook.mdx |  6 +--
 .../authentication/social-logins/google.mdx   |  6 +--
 .../authentication/social-logins/oauth.mdx    |  2 +-
 .../authentication/social-logins/twitch.mdx   |  6 +--
 .../evm/aleph-zero/node.mdx                   |  2 +-
 .../evm/aleph-zero/react-native.mdx           |  2 +-
 .../connect-blockchain/evm/ancient8/node.mdx  |  2 +-
 .../evm/ancient8/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/arbitrum/node.mdx  |  2 +-
 .../evm/arbitrum/react-native.mdx             |  2 +-
 .../evm/astar-zkevm/node.mdx                  |  2 +-
 .../evm/astar-zkevm/react-native.mdx          |  2 +-
 .../evm/astar-zkyoto/node.mdx                 |  2 +-
 .../evm/astar-zkyoto/react-native.mdx         |  2 +-
 .../connect-blockchain/evm/avalanche/node.mdx |  2 +-
 .../evm/avalanche/react-native.mdx            |  2 +-
 .../connect-blockchain/evm/base/node.mdx      |  2 +-
 .../evm/base/react-native.mdx                 |  2 +-
 .../connect-blockchain/evm/bitkub/node.mdx    |  2 +-
 .../evm/bitkub/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/bnb/node.mdx       |  2 +-
 .../evm/bnb/react-native.mdx                  |  2 +-
 .../connect-blockchain/evm/celo/node.mdx      |  2 +-
 .../evm/celo/react-native.mdx                 |  2 +-
 .../connect-blockchain/evm/chiliz/node.mdx    |  2 +-
 .../evm/chiliz/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/cronos/node.mdx    |  2 +-
 .../evm/cronos/react-native.mdx               |  2 +-
 .../evm/ethereum/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/fhenix/node.mdx    |  2 +-
 .../evm/fhenix/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/flare/node.mdx     |  2 +-
 .../evm/flare/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/flow/node.mdx      |  2 +-
 .../evm/flow/react-native.mdx                 |  2 +-
 .../connect-blockchain/evm/harmony/node.mdx   |  2 +-
 .../evm/harmony/react-native.mdx              |  2 +-
 .../connect-blockchain/evm/hedera/node.mdx    |  2 +-
 .../evm/hedera/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/kinto/node.mdx     |  2 +-
 .../evm/kinto/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/klaytn/node.mdx    |  2 +-
 .../evm/klaytn/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/linea/node.mdx     |  2 +-
 .../evm/linea/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/manta/node.mdx     |  2 +-
 .../evm/manta/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/metis/node.mdx     |  2 +-
 .../evm/metis/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/mint/node.mdx      |  2 +-
 .../evm/mint/react-native.mdx                 |  2 +-
 .../connect-blockchain/evm/moonbeam/node.mdx  |  2 +-
 .../evm/moonbeam/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/moonriver/node.mdx |  2 +-
 .../evm/moonriver/react-native.mdx            |  2 +-
 .../connect-blockchain/evm/morph/node.mdx     |  2 +-
 .../evm/morph/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/neon/node.mdx      |  2 +-
 .../evm/neon/react-native.mdx                 |  2 +-
 .../connect-blockchain/evm/nibiru/node.mdx    |  2 +-
 .../evm/nibiru/react-native.mdx               |  2 +-
 .../connect-blockchain/evm/opbnb/node.mdx     |  2 +-
 .../evm/opbnb/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/optimism/node.mdx  |  2 +-
 .../evm/optimism/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/polygon/node.mdx   |  2 +-
 .../evm/polygon/react-native.mdx              |  2 +-
 .../connect-blockchain/evm/rootstock/node.mdx |  2 +-
 .../evm/rootstock/react-native.mdx            |  2 +-
 .../connect-blockchain/evm/saakuru/node.mdx   |  2 +-
 .../evm/saakuru/react-native.mdx              |  2 +-
 .../connect-blockchain/evm/shardeum/node.mdx  |  2 +-
 .../evm/shardeum/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/skale/node.mdx     |  2 +-
 .../evm/skale/react-native.mdx                |  2 +-
 .../connect-blockchain/evm/soneium/node.mdx   |  2 +-
 .../evm/soneium/react-native.mdx              |  2 +-
 .../connect-blockchain/evm/songbird/node.mdx  |  2 +-
 .../evm/songbird/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/unichain/node.mdx  |  2 +-
 .../evm/unichain/react-native.mdx             |  2 +-
 .../connect-blockchain/evm/xdc/node.mdx       |  2 +-
 .../evm/xdc/react-native.mdx                  |  2 +-
 .../connect-blockchain/evm/zetachain/node.mdx |  2 +-
 .../evm/zetachain/react-native.mdx            |  2 +-
 .../connect-blockchain/evm/zilliqa/node.mdx   |  2 +-
 .../evm/zilliqa/react-native.mdx              |  2 +-
 .../connect-blockchain/evm/zircuit/node.mdx   |  2 +-
 .../evm/zircuit/react-native.mdx              |  2 +-
 .../dashboard/advanced/key-export.mdx         | 18 +++----
 .../dashboard/advanced/session-management.mdx |  8 +--
 embedded-wallets/dashboard/analytics.mdx      |  2 +-
 embedded-wallets/dashboard/authentication.mdx |  2 +-
 .../dashboard/chains-and-networks.mdx         |  4 +-
 embedded-wallets/dashboard/customization.mdx  | 22 ++++----
 .../dashboard/project-settings.mdx            | 51 +++++++++----------
 .../dashboard/wallet-services.mdx             |  2 +-
 embedded-wallets/dashboard/whitelist.mdx      |  2 +-
 embedded-wallets/sdk/js/events.mdx            |  2 +-
 .../troubleshooting/jwt-errors.mdx            |  2 +-
 106 files changed, 172 insertions(+), 173 deletions(-)

diff --git a/embedded-wallets/authentication/basic-logins/sms-otp.mdx b/embedded-wallets/authentication/basic-logins/sms-otp.mdx
index 9cda2c45fe9..29b63f73a09 100644
--- a/embedded-wallets/authentication/basic-logins/sms-otp.mdx
+++ b/embedded-wallets/authentication/basic-logins/sms-otp.mdx
@@ -48,7 +48,7 @@ For enhanced control and branding, developers are encouraged to configure a cust
 
 1. Visit the [dashboard](https://dashboard.web3auth.io).
 2. Go to the **Social Connections** section.
-3. Click the **Settings** icon next to the toggle for `SMS OTP`.
+3. Click the **Settings** icon next to the toggle for **SMS OTP**.
 4. Enter your custom `Auth Connection ID`.
 5. Click **Add Connection** to complete the setup.
 
diff --git a/embedded-wallets/authentication/custom-connections/auth0.mdx b/embedded-wallets/authentication/custom-connections/auth0.mdx
index 1c84b17181a..e94acef35a4 100644
--- a/embedded-wallets/authentication/custom-connections/auth0.mdx
+++ b/embedded-wallets/authentication/custom-connections/auth0.mdx
@@ -140,7 +140,7 @@ In your activity, create a `Web3Auth` instance with your Web3Auth project's conf
 web3Auth = Web3Auth(
   Web3AuthOptions(
     context = this,
-    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Web3Auth Dashboard
+    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Embedded Wallets dashboard
     network = Network.SAPPHIRE_MAINNET
     redirectUrl = Uri.parse("{YOUR_APP_PACKAGE_NAME}://auth"), // your app's redirect URL
     // focus-start
diff --git a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
index e1b41248829..428b0c3e464 100644
--- a/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
+++ b/embedded-wallets/authentication/custom-connections/aws-cognito.mdx
@@ -8,7 +8,7 @@ import CustomConnectionOptions from '@site/static/img/embedded-wallets/w3a-dashb
 import AWSConnection from '@site/static/img/embedded-wallets/w3a-dashboard/aws-cognito-connection.png'
 import ImplicitLoginCognito from '../../sdk/react/advanced/_custom-authentication-snippets/_implicit_login_aws_cognito.mdx'
 
-[AWS Cognito](https://aws.amazon.com/cognito/) is a scalable authentication service provided by Amazon Web Services that enables developers to securely manage user sign-up, sign-in, and access control. Web3Auth supports AWS Cognito as a service provider, allowing seamless integration between AWS Cognito’s authentication capabilities and Web3Auth’s decentralized key management infrastructure.
+[AWS Cognito](https://aws.amazon.com/cognito/) is a scalable authentication service provided by Amazon Web Services that enables developers to securely manage user sign-up, sign-in, and access control. Embedded Wallets supports AWS Cognito as a service provider, allowing seamless integration between AWS Cognito’s authentication capabilities and Embedded Wallets’s decentralized key management infrastructure.
 
 AWS Cognito [supports a wide set of social logins](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-social-idp.html).
 
@@ -47,13 +47,13 @@ Follow these steps to create a AWS Cognito connection:
 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. Toggle the Case Sensitivity of `User Identifier`. (Optional)
+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 `https://cognito-idp.{REGION}.amazonaws.com/{USER_POOL_ID}` as a value.
    1. Next, type aud as a field and `APP_CLIENT_ID` as a value.
-1. Finally, click on the **Add Connection** button.
+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.
 
diff --git a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
index f7ea3e98ac3..ce8f890ed5e 100644
--- a/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
+++ b/embedded-wallets/authentication/custom-connections/custom-jwt.mdx
@@ -47,11 +47,11 @@ Follow these steps to create a custom JWT connection:
 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. Toggle the Case Sensitivity of `User Identifier`. (Optional)
+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.
-   1. Next, type aud as a field and `your-audience` as a value.
-1. Finally, click on the **Add Connection** button.
+   1. Type aud as a field and `your-audience` as a value.
+1. Click the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/custom-connections/firebase.mdx b/embedded-wallets/authentication/custom-connections/firebase.mdx
index c75ac0b4eea..1c3d2089fad 100644
--- a/embedded-wallets/authentication/custom-connections/firebase.mdx
+++ b/embedded-wallets/authentication/custom-connections/firebase.mdx
@@ -10,7 +10,7 @@ import CustomConnectionOptions from '@site/static/img/embedded-wallets/w3a-dashb
 import FirebaseConnection from '@site/static/img/embedded-wallets/w3a-dashboard/firebase-connection.png'
 import JwtLoginFirebase from '../../sdk/react/advanced/_custom-authentication-snippets/_jwt_login_firebase.mdx'
 
-[Firebase](https://firebase.google.com/) is a popular backend platform that enables developers to seamlessly integrate authentication, databases, and other services into their applications. Web3Auth supports Firebase as an authentication provider, allowing developers to leverage Firebase Authentication within the Web3Auth framework for secure user login and key management.
+[Firebase](https://firebase.google.com/) is a popular backend platform that enables developers to seamlessly integrate authentication, databases, and other services into their applications. Embedded Wallets supports Firebase as an authentication provider, allowing developers to leverage Firebase Authentication within the Web3Auth framework for secure user login and key management.
 
 Firebase [supports a wide set of social logins](https://firebase.google.com/docs/auth).
 
@@ -93,13 +93,13 @@ Follow these steps to create a Firebase connection:
 1. Click on the **Settings** icon near the Firebase connection.
 1. Enter the `Firebase Connection ID`.
 1. Paste `https://www.googleapis.com/service_accounts/v1/jwk/securetoken@system.gserviceaccount.com` 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. Toggle the Case Sensitivity of `User Identifier`. (Optional)
+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 `https://securetoken.google.com/FIREBASE-PROJECT-ID` as a value.
    1. Next, type aud as a field and `FIREBASE-PROJECT-ID` as a value.
-1. Finally, click on the **Add Connection** button.
+1. Click on the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -133,7 +133,7 @@ In your activity, create a `Web3Auth` instance with your Web3Auth project's conf
 web3Auth = Web3Auth(
   Web3AuthOptions(
     context = this,
-    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Web3Auth Dashboard
+    clientId = getString(R.string.web3auth_project_id), // pass over your Web3Auth Client ID from Embedded Wallets dashboard
     network = Network.SAPPHIRE_MAINNET
     redirectUrl = Uri.parse("{YOUR_APP_PACKAGE_NAME}://auth"), // your app's redirect URL
     // focus-start
diff --git a/embedded-wallets/authentication/social-logins/discord.mdx b/embedded-wallets/authentication/social-logins/discord.mdx
index 1d001a2eeef..e5b30ca91df 100644
--- a/embedded-wallets/authentication/social-logins/discord.mdx
+++ b/embedded-wallets/authentication/social-logins/discord.mdx
@@ -22,7 +22,7 @@ To integrate Discord with Web3Auth, developers must first create a Discord App v
 
 3. Don't forget to save your changes!
 
-4. Next, obtain the **Client ID** from here. We will use this in our Embedded Wallets Dashboard.
+4. Copy the **Client ID** from here. We will use this in the Embedded Wallets Dashboard.
 
    ![Discord OAuth2.0 App Client ID and Secret](/img/embedded-wallets/authentication/discord/discord-clientid-secret.png)
 
@@ -30,7 +30,7 @@ To integrate Discord with Web3Auth, developers must first create a Discord App v
 
 :::success Enable on dashboard
 
-To use this feature, please enable `Discord` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
+To use this feature, enable `Discord` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Discord login.
 
@@ -52,10 +52,10 @@ Follow these steps to create a Discord connection:
 
 1. Visit the [dashboard](https://dashboard.web3auth.io).
 1. Go to the **Social Connections** section.
-1. Click on the **Settings** icon near the Discord connection.
+1. Click the **Settings** icon near the Discord connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Discord Client ID`.
-1. Finally, click on the **Add Connection** button.
+1. Click the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/social-logins/facebook.mdx b/embedded-wallets/authentication/social-logins/facebook.mdx
index 2602d42dea2..4919fab7df4 100644
--- a/embedded-wallets/authentication/social-logins/facebook.mdx
+++ b/embedded-wallets/authentication/social-logins/facebook.mdx
@@ -34,7 +34,7 @@ To integrate Facebook with Web3Auth, developers must first create a Facebook App
 
 :::success Enable on Dashboard
 
-To use this feature, please enable `Facebook` from the Social Connections section in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
+To use this feature, enable `Facebook` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Facebook login.
 
@@ -56,11 +56,11 @@ Follow these steps to create a Facebook connection:
 
 1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
 1. Go to the **Social Connections** section.
-1. Click on the **Settings** icon near the Facebook connection.
+1. Click the **Settings** icon near the Facebook connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Facebook App ID`.
 1. Enter the `Facebook App Secret`.
-1. Finally, click on the **Add Connection** button.
+1. Click the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/social-logins/google.mdx b/embedded-wallets/authentication/social-logins/google.mdx
index e0e67bfd45d..dfab17e1757 100644
--- a/embedded-wallets/authentication/social-logins/google.mdx
+++ b/embedded-wallets/authentication/social-logins/google.mdx
@@ -30,7 +30,7 @@ To integrate Google Sign-In with Embedded Wallets, developers must first configu
 
 :::success Enable on Dashboard
 
-To use this feature, please enable **Google** from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
+To use this feature, enable **Google** from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Google login.
 
@@ -52,10 +52,10 @@ Follow these steps to create a Google connection:
 
 1. Visit the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
 1. Go to the **Social Connections** section.
-1. Click on the **Settings** icon near the Google connection.
+1. Click the **Settings** icon near the Google connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Google Client ID`.
-1. Finally, click on the **Add Connection** button.
+1. Click the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/authentication/social-logins/oauth.mdx b/embedded-wallets/authentication/social-logins/oauth.mdx
index f29a4fb2c6b..6fae9abaf12 100644
--- a/embedded-wallets/authentication/social-logins/oauth.mdx
+++ b/embedded-wallets/authentication/social-logins/oauth.mdx
@@ -10,7 +10,7 @@ import OAuthToggle from '@site/static/img/embedded-wallets/w3a-dashboard/authent
 
 :::success Enable on dashboard
 
-To use this feature, please enable X(Twitter), Farcaster, Apple, GitHub, Reddit, Line, Kakao, LinkedIn, or WeChat from the **Social Connections** section in the [dashboard](https://dashboard.web3auth.io).
+To use this feature, enable X(Twitter), Farcaster, Apple, GitHub, Reddit, Line, Kakao, LinkedIn, or WeChat from the **Social Connections** section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for different social login providers.
 
diff --git a/embedded-wallets/authentication/social-logins/twitch.mdx b/embedded-wallets/authentication/social-logins/twitch.mdx
index 1136e9f48cc..460680972a7 100644
--- a/embedded-wallets/authentication/social-logins/twitch.mdx
+++ b/embedded-wallets/authentication/social-logins/twitch.mdx
@@ -33,7 +33,7 @@ Twitch supports social login, allowing users to [sign in using their Twitch cred
 
 :::success Enable on dashboard
 
-To use this feature, please enable `Twitch` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
+To use this feature, enable `Twitch` from the Social Connections section in the [dashboard](https://dashboard.web3auth.io).
 
 > By default, Web3Auth uses its own pre-configured credentials for Twitch login.
 
@@ -55,10 +55,10 @@ Follow these steps to create a Twitch connection:
 
 1. Visit the [dashboard](https://dashboard.web3auth.io).
 1. Go to the **Social Connections** section.
-1. Click on the **Settings** icon near the Twitch connection.
+1. Click the **Settings** icon near the Twitch connection.
 1. Enter the `Auth Connection ID`.
 1. Enter the `Twitch Client ID`.
-1. Finally, click on the **Add Connection** button.
+1. Click the **Add Connection** button to save the settings.
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
diff --git a/embedded-wallets/connect-blockchain/evm/aleph-zero/node.mdx b/embedded-wallets/connect-blockchain/evm/aleph-zero/node.mdx
index 4feffa1c405..c1414b232ef 100644
--- a/embedded-wallets/connect-blockchain/evm/aleph-zero/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/aleph-zero/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Aleph Zero Blockchain in Node
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAlephZero from '../../_general-connect-blockchain/_aleph-zero.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Aleph Zero](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Aleph Zero](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Aleph Zero
 
diff --git a/embedded-wallets/connect-blockchain/evm/aleph-zero/react-native.mdx b/embedded-wallets/connect-blockchain/evm/aleph-zero/react-native.mdx
index ccfe31fc571..b9d0c256c79 100644
--- a/embedded-wallets/connect-blockchain/evm/aleph-zero/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/aleph-zero/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Aleph Zero Blockchain in React
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAlephZero from '../../_general-connect-blockchain/_aleph-zero.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Aleph Zero](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Aleph Zero](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Aleph Zero
 
diff --git a/embedded-wallets/connect-blockchain/evm/ancient8/node.mdx b/embedded-wallets/connect-blockchain/evm/ancient8/node.mdx
index 9c8591e08a9..538411ba1bf 100644
--- a/embedded-wallets/connect-blockchain/evm/ancient8/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/ancient8/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Ancient8 Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAncient8 from '../../_general-connect-blockchain/_ancient8.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ancient8](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ancient8](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Ancient8
 
diff --git a/embedded-wallets/connect-blockchain/evm/ancient8/react-native.mdx b/embedded-wallets/connect-blockchain/evm/ancient8/react-native.mdx
index be311aa246b..368594556a2 100644
--- a/embedded-wallets/connect-blockchain/evm/ancient8/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/ancient8/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Ancient8 Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAncient8 from '../../_general-connect-blockchain/_ancient8.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ancient8](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ancient8](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Ancient8
 
diff --git a/embedded-wallets/connect-blockchain/evm/arbitrum/node.mdx b/embedded-wallets/connect-blockchain/evm/arbitrum/node.mdx
index e05a76e6455..d16bf601928 100644
--- a/embedded-wallets/connect-blockchain/evm/arbitrum/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/arbitrum/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Arbitrum Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsArbitrum from '../../_general-connect-blockchain/_arbitrum.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Arbitrum](https://arbitrum.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Arbitrum](https://arbitrum.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Arbitrum
 
diff --git a/embedded-wallets/connect-blockchain/evm/arbitrum/react-native.mdx b/embedded-wallets/connect-blockchain/evm/arbitrum/react-native.mdx
index 4f6b6cb6cd2..51157d5ab94 100644
--- a/embedded-wallets/connect-blockchain/evm/arbitrum/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/arbitrum/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Arbitrum Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsArbitrum from '../../_general-connect-blockchain/_arbitrum.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Arbitrum](https://arbitrum.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Arbitrum](https://arbitrum.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Arbitrum
 
diff --git a/embedded-wallets/connect-blockchain/evm/astar-zkevm/node.mdx b/embedded-wallets/connect-blockchain/evm/astar-zkevm/node.mdx
index fcf193c1ea6..b6a58c94fe3 100644
--- a/embedded-wallets/connect-blockchain/evm/astar-zkevm/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/astar-zkevm/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Astar zkEVM Blockchain in Node
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAstarZkevm from '../../_general-connect-blockchain/_astar-zkevm.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar zkEVM](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar zkEVM](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Astar zkEVM
 
diff --git a/embedded-wallets/connect-blockchain/evm/astar-zkevm/react-native.mdx b/embedded-wallets/connect-blockchain/evm/astar-zkevm/react-native.mdx
index bff13d3f7cb..98ce1397fe8 100644
--- a/embedded-wallets/connect-blockchain/evm/astar-zkevm/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/astar-zkevm/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Astar zkEVM Blockchain in Reac
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAstarZkevm from '../../_general-connect-blockchain/_astar-zkevm.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar zkEVM](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar zkEVM](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly.
 
 ## Chain details for Astar zkEVM
 
diff --git a/embedded-wallets/connect-blockchain/evm/astar-zkyoto/node.mdx b/embedded-wallets/connect-blockchain/evm/astar-zkyoto/node.mdx
index 234b98f529e..e2079ab8c0a 100644
--- a/embedded-wallets/connect-blockchain/evm/astar-zkyoto/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/astar-zkyoto/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Astar Zkyoto Blockchain in Nod
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAstarZkyoto from '../../_general-connect-blockchain/_astar-zkyoto.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar Zkyoto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar Zkyoto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Astar Zkyoto
 
diff --git a/embedded-wallets/connect-blockchain/evm/astar-zkyoto/react-native.mdx b/embedded-wallets/connect-blockchain/evm/astar-zkyoto/react-native.mdx
index 1828b621246..b68986c1744 100644
--- a/embedded-wallets/connect-blockchain/evm/astar-zkyoto/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/astar-zkyoto/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Astar Zkyoto Blockchain in Rea
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAstarZkyoto from '../../_general-connect-blockchain/_astar-zkyoto.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar Zkyoto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Astar Zkyoto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Astar Zkyoto
 
diff --git a/embedded-wallets/connect-blockchain/evm/avalanche/node.mdx b/embedded-wallets/connect-blockchain/evm/avalanche/node.mdx
index b2f5fe10528..1c0dc290319 100644
--- a/embedded-wallets/connect-blockchain/evm/avalanche/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/avalanche/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Avalanche Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAvalanche from '../../_general-connect-blockchain/_avalanche.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Avalanche](https://www.avax.network/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Avalanche](https://www.avax.network/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Avalanche
 
diff --git a/embedded-wallets/connect-blockchain/evm/avalanche/react-native.mdx b/embedded-wallets/connect-blockchain/evm/avalanche/react-native.mdx
index 739c19e331a..510661f9a67 100644
--- a/embedded-wallets/connect-blockchain/evm/avalanche/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/avalanche/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Avalanche Blockchain in React
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsAvalanche from '../../_general-connect-blockchain/_avalanche.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Avalanche](https://www.avax.network/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Avalanche](https://www.avax.network/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Avalanche
 
diff --git a/embedded-wallets/connect-blockchain/evm/base/node.mdx b/embedded-wallets/connect-blockchain/evm/base/node.mdx
index 7da7acbc95e..eb5fc4b6608 100644
--- a/embedded-wallets/connect-blockchain/evm/base/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/base/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Base Blockchain in Node | Embe
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBase from '../../_general-connect-blockchain/_base.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Base](https://base.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Base](https://base.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Base
 
diff --git a/embedded-wallets/connect-blockchain/evm/base/react-native.mdx b/embedded-wallets/connect-blockchain/evm/base/react-native.mdx
index 694c1931c65..4ff4c9ca5f9 100644
--- a/embedded-wallets/connect-blockchain/evm/base/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/base/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Base Blockchain in React Nativ
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBase from '../../_general-connect-blockchain/_base.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Base](https://base.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Base](https://base.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Base
 
diff --git a/embedded-wallets/connect-blockchain/evm/bitkub/node.mdx b/embedded-wallets/connect-blockchain/evm/bitkub/node.mdx
index ff4dfefa433..b3ef6de2b04 100644
--- a/embedded-wallets/connect-blockchain/evm/bitkub/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/bitkub/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Bitkub Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBitkub from '../../_general-connect-blockchain/_bitkub.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Bitkub](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Bitkub](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Bitkub
 
diff --git a/embedded-wallets/connect-blockchain/evm/bitkub/react-native.mdx b/embedded-wallets/connect-blockchain/evm/bitkub/react-native.mdx
index 8a3d3ed019a..af0d0e1319a 100644
--- a/embedded-wallets/connect-blockchain/evm/bitkub/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/bitkub/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Bitkub Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBitkub from '../../_general-connect-blockchain/_bitkub.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Bitkub](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Bitkub](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Bitkub
 
diff --git a/embedded-wallets/connect-blockchain/evm/bnb/node.mdx b/embedded-wallets/connect-blockchain/evm/bnb/node.mdx
index 414141e3888..b6de96a2f1a 100644
--- a/embedded-wallets/connect-blockchain/evm/bnb/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/bnb/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the BNB Blockchain in Node | Embed
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBnb from '../../_general-connect-blockchain/_bnb.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [BNB](https://www.bnbchain.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [BNB](https://www.bnbchain.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for BNB
 
diff --git a/embedded-wallets/connect-blockchain/evm/bnb/react-native.mdx b/embedded-wallets/connect-blockchain/evm/bnb/react-native.mdx
index 3d48854ba85..e3358879b18 100644
--- a/embedded-wallets/connect-blockchain/evm/bnb/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/bnb/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the BNB Blockchain in React Native
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsBnb from '../../_general-connect-blockchain/_bnb.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [BNB](https://www.bnbchain.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [BNB](https://www.bnbchain.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for BNB
 
diff --git a/embedded-wallets/connect-blockchain/evm/celo/node.mdx b/embedded-wallets/connect-blockchain/evm/celo/node.mdx
index b516ad76eed..9efc0ed171e 100644
--- a/embedded-wallets/connect-blockchain/evm/celo/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/celo/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Celo Blockchain in Node | Embe
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsCelo from '../../_general-connect-blockchain/_celo.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Celo](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Celo](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Celo
 
diff --git a/embedded-wallets/connect-blockchain/evm/celo/react-native.mdx b/embedded-wallets/connect-blockchain/evm/celo/react-native.mdx
index ab0518711c7..aef4fc8acc4 100644
--- a/embedded-wallets/connect-blockchain/evm/celo/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/celo/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Celo Blockchain in React Nativ
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsCelo from '../../_general-connect-blockchain/_celo.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Celo](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Celo](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Celo
 
diff --git a/embedded-wallets/connect-blockchain/evm/chiliz/node.mdx b/embedded-wallets/connect-blockchain/evm/chiliz/node.mdx
index 517141477ea..3315f53cf52 100644
--- a/embedded-wallets/connect-blockchain/evm/chiliz/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/chiliz/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Chiliz Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsChiliz from '../../_general-connect-blockchain/_chiliz.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Chiliz](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Chiliz](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Chiliz
 
diff --git a/embedded-wallets/connect-blockchain/evm/chiliz/react-native.mdx b/embedded-wallets/connect-blockchain/evm/chiliz/react-native.mdx
index d660c868e81..eb408eb8ee4 100644
--- a/embedded-wallets/connect-blockchain/evm/chiliz/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/chiliz/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Chiliz Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsChiliz from '../../_general-connect-blockchain/_chiliz.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Chiliz](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Chiliz](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Chiliz
 
diff --git a/embedded-wallets/connect-blockchain/evm/cronos/node.mdx b/embedded-wallets/connect-blockchain/evm/cronos/node.mdx
index 8544abd5298..55104ba391c 100644
--- a/embedded-wallets/connect-blockchain/evm/cronos/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/cronos/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Cronos Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsCronos from '../../_general-connect-blockchain/_cronos.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Cronos](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Cronos](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Cronos
 
diff --git a/embedded-wallets/connect-blockchain/evm/cronos/react-native.mdx b/embedded-wallets/connect-blockchain/evm/cronos/react-native.mdx
index 97421992597..e58b7b7e0d2 100644
--- a/embedded-wallets/connect-blockchain/evm/cronos/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/cronos/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Cronos Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsCronos from '../../_general-connect-blockchain/_cronos.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Cronos](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Cronos](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Cronos
 
diff --git a/embedded-wallets/connect-blockchain/evm/ethereum/react-native.mdx b/embedded-wallets/connect-blockchain/evm/ethereum/react-native.mdx
index e94ae90c549..5beaa829723 100644
--- a/embedded-wallets/connect-blockchain/evm/ethereum/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/ethereum/react-native.mdx
@@ -17,7 +17,7 @@ import Tabs from '@theme/Tabs'
 import TabItem from '@theme/TabItem'
 import ChainDetailsEthereum from '../../_general-connect-blockchain/_ethereum.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ethereum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Ethereum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Ethereum
 
diff --git a/embedded-wallets/connect-blockchain/evm/fhenix/node.mdx b/embedded-wallets/connect-blockchain/evm/fhenix/node.mdx
index 4955201da40..d32b420d66b 100644
--- a/embedded-wallets/connect-blockchain/evm/fhenix/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/fhenix/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Fhenix Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFhenix from '../../_general-connect-blockchain/_fhenix.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Fhenix](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Fhenix](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Fhenix
 
diff --git a/embedded-wallets/connect-blockchain/evm/fhenix/react-native.mdx b/embedded-wallets/connect-blockchain/evm/fhenix/react-native.mdx
index bde6c474203..49c7faae41c 100644
--- a/embedded-wallets/connect-blockchain/evm/fhenix/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/fhenix/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Fhenix Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFhenix from '../../_general-connect-blockchain/_fhenix.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Fhenix](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Fhenix](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Fhenix
 
diff --git a/embedded-wallets/connect-blockchain/evm/flare/node.mdx b/embedded-wallets/connect-blockchain/evm/flare/node.mdx
index 997549cfe58..abda5f0ea2e 100644
--- a/embedded-wallets/connect-blockchain/evm/flare/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/flare/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Flare Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFlare from '../../_general-connect-blockchain/_flare.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flare](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flare](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Flare
 
diff --git a/embedded-wallets/connect-blockchain/evm/flare/react-native.mdx b/embedded-wallets/connect-blockchain/evm/flare/react-native.mdx
index c1a25118ed4..cf2992d1ffc 100644
--- a/embedded-wallets/connect-blockchain/evm/flare/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/flare/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Flare Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFlare from '../../_general-connect-blockchain/_flare.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flare](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flare](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Flare
 
diff --git a/embedded-wallets/connect-blockchain/evm/flow/node.mdx b/embedded-wallets/connect-blockchain/evm/flow/node.mdx
index 375be10e33c..78cdc11ccb6 100644
--- a/embedded-wallets/connect-blockchain/evm/flow/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/flow/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Flow Blockchain in Node | Embe
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFlow from '../../_general-connect-blockchain/_flow.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flow](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flow](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Flow
 
diff --git a/embedded-wallets/connect-blockchain/evm/flow/react-native.mdx b/embedded-wallets/connect-blockchain/evm/flow/react-native.mdx
index 5894b322685..f4aeb2e59ca 100644
--- a/embedded-wallets/connect-blockchain/evm/flow/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/flow/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Flow Blockchain in React Nativ
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsFlow from '../../_general-connect-blockchain/_flow.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flow](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Flow](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Flow
 
diff --git a/embedded-wallets/connect-blockchain/evm/harmony/node.mdx b/embedded-wallets/connect-blockchain/evm/harmony/node.mdx
index 876a7096669..12b00ef196b 100644
--- a/embedded-wallets/connect-blockchain/evm/harmony/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/harmony/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Harmony Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsHarmony from '../../_general-connect-blockchain/_harmony.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Harmony](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Harmony](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Harmony
 
diff --git a/embedded-wallets/connect-blockchain/evm/harmony/react-native.mdx b/embedded-wallets/connect-blockchain/evm/harmony/react-native.mdx
index c1ddd912b65..ed9122bd756 100644
--- a/embedded-wallets/connect-blockchain/evm/harmony/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/harmony/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Harmony Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsHarmony from '../../_general-connect-blockchain/_harmony.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Harmony](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Harmony](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Harmony
 
diff --git a/embedded-wallets/connect-blockchain/evm/hedera/node.mdx b/embedded-wallets/connect-blockchain/evm/hedera/node.mdx
index b3cf639760d..96ff7e37ac8 100644
--- a/embedded-wallets/connect-blockchain/evm/hedera/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/hedera/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Hedera Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsHedera from '../../_general-connect-blockchain/_hedera.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Hedera](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Hedera](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Hedera
 
diff --git a/embedded-wallets/connect-blockchain/evm/hedera/react-native.mdx b/embedded-wallets/connect-blockchain/evm/hedera/react-native.mdx
index 69f00e3f054..04f14ef8426 100644
--- a/embedded-wallets/connect-blockchain/evm/hedera/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/hedera/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Hedera Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsHedera from '../../_general-connect-blockchain/_hedera.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Hedera](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Hedera](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Hedera
 
diff --git a/embedded-wallets/connect-blockchain/evm/kinto/node.mdx b/embedded-wallets/connect-blockchain/evm/kinto/node.mdx
index 4a9d553e74b..20274612fa6 100644
--- a/embedded-wallets/connect-blockchain/evm/kinto/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/kinto/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Kinto Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsKinto from '../../_general-connect-blockchain/_kinto.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Kinto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Kinto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Kinto
 
diff --git a/embedded-wallets/connect-blockchain/evm/kinto/react-native.mdx b/embedded-wallets/connect-blockchain/evm/kinto/react-native.mdx
index e4209558f97..bf87dcdd4e6 100644
--- a/embedded-wallets/connect-blockchain/evm/kinto/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/kinto/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Kinto Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsKinto from '../../_general-connect-blockchain/_kinto.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Kinto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Kinto](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Kinto
 
diff --git a/embedded-wallets/connect-blockchain/evm/klaytn/node.mdx b/embedded-wallets/connect-blockchain/evm/klaytn/node.mdx
index 5d228660adf..c91f87bfe41 100644
--- a/embedded-wallets/connect-blockchain/evm/klaytn/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/klaytn/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Klaytn Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsKlaytn from '../../_general-connect-blockchain/_klaytn.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Klaytn](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Klaytn](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Klaytn
 
diff --git a/embedded-wallets/connect-blockchain/evm/klaytn/react-native.mdx b/embedded-wallets/connect-blockchain/evm/klaytn/react-native.mdx
index 35d5f1ffdcf..0c1799a570c 100644
--- a/embedded-wallets/connect-blockchain/evm/klaytn/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/klaytn/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Klaytn Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsKlaytn from '../../_general-connect-blockchain/_klaytn.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Klaytn](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Klaytn](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Klaytn
 
diff --git a/embedded-wallets/connect-blockchain/evm/linea/node.mdx b/embedded-wallets/connect-blockchain/evm/linea/node.mdx
index 6f4b5a3297b..03e31a0ed36 100644
--- a/embedded-wallets/connect-blockchain/evm/linea/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/linea/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Linea Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsLinea from '../../_general-connect-blockchain/_linea.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Linea](https://linea.build/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Linea](https://linea.build/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Linea
 
diff --git a/embedded-wallets/connect-blockchain/evm/linea/react-native.mdx b/embedded-wallets/connect-blockchain/evm/linea/react-native.mdx
index d2fe0b76125..0ef8774f97d 100644
--- a/embedded-wallets/connect-blockchain/evm/linea/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/linea/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Linea Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsLinea from '../../_general-connect-blockchain/_linea.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Linea](https://linea.build/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Linea](https://linea.build/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Linea
 
diff --git a/embedded-wallets/connect-blockchain/evm/manta/node.mdx b/embedded-wallets/connect-blockchain/evm/manta/node.mdx
index c78f48cec8a..1b3449d80e9 100644
--- a/embedded-wallets/connect-blockchain/evm/manta/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/manta/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Manta Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsManta from '../../_general-connect-blockchain/_manta.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Manta](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Manta](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Manta
 
diff --git a/embedded-wallets/connect-blockchain/evm/manta/react-native.mdx b/embedded-wallets/connect-blockchain/evm/manta/react-native.mdx
index 1721f70ec46..48f1f8d118f 100644
--- a/embedded-wallets/connect-blockchain/evm/manta/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/manta/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Manta Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsManta from '../../_general-connect-blockchain/_manta.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Manta](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Manta](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Manta
 
diff --git a/embedded-wallets/connect-blockchain/evm/metis/node.mdx b/embedded-wallets/connect-blockchain/evm/metis/node.mdx
index 58935544c7f..b325a493f66 100644
--- a/embedded-wallets/connect-blockchain/evm/metis/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/metis/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Metis Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMetis from '../../_general-connect-blockchain/_metis.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Metis](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Metis](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Metis
 
diff --git a/embedded-wallets/connect-blockchain/evm/metis/react-native.mdx b/embedded-wallets/connect-blockchain/evm/metis/react-native.mdx
index 98882d61042..6f4542870d1 100644
--- a/embedded-wallets/connect-blockchain/evm/metis/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/metis/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Metis Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMetis from '../../_general-connect-blockchain/_metis.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Metis](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Metis](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Metis
 
diff --git a/embedded-wallets/connect-blockchain/evm/mint/node.mdx b/embedded-wallets/connect-blockchain/evm/mint/node.mdx
index b3472539d75..bd1084fa8bc 100644
--- a/embedded-wallets/connect-blockchain/evm/mint/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/mint/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Mint Blockchain in Node | Embe
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMint from '../../_general-connect-blockchain/_mint.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Mint](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Mint](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Mint
 
diff --git a/embedded-wallets/connect-blockchain/evm/mint/react-native.mdx b/embedded-wallets/connect-blockchain/evm/mint/react-native.mdx
index 32518eaa56f..881e7078982 100644
--- a/embedded-wallets/connect-blockchain/evm/mint/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/mint/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Mint Blockchain in React Nativ
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMint from '../../_general-connect-blockchain/_mint.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Mint](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Mint](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Mint
 
diff --git a/embedded-wallets/connect-blockchain/evm/moonbeam/node.mdx b/embedded-wallets/connect-blockchain/evm/moonbeam/node.mdx
index ceb26b18fb0..f476f2272e7 100644
--- a/embedded-wallets/connect-blockchain/evm/moonbeam/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/moonbeam/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Moonbeam Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMoonbeam from '../../_general-connect-blockchain/_moonbeam.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonbeam](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonbeam](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Moonbeam
 
diff --git a/embedded-wallets/connect-blockchain/evm/moonbeam/react-native.mdx b/embedded-wallets/connect-blockchain/evm/moonbeam/react-native.mdx
index fe3a5bb1054..4f629619c4b 100644
--- a/embedded-wallets/connect-blockchain/evm/moonbeam/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/moonbeam/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Moonbeam Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMoonbeam from '../../_general-connect-blockchain/_moonbeam.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonbeam](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonbeam](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Moonbeam
 
diff --git a/embedded-wallets/connect-blockchain/evm/moonriver/node.mdx b/embedded-wallets/connect-blockchain/evm/moonriver/node.mdx
index 6e4bd589b6a..60639872b82 100644
--- a/embedded-wallets/connect-blockchain/evm/moonriver/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/moonriver/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Moonriver Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMoonriver from '../../_general-connect-blockchain/_moonriver.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonriver](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonriver](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Moonriver
 
diff --git a/embedded-wallets/connect-blockchain/evm/moonriver/react-native.mdx b/embedded-wallets/connect-blockchain/evm/moonriver/react-native.mdx
index 59db20ac076..a1d4f1e3de9 100644
--- a/embedded-wallets/connect-blockchain/evm/moonriver/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/moonriver/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Moonriver Blockchain in React
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMoonriver from '../../_general-connect-blockchain/_moonriver.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonriver](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Moonriver](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Moonriver
 
diff --git a/embedded-wallets/connect-blockchain/evm/morph/node.mdx b/embedded-wallets/connect-blockchain/evm/morph/node.mdx
index 788f1b0d1ad..ea42e5f3987 100644
--- a/embedded-wallets/connect-blockchain/evm/morph/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/morph/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Morph Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMorph from '../../_general-connect-blockchain/_morph.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Morph](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Morph](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Morph
 
diff --git a/embedded-wallets/connect-blockchain/evm/morph/react-native.mdx b/embedded-wallets/connect-blockchain/evm/morph/react-native.mdx
index c586856fce7..971dc082e19 100644
--- a/embedded-wallets/connect-blockchain/evm/morph/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/morph/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Morph Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsMorph from '../../_general-connect-blockchain/_morph.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Morph](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Morph](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Morph
 
diff --git a/embedded-wallets/connect-blockchain/evm/neon/node.mdx b/embedded-wallets/connect-blockchain/evm/neon/node.mdx
index df8b10a5bff..4a4d3cbd4e4 100644
--- a/embedded-wallets/connect-blockchain/evm/neon/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/neon/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Neon Blockchain in Node | Embe
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsNeon from '../../_general-connect-blockchain/_neon.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Neon](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Neon](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Neon
 
diff --git a/embedded-wallets/connect-blockchain/evm/neon/react-native.mdx b/embedded-wallets/connect-blockchain/evm/neon/react-native.mdx
index 83ddeab1d6e..02ee5247bfa 100644
--- a/embedded-wallets/connect-blockchain/evm/neon/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/neon/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Neon Blockchain in React Nativ
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsNeon from '../../_general-connect-blockchain/_neon.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Neon](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Neon](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Neon
 
diff --git a/embedded-wallets/connect-blockchain/evm/nibiru/node.mdx b/embedded-wallets/connect-blockchain/evm/nibiru/node.mdx
index 5e5cd9ac502..031faea4320 100644
--- a/embedded-wallets/connect-blockchain/evm/nibiru/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/nibiru/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Nibiru Blockchain in Node | Em
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsNibiru from '../../_general-connect-blockchain/_nibiru.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Nibiru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Nibiru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Nibiru
 
diff --git a/embedded-wallets/connect-blockchain/evm/nibiru/react-native.mdx b/embedded-wallets/connect-blockchain/evm/nibiru/react-native.mdx
index 0c988dfa506..cb649ac32a9 100644
--- a/embedded-wallets/connect-blockchain/evm/nibiru/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/nibiru/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Nibiru Blockchain in React Nat
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsNibiru from '../../_general-connect-blockchain/_nibiru.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Nibiru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Nibiru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Nibiru
 
diff --git a/embedded-wallets/connect-blockchain/evm/opbnb/node.mdx b/embedded-wallets/connect-blockchain/evm/opbnb/node.mdx
index 3b940a9019f..2d67be60503 100644
--- a/embedded-wallets/connect-blockchain/evm/opbnb/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/opbnb/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the OpBNB Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsOpBnb from '../../_general-connect-blockchain/_opbnb.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [OpBNB](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [OpBNB](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for OpBNB
 
diff --git a/embedded-wallets/connect-blockchain/evm/opbnb/react-native.mdx b/embedded-wallets/connect-blockchain/evm/opbnb/react-native.mdx
index 771b093d37b..3868227a247 100644
--- a/embedded-wallets/connect-blockchain/evm/opbnb/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/opbnb/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the OpBNB Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsOpBnb from '../../_general-connect-blockchain/_opbnb.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [OpBNB](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [OpBNB](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for OpBNB
 
diff --git a/embedded-wallets/connect-blockchain/evm/optimism/node.mdx b/embedded-wallets/connect-blockchain/evm/optimism/node.mdx
index e556eb38f6c..cb32df76b42 100644
--- a/embedded-wallets/connect-blockchain/evm/optimism/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/optimism/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Optimism Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsOptimism from '../../_general-connect-blockchain/_optimism.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Optimism](https://www.optimism.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Optimism](https://www.optimism.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Optimism
 
diff --git a/embedded-wallets/connect-blockchain/evm/optimism/react-native.mdx b/embedded-wallets/connect-blockchain/evm/optimism/react-native.mdx
index 7bc537dc58d..8b5cf3c0860 100644
--- a/embedded-wallets/connect-blockchain/evm/optimism/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/optimism/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Optimism Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsOptimism from '../../_general-connect-blockchain/_optimism.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Optimism](https://www.optimism.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Optimism](https://www.optimism.io/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Optimism
 
diff --git a/embedded-wallets/connect-blockchain/evm/polygon/node.mdx b/embedded-wallets/connect-blockchain/evm/polygon/node.mdx
index eb7ebf0d07e..05fcbc91e6b 100644
--- a/embedded-wallets/connect-blockchain/evm/polygon/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/polygon/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Polygon Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsPolygon from '../../_general-connect-blockchain/_polygon.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Polygon](https://polygon.technology/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Polygon](https://polygon.technology/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Polygon
 
diff --git a/embedded-wallets/connect-blockchain/evm/polygon/react-native.mdx b/embedded-wallets/connect-blockchain/evm/polygon/react-native.mdx
index 4da11b573dd..709da3e9484 100644
--- a/embedded-wallets/connect-blockchain/evm/polygon/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/polygon/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Polygon Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsPolygon from '../../_general-connect-blockchain/_polygon.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Polygon](https://polygon.technology/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Polygon](https://polygon.technology/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Polygon
 
diff --git a/embedded-wallets/connect-blockchain/evm/rootstock/node.mdx b/embedded-wallets/connect-blockchain/evm/rootstock/node.mdx
index c25c506eb4d..333459e9900 100644
--- a/embedded-wallets/connect-blockchain/evm/rootstock/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/rootstock/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Rootstock Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsRootstock from '../../_general-connect-blockchain/_rootstock.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Rootstock](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Rootstock](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Rootstock
 
diff --git a/embedded-wallets/connect-blockchain/evm/rootstock/react-native.mdx b/embedded-wallets/connect-blockchain/evm/rootstock/react-native.mdx
index 503d09e047e..360463efe71 100644
--- a/embedded-wallets/connect-blockchain/evm/rootstock/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/rootstock/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Rootstock Blockchain in React
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsRootstock from '../../_general-connect-blockchain/_rootstock.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Rootstock](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Rootstock](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Rootstock
 
diff --git a/embedded-wallets/connect-blockchain/evm/saakuru/node.mdx b/embedded-wallets/connect-blockchain/evm/saakuru/node.mdx
index 4ec9a8e8962..00e749cad49 100644
--- a/embedded-wallets/connect-blockchain/evm/saakuru/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/saakuru/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Saakuru Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSaakuru from '../../_general-connect-blockchain/_saakuru.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Saakuru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Saakuru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Saakuru
 
diff --git a/embedded-wallets/connect-blockchain/evm/saakuru/react-native.mdx b/embedded-wallets/connect-blockchain/evm/saakuru/react-native.mdx
index 23fe5423bd3..f67816feb92 100644
--- a/embedded-wallets/connect-blockchain/evm/saakuru/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/saakuru/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Saakuru Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSaakuru from '../../_general-connect-blockchain/_saakuru.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Saakuru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Saakuru](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Saakuru
 
diff --git a/embedded-wallets/connect-blockchain/evm/shardeum/node.mdx b/embedded-wallets/connect-blockchain/evm/shardeum/node.mdx
index b240dbc105d..2aee77bdf26 100644
--- a/embedded-wallets/connect-blockchain/evm/shardeum/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/shardeum/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Shardeum Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsShardeum from '../../_general-connect-blockchain/_shardeum.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Shardeum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Shardeum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Shardeum
 
diff --git a/embedded-wallets/connect-blockchain/evm/shardeum/react-native.mdx b/embedded-wallets/connect-blockchain/evm/shardeum/react-native.mdx
index d4bf807d8b8..f0b39e27a3a 100644
--- a/embedded-wallets/connect-blockchain/evm/shardeum/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/shardeum/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Shardeum Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsShardeum from '../../_general-connect-blockchain/_shardeum.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Shardeum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Shardeum](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Shardeum
 
diff --git a/embedded-wallets/connect-blockchain/evm/skale/node.mdx b/embedded-wallets/connect-blockchain/evm/skale/node.mdx
index d4f0aaeede1..3f68c4c4fb2 100644
--- a/embedded-wallets/connect-blockchain/evm/skale/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/skale/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Skale Blockchain in Node | Emb
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSkale from '../../_general-connect-blockchain/_skale.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Skale](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Skale](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Skale
 
diff --git a/embedded-wallets/connect-blockchain/evm/skale/react-native.mdx b/embedded-wallets/connect-blockchain/evm/skale/react-native.mdx
index 441ada4a09a..9fbd8323c90 100644
--- a/embedded-wallets/connect-blockchain/evm/skale/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/skale/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Skale Blockchain in React Nati
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSkale from '../../_general-connect-blockchain/_skale.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Skale](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Skale](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Skale
 
diff --git a/embedded-wallets/connect-blockchain/evm/soneium/node.mdx b/embedded-wallets/connect-blockchain/evm/soneium/node.mdx
index 9ff63e9a7e1..4494265a39a 100644
--- a/embedded-wallets/connect-blockchain/evm/soneium/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/soneium/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Soneium Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSoneium from '../../_general-connect-blockchain/_soneium.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Soneium](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Soneium](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Soneium
 
diff --git a/embedded-wallets/connect-blockchain/evm/soneium/react-native.mdx b/embedded-wallets/connect-blockchain/evm/soneium/react-native.mdx
index 9e4231f66bf..18b75d0c86f 100644
--- a/embedded-wallets/connect-blockchain/evm/soneium/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/soneium/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Soneium Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSoneium from '../../_general-connect-blockchain/_soneium.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Soneium](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Soneium](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Soneium
 
diff --git a/embedded-wallets/connect-blockchain/evm/songbird/node.mdx b/embedded-wallets/connect-blockchain/evm/songbird/node.mdx
index 59461deede3..861a7c2531a 100644
--- a/embedded-wallets/connect-blockchain/evm/songbird/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/songbird/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Songbird Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSongbird from '../../_general-connect-blockchain/_songbird.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Songbird](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Songbird](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Songbird
 
diff --git a/embedded-wallets/connect-blockchain/evm/songbird/react-native.mdx b/embedded-wallets/connect-blockchain/evm/songbird/react-native.mdx
index 68bd488b5d3..c91724bbd09 100644
--- a/embedded-wallets/connect-blockchain/evm/songbird/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/songbird/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Songbird Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsSongbird from '../../_general-connect-blockchain/_songbird.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Songbird](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Songbird](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Songbird
 
diff --git a/embedded-wallets/connect-blockchain/evm/unichain/node.mdx b/embedded-wallets/connect-blockchain/evm/unichain/node.mdx
index 260afab366e..b4a53d02f2a 100644
--- a/embedded-wallets/connect-blockchain/evm/unichain/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/unichain/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Unichain Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsUnichain from '../../_general-connect-blockchain/_unichain.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Unichain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Unichain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Unichain
 
diff --git a/embedded-wallets/connect-blockchain/evm/unichain/react-native.mdx b/embedded-wallets/connect-blockchain/evm/unichain/react-native.mdx
index 840295ec32a..ec005722b4d 100644
--- a/embedded-wallets/connect-blockchain/evm/unichain/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/unichain/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Unichain Blockchain in React N
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsUnichain from '../../_general-connect-blockchain/_unichain.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Unichain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Unichain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Unichain
 
diff --git a/embedded-wallets/connect-blockchain/evm/xdc/node.mdx b/embedded-wallets/connect-blockchain/evm/xdc/node.mdx
index 3885c311fb9..8db0e1bfdde 100644
--- a/embedded-wallets/connect-blockchain/evm/xdc/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/xdc/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the XDC Blockchain in Node | Embed
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsXdc from '../../_general-connect-blockchain/_xdc.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [XDC](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [XDC](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for XDC
 
diff --git a/embedded-wallets/connect-blockchain/evm/xdc/react-native.mdx b/embedded-wallets/connect-blockchain/evm/xdc/react-native.mdx
index 9277c2b0b2b..0c894187765 100644
--- a/embedded-wallets/connect-blockchain/evm/xdc/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/xdc/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the XDC Blockchain in React Native
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsXdc from '../../_general-connect-blockchain/_xdc.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [XDC](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [XDC](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for XDC
 
diff --git a/embedded-wallets/connect-blockchain/evm/zetachain/node.mdx b/embedded-wallets/connect-blockchain/evm/zetachain/node.mdx
index 32ad4c98d0f..c3834c25679 100644
--- a/embedded-wallets/connect-blockchain/evm/zetachain/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zetachain/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zetachain Blockchain in Node |
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZetachain from '../../_general-connect-blockchain/_zetachain.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zetachain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zetachain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zetachain
 
diff --git a/embedded-wallets/connect-blockchain/evm/zetachain/react-native.mdx b/embedded-wallets/connect-blockchain/evm/zetachain/react-native.mdx
index 733fd575ecb..b86353767be 100644
--- a/embedded-wallets/connect-blockchain/evm/zetachain/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zetachain/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zetachain Blockchain in React
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZetachain from '../../_general-connect-blockchain/_zetachain.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zetachain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zetachain](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zetachain
 
diff --git a/embedded-wallets/connect-blockchain/evm/zilliqa/node.mdx b/embedded-wallets/connect-blockchain/evm/zilliqa/node.mdx
index 20219ae1942..a870a67ef41 100644
--- a/embedded-wallets/connect-blockchain/evm/zilliqa/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zilliqa/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zilliqa Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZilliqa from '../../_general-connect-blockchain/_zilliqa.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zilliqa](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zilliqa](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zilliqa
 
diff --git a/embedded-wallets/connect-blockchain/evm/zilliqa/react-native.mdx b/embedded-wallets/connect-blockchain/evm/zilliqa/react-native.mdx
index b192d3c1873..b765c773cd4 100644
--- a/embedded-wallets/connect-blockchain/evm/zilliqa/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zilliqa/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zilliqa Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZilliqa from '../../_general-connect-blockchain/_zilliqa.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zilliqa](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zilliqa](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zilliqa
 
diff --git a/embedded-wallets/connect-blockchain/evm/zircuit/node.mdx b/embedded-wallets/connect-blockchain/evm/zircuit/node.mdx
index 07cd87c5c97..aed4b3c9899 100644
--- a/embedded-wallets/connect-blockchain/evm/zircuit/node.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zircuit/node.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zircuit Blockchain in Node | E
 import EVMInteraction from '../../_node-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZircuit from '../../_general-connect-blockchain/_zircuit.mdx'
 
-While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zircuit](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth Node SDK, you get a Ethers Signer on successful authentication. This signer can be used with libraries like [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zircuit](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zircuit
 
diff --git a/embedded-wallets/connect-blockchain/evm/zircuit/react-native.mdx b/embedded-wallets/connect-blockchain/evm/zircuit/react-native.mdx
index 4ca3aa1addb..78d77943d93 100644
--- a/embedded-wallets/connect-blockchain/evm/zircuit/react-native.mdx
+++ b/embedded-wallets/connect-blockchain/evm/zircuit/react-native.mdx
@@ -10,7 +10,7 @@ description: 'Integrate Embedded Wallets with the Zircuit Blockchain in React Na
 import EVMInteraction from '../../_react-native-connect-blockchain/_evm-interaction.mdx'
 import ChainDetailsZircuit from '../../_general-connect-blockchain/_zircuit.mdx'
 
-While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [Metamask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zircuit](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started quickly on that.
+While using the Web3Auth React Native SDK, you get a [`EIP1193`](https://eips.ethereum.org/EIPS/eip-1193) provider, similar to the [MetaMask Provider](https://docs.metamask.io/guide/ethereum-provider.html). This provider can be used with libraries like [`web3.js`](https://web3js.readthedocs.io/en/v1.2.8/getting-started.html), [`ethers.js`](https://docs.ethers.io/v5/getting-started/) etc. to make [Zircuit](https://ethereum.org/) blockchain calls like getting the user's `account`, fetching `balance`, `sign transaction`, `send transaction`, `read` from and `write` to the smart contract, etc. We have highlighted a few here to get you started.
 
 ## Chain details for Zircuit
 
diff --git a/embedded-wallets/dashboard/advanced/key-export.mdx b/embedded-wallets/dashboard/advanced/key-export.mdx
index f5ad47f6431..adbcea03ea0 100644
--- a/embedded-wallets/dashboard/advanced/key-export.mdx
+++ b/embedded-wallets/dashboard/advanced/key-export.mdx
@@ -240,11 +240,11 @@ async function createSecureBackup() {
 
 Key handling best practices:
 
-- Minimize exposure: Retrieve keys only when necessary
-- Secure transmission: Use HTTPS and encrypted channels
-- Memory management: Clear private keys from memory immediately after use
-- No persistent storage: **Never** store private keys in databases or local storage
-- Audit logging: Log key export events for security monitoring
+- **Minimize exposure**: Retrieve keys only when necessary
+- **Secure transmission**: Use HTTPS and encrypted channels
+- **Memory management**: Clear private keys from memory immediately after use
+- **No persistent storage**: **Never** store private keys in databases or local storage
+- **Audit logging**: Log key export events for security monitoring
 
 #### Implementation security
 
@@ -312,10 +312,10 @@ const securityWarnings = {
 
 It's vital to comply with regulations, always consider:
 
-- Data protection: Ensure key export complies with privacy regulations
-- Audit requirements: Maintain records of key export events
-- User consent: Obtain explicit consent for key export operations
-- Jurisdictional laws: Consider local regulations regarding cryptographic material
+- **Data protection**: Ensure key export complies with privacy regulations
+- **Audit requirements**: Maintain records of key export events
+- **User consent**: Obtain explicit consent for key export operations
+- **Jurisdictional laws**: Consider local regulations regarding cryptographic material
 
 ## Monitoring and analytics
 
diff --git a/embedded-wallets/dashboard/advanced/session-management.mdx b/embedded-wallets/dashboard/advanced/session-management.mdx
index 930e0830d50..9c3e08eb6db 100644
--- a/embedded-wallets/dashboard/advanced/session-management.mdx
+++ b/embedded-wallets/dashboard/advanced/session-management.mdx
@@ -83,10 +83,10 @@ The following durations are typical for the stated use cases:
 
 In some use cases longer session durations can benefit the user:
 
-- Improved UX: Reduces authentication friction for users
-- Productivity: Minimizes workflow interruptions
-- Retention: Decreases abandonment due to re-authentication
-- Convenience: Better for applications with frequent usage
+- **Improved UX**: Reduces authentication friction for users
+- **Productivity**: Minimizes workflow interruptions
+- **Retention**: Decreases abandonment due to re-authentication
+- **Convenience**: Better for applications with frequent usage
 
 The following durations are typical for the stated use cases:
 
diff --git a/embedded-wallets/dashboard/analytics.mdx b/embedded-wallets/dashboard/analytics.mdx
index 4193974c432..e4ece211946 100644
--- a/embedded-wallets/dashboard/analytics.mdx
+++ b/embedded-wallets/dashboard/analytics.mdx
@@ -7,7 +7,7 @@ description: 'Monitor project analytics in Web3Auth Dashboard | Embedded Wallets
 
 import DashboardAnalytics from '@site/static/img/embedded-wallets/w3a-dashboard/dashboard-analytics.png'
 
-The project analytics section in the Web3Auth dashboard provides developers with a comprehensive overview of user activity and project engagement. This analytics system gathers and visualizes key data points to help developers monitor authentication trends, evaluate project performance, and make informed decisions to enhance user experience.
+The project analytics section in the Embedded Wallets dashboard provides developers with a comprehensive overview of user activity and project engagement. This analytics system gathers and visualizes key data points to help developers monitor authentication trends, evaluate project performance, and make informed decisions to enhance user experience.
 
 By offering visibility into user behavior and system usage, analytics empowers teams to optimize authentication flows, track growth, and ensure the platform's reliability at scale.
 
diff --git a/embedded-wallets/dashboard/authentication.mdx b/embedded-wallets/dashboard/authentication.mdx
index 4aea24a9316..44445730877 100644
--- a/embedded-wallets/dashboard/authentication.mdx
+++ b/embedded-wallets/dashboard/authentication.mdx
@@ -208,7 +208,7 @@ For most applications, it is recommended to either pair Basic Logins with altern
 
 ### Social logins
 
-Social logins allow users to authenticate using their existing accounts from widely adopted platforms, offering a seamless and familiar experience. Web3Auth supports a wide range of social identity providers, including:
+Social logins allow users to authenticate using their existing accounts from widely adopted platforms, offering a seamless and familiar experience. Embedded Wallets supports a wide range of social identity providers, including:
 
 Each social login method can be configured individually through the Web3Auth Dashboard. Developers can follow platform-specific guides to obtain necessary credentials (such as client IDs, secrets), and enable the desired providers.
 
diff --git a/embedded-wallets/dashboard/chains-and-networks.mdx b/embedded-wallets/dashboard/chains-and-networks.mdx
index 939e66f5b28..655a3a41adf 100644
--- a/embedded-wallets/dashboard/chains-and-networks.mdx
+++ b/embedded-wallets/dashboard/chains-and-networks.mdx
@@ -40,8 +40,8 @@ And many more...
 For networks not included in the pre-configured list, developers can add custom blockchain networks by providing:
 
 - Chain ID: The unique identifier for the blockchain network
-- Currency Symbol: The native token symbol (such as ETH, MATIC, AVAX)
-- Block Explorer URL: The base URL for the network's block explorer
+- Currency symbol: The native token symbol (such as ETH, MATIC, AVAX)
+- Block explorer URL: The base URL for the network's block explorer
 - Namespace: The blockchain namespace (typically "eip155" for EVM-compatible chains)
 - RPC URL: The endpoint for interacting with the blockchain network
 
diff --git a/embedded-wallets/dashboard/customization.mdx b/embedded-wallets/dashboard/customization.mdx
index b46819b3cee..2e2041c78c8 100644
--- a/embedded-wallets/dashboard/customization.mdx
+++ b/embedded-wallets/dashboard/customization.mdx
@@ -10,7 +10,7 @@ import CustomizationLoginModal from '@site/static/img/embedded-wallets/w3a-dashb
 
 ## Branding
 
-The branding page under the customization section of the Web3Auth dashboard allows developers to personalize the visual identity of their application across multiple user interfaces. This includes the login screens, Multi-Factor Authentication (MFA) screens, wallet UI, and login modals.
+The branding page under the customization section of the Embedded Wallets dashboard allows developers to personalize the visual identity of their application across multiple user interfaces. This includes the login screens, Multi-Factor Authentication (MFA) screens, wallet UI, and login modals.
 
 Effective branding ensures a seamless and recognizable user experience, helping users feel confident that they are interacting with your application—even when interacting with Web3Auth-hosted interfaces.
 
@@ -93,7 +93,7 @@ Choose color combinations that meet accessibility guidelines (such as [WCAG](htt
 
 ## Login modal
 
-The login modal page within the customization section of the Web3Auth dashboard provides developers with granular control over the appearance and behavior of the Web3Auth login flow.
+The login modal page within the customization section of the Embedded Wallets dashboard provides developers with granular control over the appearance and behavior of the Web3Auth login flow.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -111,15 +111,15 @@ The design section offers layout and styling options to customize how the login
 
 Developers can choose between two display modes for the login interface:
 
-- Embedded widget: The login UI is embedded directly within the application's layout. This option is ideal for single-page applications or flows that require a fully integrated experience.
-- Modal widget: The login interface opens as a pop-up modal overlay. This provides a more traditional Web3 wallet experience, where authentication occurs in a floating layer over the existing content.
+- **Embedded widget**: The login UI is embedded directly within the application's layout. This option is ideal for single-page applications or flows that require a fully integrated experience.
+- **Modal widget**: The login interface opens as a pop-up modal overlay. This provides a more traditional Web3 wallet experience, where authentication occurs in a floating layer over the existing content.
 
 #### Logo alignment
 
 Configure how the application logo is aligned within the login modal:
 
-- Center-aligned: Displays the logo at the top center, suitable for balanced layouts.
-- Left-Aligned: Positions the logo to the top-left, often preferred for enterprise or dashboard-style applications.
+- **Center-aligned**: Displays the logo at the top center, suitable for balanced layouts.
+- **Left-aligned**: Positions the logo to the top-left, often preferred for enterprise or dashboard-style applications.
 
 #### Border radius
 
@@ -131,9 +131,9 @@ Adjust the corner curvature of the modal interface:
 
 Refine the shape of buttons and input fields within the modal by selecting:
 
-- Pill: Fully rounded ends for a modern, soft appearance.
-- Rounded: Gently curved corners for a subtle aesthetic.
-- Square: Sharp 90° corners for a more technical or minimalist look.
+- **Pill**: Fully rounded ends for a modern, soft appearance.
+- **Rounded**: Gently curved corners for a subtle aesthetic.
+- **Square**: Sharp 90° corners for a more technical or minimalist look.
 
 These design customizations allow developers to ensure the login experience feels native to the application, enhancing user trust and engagement.
 
@@ -143,9 +143,9 @@ The Authentication section provides flexibility in how login options are present
 
 #### Arrange login order
 
-When multiple login methods (such as, social, email/phone, external wallets) are available, developers can define the order in which these options appear.
+When multiple login methods (such as, social, email/phone, external wallets) are available, developers can define the order in which these options appear:
 
-- Drag and drop the logi n methods to rearrange their position.
+- Drag and drop the login methods to rearrange their position.
 - Order determines the priority and placement of login options shown to users during authentication.
 
 :::note
diff --git a/embedded-wallets/dashboard/project-settings.mdx b/embedded-wallets/dashboard/project-settings.mdx
index 2ad5eb1c011..1e8bc686841 100644
--- a/embedded-wallets/dashboard/project-settings.mdx
+++ b/embedded-wallets/dashboard/project-settings.mdx
@@ -7,7 +7,7 @@ description: 'Configure project settings in Web3Auth Dashboard | Embedded Wallet
 
 import ProjectSettingsGeneral from '@site/static/img/embedded-wallets/w3a-dashboard/project-settings-general.png'
 
-The project settings section of the Web3Auth dashboard allows developers to manage core configuration options for each project. These settings determine how the project integrates with the Web3Auth SDK and how it behaves across different environments.
+The project settings section of the Embedded Wallets dashboard allows developers to manage core configuration options for each project. These settings determine how the project integrates with the Embedded Wallets SDK and how it behaves across different environments.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
@@ -75,12 +75,12 @@ Each platform offers specific features:
 
 A unique identifier automatically generated for each project. This is the primary credential used to authenticate your application with Web3Auth services. This ID is: 
 
-- Publicly safe: Can be exposed in client-side code
-- Required for integration: Essential for all SDK implementations
-- Unique per project: Each project receives a distinct Client ID
-- Immutable: Cannot be changed after generation
+- **Publicly safe**: Can be exposed in client-side code
+- **Required for integration**: Essential for all SDK implementations
+- **Unique per project**: Each project receives a distinct Client ID
+- **Immutable**: Cannot be changed after generation
 
-**Implementation Example:**
+#### Implementation example
 
 ```javascript
 import { Web3Auth } from '@web3auth/modal'
@@ -97,14 +97,13 @@ A **confidential** key used for authenticating server-side API requests and adva
 
 :::danger Security Warning
 
-The client secret must never be exposed in client-side code, mobile applications, or any publicly accessible environment. Exposure could compromise your project's security.
+The client secret must never be exposed in frontend or client-side code, mobile applications, or any publicly accessible environment. Exposure could compromise your project's security.
 
 :::
 
-- Never expose in frontend code or client-side environments
-- Server-side only: Use exclusively in backend services
-- Secure storage: Store in environment variables or secure vaults
-- Rotation capability: Can be regenerated if compromised
+- **Server-side only**: Use exclusively in backend services
+- **Secure storage**: Store in environment variables or secure vaults
+- **Rotation capability**: Can be regenerated if compromised
 
 The client secret is used for:
 
@@ -119,10 +118,10 @@ The client secret is used for:
 
 A public endpoint that exposes the JSON Web Key Set (JWKS) used by Web3Auth to sign JWTs. This endpoint enables you to verify the authenticity of identity tokens issued by Web3Auth, providing the following benefits:
 
-- Dynamic key rotation: Automatically receives updated signing keys
-- Industry standard: JWKS is a widely adopted standard for JWT verification
-- High availability: Backed by Web3Auth's global infrastructure
-- Real-time updates: Always provides current verification keys
+- **Dynamic key rotation**: Automatically receives updated signing keys
+- **Industry standard**: JWKS is a widely adopted standard for JWT verification
+- **High availability**: Backed by Web3Auth's global infrastructure
+- **Real-time updates**: Always provides current verification keys
 
 #### Using the JWKS endpoint
 
@@ -132,7 +131,7 @@ Pass the request to the JWKS endpoint with your project ID as the identifier:
 https://api.web3auth.io/jwks?project_id=<YOUR_PROJECT_ID>
 ```
 
-**Implementation Example:**
+##### Implementation example
 
 ```javascript
 import jwt from 'jsonwebtoken'
@@ -163,10 +162,10 @@ jwt.verify(token, getKey, options, (err, decoded) => {
 
 An alternative to using the JWKS endpoint, this static key allows for token verification without depending on external JWKS URL calls. While providing less security, this offers the following advantages:
 
-- Offline Verification: No external API calls required
-- Reduced Latency: Faster token verification process
-- Network Independence: Works in environments with limited connectivity
-- Simplified Implementation: Single key verification logic
+- **Offline verification**: No external API calls required
+- **Reduced latency**: Faster token verification process
+- **Network independence**: Works in environments with limited connectivity
+- **Simplified implementation**: Single key verification logic
 
 The project verification key is suitable for:
 
@@ -175,7 +174,7 @@ The project verification key is suitable for:
 - Simplified verification workflows
 - Backup verification method
 
-**Implementation Example:**
+#### Implementation example
 
 ```javascript
 import jwt from 'jsonwebtoken'
@@ -202,10 +201,10 @@ The archive project feature allows you to deactivate a project while preserving
 
 **Archive Effects:**
 
-- Read-Only Mode: Project becomes non-functional but viewable
-- Authentication Disabled: Users cannot log in to archived projects
-- Data Preservation: All configuration and user data is retained
-- Reversible: Projects can be restored from archived state
+- **Read-only mode**: Project becomes non-functional but viewable
+- **Authentication disabled**: Users cannot log in to archived projects
+- **Data preservation**: All configuration and user data is retained
+- **Reversible**: Projects can be restored from archived state
 
 **When to Archive:**
 
@@ -223,7 +222,7 @@ The archive project feature allows you to deactivate a project while preserving
 
 :::info Archive vs. Delete
 
-Archiving preserves all project data and allows for restoration. If you need to permanently remove a project, contact Web3Auth support for assistance with proper data deletion procedures.
+Archiving preserves all project data and allows for restoration. If you need to permanently remove a project, contact Embedded Wallets support for assistance with proper data deletion procedures.
 
 :::
 
diff --git a/embedded-wallets/dashboard/wallet-services.mdx b/embedded-wallets/dashboard/wallet-services.mdx
index b756bc8a3b0..76ac900b1e1 100644
--- a/embedded-wallets/dashboard/wallet-services.mdx
+++ b/embedded-wallets/dashboard/wallet-services.mdx
@@ -7,7 +7,7 @@ description: 'Configure wallet services and UI in Web3Auth Dashboard | Embedded
 
 import WalletConfiguration from '@site/static/img/embedded-wallets/w3a-dashboard/wallet-configuration.png'
 
-The wallet configuration tab within the Web3Auth dashboard enables developers to customize the wallet experience provided to users within their decentralized applications (dApps). These settings define the appearance, capabilities, and interactivity of the Web3Auth wallet interface.
+The wallet configuration tab within the Embedded Wallets dashboard enables developers to customize the wallet experience provided to users within their decentralized applications (dApps). These settings define the appearance, capabilities, and interactivity of the Embedded Wallets wallet interface.
 
 <div style={{ flexBasis: '300px', flexGrow: '1', textAlign: 'center' }}>
   <img
diff --git a/embedded-wallets/dashboard/whitelist.mdx b/embedded-wallets/dashboard/whitelist.mdx
index 994725e401d..0e75483f164 100644
--- a/embedded-wallets/dashboard/whitelist.mdx
+++ b/embedded-wallets/dashboard/whitelist.mdx
@@ -34,7 +34,7 @@ Domain whitelisting is a critical security feature that prevents unauthorized ap
 
 ### Supported URL formats
 
-Web3Auth supports various URL formats for comprehensive domain coverage:
+Embedded Wallets supports various URL formats for comprehensive domain coverage:
 
 <Tabs>
 <TabItem value="standard" label="Standard domains">
diff --git a/embedded-wallets/sdk/js/events.mdx b/embedded-wallets/sdk/js/events.mdx
index e650cbc156b..2478a7130bf 100644
--- a/embedded-wallets/sdk/js/events.mdx
+++ b/embedded-wallets/sdk/js/events.mdx
@@ -64,7 +64,7 @@ connectedConnectorName: WALLET_CONNECTOR_TYPE | null
 | `AUTH`              | Web3Auth connector.          |
 | `WALLET_CONNECT_V2` | Wallet Connect V2 connector. |
 | `COINBASE`          | Coinbase connector.          |
-| `METAMASK`          | Metamask connector.          |
+| `METAMASK`          | MetaMask connector.          |
 
   </TabItem>
   <TabItem value="interface" label="Interface">
diff --git a/embedded-wallets/troubleshooting/jwt-errors.mdx b/embedded-wallets/troubleshooting/jwt-errors.mdx
index 9b8607cc600..7313208fae3 100644
--- a/embedded-wallets/troubleshooting/jwt-errors.mdx
+++ b/embedded-wallets/troubleshooting/jwt-errors.mdx
@@ -34,7 +34,7 @@ When configuring Web3Auth's Custom Authentication, you may encounter JWT errors.
 
 "Error occurred while verifying params could not verify identity" error could be because the `verifierIdField` of `extraLoginOptions` is different from the one you have set up during the creation of Verifiers (`JWT Verifiers ID`) on the Web3Auth dashboard.
 
-- This is the `JWT Verifiers ID` field on the `Verifier Modal` of the Web3Auth dashboard.
+- This is the `JWT Verifiers ID` field on the `Verifier Modal` of the Embedded Wallets dashboard.
   <img
     style={{ display: 'block', maxHeight: '200px', marginBottom: '20px' }}
     src={JWTVerifierID}