style pass over features (#2602)

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

Author: m4sterbunny

embedded-wallets/features/external-wallets.mdx

@@ -4,7 +4,7 @@ image: 'img/metamaskog.jpg'
 description: 'A complete, cross-ecosystem wallet aggregation experience built into the Embedded Wallets SDK.'
 ---
 
-The MM Embedded Wallets SDK contains one of the most complete wallet aggregators on the market. It unifies EVM and Solana wallet discovery, connection, and session management into a single, production‑ready layer you can drop into any app.
+The MetaMask Embedded Wallets SDK provides one of the most complete wallet aggregators on the market. It unifies EVM and Solana wallet discovery, connection, and session management into a single, production‑ready layer you can drop into any app.
 
 :::info demo
 
@@ -14,18 +14,18 @@ Looking for a quick preview? See the [Demo](https://demo.web3auth.io).
 
 ## Highlights
 
-- **Cross‑ecosystem**: EVM + Solana in a single flow.
-- **Standards‑native**: EIP‑6963 (EVM) and Solana Wallet Standard.
-- **Works with your stack**: `ethers`, `viem`, `wagmi`, `@solana/web3.js`.
-- **First‑class DX**: Hooks and composables for React/Vue.
-- **Central control**: Manage everything in the Dashboard.
+- **Cross‑ecosystem:** EVM and Solana in a single flow.
+- **Standards‑native:** EIP‑6963 (EVM) and Solana Wallet Standard.
+- **Works with your stack:** `ethers`, `viem`, `wagmi`, `@solana/web3.js`.
+- **First‑class developer experience:** Hooks and composables for React/Vue.
+- **Central control:** Manage everything in the [Embedded Wallets Dashboard](https://dashboard.web3auth.io).
 
 ![Wallet Discovery](/img/wallet-discovery.png) _A familiar, unified wallet selection experience for users._
 
-## Customize flow within the Developer Dashboard
+## Customize flow within the dashboard
 
-- **Wallet aggregator only**: Drop‑in discovery, connection, and session state.
-- **With social logins**: Offer socials and external wallets side‑by‑side in one flow.
+- **Wallet aggregator only:** Drop‑in discovery, connection, and session state.
+- **With social logins:** Offer socials and external wallets side‑by‑side in one flow.
 
 ![Dashboard Wallet Toggle](/img/embedded-wallets/w3a-dashboard/external-wallets-toggle.png) _Toggle social logins and external wallets visibility._
 

embedded-wallets/features/funding.mdx

@@ -6,25 +6,25 @@ description: 'Funding | Embedded Wallets'
 
 MetaMask Embedded Wallets supports multiple ways for users to add funds to their wallets. Let users pick the method that suits them:
 
-- Buy crypto with card, bank transfer, or local payment methods (Fiat On‑Ramp Aggregator).
+- Buy crypto with card, bank transfer, or local payment methods (fiat on‑ramp aggregator).
 - Transfer from an existing wallet or exchange.
 - Connect an external wallet and deposit to the embedded wallet.
 
-## Buy crypto with card or bank transfer (Fiat On‑Ramp Aggregator)
+## Buy crypto with card or bank transfer (fiat on‑ramp aggregator)
 
-The Fiat On-Ramp Aggregator, a key component of the Wallet Services, streamlines the process of converting fiat to cryptocurrency. With integration requiring just a single line of code, it supports over 100 payment methods.
+The fiat on‑ramp aggregator, a key component of the Embedded Wallets' services, streamlines the process of converting fiat to cryptocurrency. With integration requiring just a single line of code, it supports over 100 payment methods.
 
 :::note
 
-The Fiat on Ramp supports both Externally Owned Accounts (EOA) and Account Abstraction (AA) accounts powered by Web3Auth Native Account Abstraction.
+The fiat on-ramp supports both Externally Owned Accounts (EOA) and Account Abstraction (AA) accounts powered by Embedded Wallets' native account abstraction.
 
 Additionally, it supports both EVM and Solana accounts, providing a versatile solution for various blockchain environments.
 
 :::
 
 ### Using the Wallet Services UI
 
-When you click **Add Funds** on the Wallet Services UI, you'll be presented with options to fund your wallet:
+When the user clicks **Add Funds** on the Wallet Services UI, they'll be presented with options to fund their wallet:
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -39,11 +39,11 @@ When you click **Add Funds** on the Wallet Services UI, you'll be presented with
   />
 </div>
 
-You can choose between two funding methods:
+Users can choose to fund by card or QR code.
 
-#### Fund by Card
+#### Fund by card
 
-Select the card option to purchase crypto using a credit or debit card. This will take you to the card payment interface:
+Users select the card option to purchase crypto using a credit or debit card. This takes them to the card payment interface:
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -60,7 +60,7 @@ Select the card option to purchase crypto using a credit or debit card. This wil
 
 #### Fund by QR Code
 
-Select the QR code option to fund your wallet by scanning a QR code with another wallet:
+Users select the QR code option to fund their wallet by scanning a QR code with another wallet:
 
 <div style={{ display: 'flex', margin: '20px 0', justifyContent: 'center' }}>
   <img
@@ -75,17 +75,19 @@ Select the QR code option to fund your wallet by scanning a QR code with another
   />
 </div>
 
-Here's how our aggregator addresses your on-ramping challenges:
+## Overcome on-ramping challenges
 
-- **Global Reach:** Access users in over 50 countries with worldwide payment coverage
+The fiat on‑ramp aggregator addresses your on-ramping challenges:
 
-- **Lower fees:** Save up to 70% on transaction fees by leveraging lower cost local payment providers
+- **Global reach:** Access users in over 50 countries with worldwide payment coverage.
 
-- **Localized Payment Options:** Offer familiar and real-time payment methods to boost user engagement and monetization
+- **Lower fees:** Save up to 70% on transaction fees by leveraging lower cost local payment providers.
 
-- **Higher Transaction Success Rates:** Address high failure rates (30-70%) of traditional methods like Visa/Mastercard in emerging markets by using reliable local payment options.
+- **Localized payment options:** Offer familiar and real-time payment methods to boost user engagement and monetization.
 
-- **Enhanced Security:** Provide a secure and cost-effective solution for both users and merchants, as local payment methods often require 2-factor authentication (2FA) and eliminate chargeback costs.
+- **Higher transaction success rates:** Address high failure rates (30-70%) of traditional methods like Visa/Mastercard in emerging markets by using reliable local payment options.
+
+- **Enhanced security:** Provide a secure and cost-effective solution for both users and merchants, as local payment methods often require 2-factor authentication (2FA) and eliminate chargeback costs.
 
 :::info
 
@@ -101,17 +103,17 @@ The UI lets users fund their embedded wallet by sending crypto from a self‑cus
 2. From an external wallet, send funds to that address on a supported network.
 3. Confirm the deposit and update balances in your app.
 
-## Fiat on Ramp Coverage
+## Fiat on-ramp coverage
 
 :::tip
 
-For the complete list of fiat, crypto and payment method coverage, please check [here](https://docs.google.com/spreadsheets/d/1HwIDgFQ-J-ptImT9yp6MmLpZId3l1NGe9qWJJN88msY/edit#gid=0)
+See a complete list of [fiat, crypto and payment method coverage](https://docs.google.com/spreadsheets/d/1HwIDgFQ-J-ptImT9yp6MmLpZId3l1NGe9qWJJN88msY/edit#gid=0)
 
 :::
 
-### Network Coverage
+### Network coverage
 
-The Onramp Aggregator is built to be chain-agnostic and supports a wide range of blockchain networks and tokens. Below is the list of main networks that we provide coverage.
+The chain-agnostic fiat on‑ramp aggregator supports a wide range of blockchain networks and tokens, including:
 
 ![Coverage](/img/embedded-wallets/wallet-services/topup/topup-coverage.png)
 

embedded-wallets/features/mpc.mdx

@@ -1,7 +1,7 @@
 ---
 title: Multi-Party Computation
 sidebar_label: Multi-Party Computation
-description: 'Multi-Party Computation | Documentation - MetaMask Embedded Wallets'
+description: 'Multi-Party Computation | MetaMask Embedded Wallets'
 ---
 
 import KeyManagementDark from '@site/static/img/embedded-wallets/flow-diagrams/key-management-dark.png'
@@ -11,23 +11,17 @@ Multi-Party Computation (MPC) powers MetaMask Embedded Wallets' non-custodial ke
 
 ## Understanding MPC in MetaMask Embedded Wallets
 
-MetaMask Embedded Wallets utilizes Threshold Cryptography, a principle of MPC, to ensure that a user can access their private key or generate transaction signatures only if they meet a specified threshold - typically 2 out of n key shares.
+MetaMask Embedded Wallets utilizes threshold cryptography, a principle of MPC, to ensure that a user can access their private key or generate transaction signatures only if they meet a specified threshold - typically 2 out of n key shares.
 
-:::note
+### Design goals
 
-This section is an overview of MPC in MetaMask Embedded Wallets. For an in-depth understanding, it might be helpful to read through [How Embedded Wallets Work](/embedded-wallets/how-it-works) and [Wallet Management and Security of our Infrastructure](/embedded-wallets/infrastructure/).
-
-:::
-
-### Design Goals
-
-- **Seamless User Experience:** MetaMask Embedded Wallets aims to provide a frictionless non-custodial wallet experience.
-- **Broad Compatibility:** Ensures integration with existing authentication methods and blockchain ecosystems.
-- **Global Performance & Scalability:** Designed to meet the expansive demands of the Web3 market efficiently.
+- **Seamless user experience:** MetaMask Embedded Wallets aims to provide a frictionless non-custodial wallet experience.
+- **Broad compatibility:** Ensures integration with existing authentication methods and blockchain ecosystems.
+- **Global performance & scalability:** Designed to meet the expansive demands of the Web3 market efficiently.
 
 ### 2-of-3 setup
 
-1. **OAuth login share:** Via the Web3Auth Network (e.g., Google).
+1. **Authentication share:** Derived from the user’s chosen login method (for example, social login such as Google).
 2. **Device share:** Stored on-device, protected by OS security/biometrics.
 3. **Backup/2FA share:** User-controlled recovery using a high-entropy secret.
 
@@ -48,6 +42,13 @@ This section is an overview of MPC in MetaMask Embedded Wallets. For an in-depth
 
 Both methods adhere to the core concept of threshold-based security but differ in their approach to wallet management and signature generation.
 
-## Wallet Management Infrastructure
+## Wallet management infrastructure
+
+The wallet management infrastructure distributes key shares so the full private key is never stored or exposed. The authentication share is generated by the Embedded Wallets Network using a 5/9 consensus, keeping wallets non-custodial. 
+
+## Next steps
+
+This section is an overview of MPC in MetaMask Embedded Wallets. For a more in-depth understanding, see:
 
-The Wallet Management Infrastructure distributes key shares so the full private key is never stored or exposed. The social-login share is generated by the Web3Auth Network using a 5/9 consensus, keeping wallets non-custodial. See the [Wallet Management Infrastructure](/embedded-wallets/infrastructure/) docs for details.
+- [How Embedded Wallets Work](/embedded-wallets/how-it-works)
+- [Wallet Management and Security of our Infrastructure](/embedded-wallets/infrastructure/)

embedded-wallets/features/nft-minting.mdx

@@ -5,37 +5,36 @@ description: 'NFT Minting | Embedded Wallets'
 sidebar_label: NFT Minting
 ---
 
-Web3Auth NFT Minting Service facilitates NFT airdrops and minting, giving you granular control over the process. The NFT Minting API is designed to facilitate the minting process for specified NFTs, supporting large-scale, gasless minting via our advanced batch minting infrastructure. This API is ideal for scenarios such as Airdrops, free mints, and situations where you prefer to manage fiat payments on your own.
+Embedded Wallets NFT Minting Service facilitates NFT airdrops and minting, giving you granular control over the process. The NFT Minting API is designed to facilitate the minting process for specified NFTs, supporting large-scale, gasless minting via our advanced batch minting infrastructure. This API is ideal for scenarios such as Airdrops, free mints, and situations where you prefer to manage fiat payments on your own.
 
 :::info
 
 Checkout our [Demo](https://demo.web3auth.io) to see it in action.
 
 :::
 
-## Key Features
+## Key features
 
-- **Control Over Fiat Payments:** Manage fiat payments independently to suit your project's needs.
-- **Custom Authorization Requirements:** Implement additional security measures, such as allowlisting addresses that are authorized to mint NFTs.
-- **Webhook Notifications:** Register webhook endpoints to receive real-time updates on transaction status.
-- **Gas Fees Covered:** Web3Auth handles all gas fees associated with the minting process, ensuring a cost-effective solution.
+- **Control over fiat payments:** Manage fiat payments independently to suit your project's needs.
+- **Custom authorization requirements:** Implement additional security measures, such as allowlisting addresses that are authorized to mint NFTs.
+- **Webhook notifications:** Register webhook endpoints to receive real-time updates on transaction status.
+- **Gas fees covered:** Embedded Wallets can handle all gas fees associated with the minting process, ensuring a cost-effective solution.
 
 ![NFT Minting](/img/nft-minting.svg)
 
 :::info
 
-The NFT Services support both Externally Owned Accounts (EOA) and Account Abstraction (AA) accounts powered by Web3Auth Native Account Abstraction.
+The NFT Services support both Externally Owned Accounts (EOA) and Account Abstraction (AA) accounts powered by Embedded Wallets' native account abstraction.
 
 Additionally, it supports both EVM and Solana accounts, providing a versatile solution for various blockchain environments.
 
 :::
 
 ## How it works
 
-To initiate the minting process, simply provide the API with the necessary contract details, token ID, and recipient wallet address. The Web3Auth infrastructure will take care of the rest, ensuring a seamless and efficient minting experience. Web3Auth supports ERC-721 and ERC-1155 smart contracts across all EVM-compatible networks.
+To initiate the minting process, provide the API with the necessary contract details, token ID, and recipient wallet address. The Embedded Wallets infrastructure will take care of the rest, ensuring a seamless and efficient minting experience. Web3Auth supports ERC-721 and ERC-1155 smart contracts across all EVM-compatible networks.
 
-:::tip Get Access to NFT Services
+## Next steps
 
-You can contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
+- Contact our [Business Team](https://calendly.com/elishamm/sales) for more information on how to access this feature.
 
-:::

embedded-wallets/features/server-side-verification.mdx

@@ -12,29 +12,27 @@ Server-side verification enables developers to securely authenticate users on th
 
 Upon a user's successful connection of their wallet, Web3Auth generates a `JWT`, signed with a private key using the `ES256` algorithm, that is unique to your application. This token serves as a verifiable credential that you can use to authenticate the user on your backend.
 
-## Implementing Server-Side Verification
+## Implementing server-side verification
 
-To implement server-side verification, follow these 3 simple steps:
+To implement server-side verification, follow these 3 steps:
 
-### 1. Retrieve the `JWT` (`idToken`)
+### Step 1. Retrieve the `JWT` (`idToken`)
 
 When a user logs in through Web3Auth, a `JWT` can be generated to prove that the user owns the wallet, and you can verify it on your backend server.
 
 **Different Flows for Different Wallets:**
 
-- **Social Logins**: These tokens include a public key linked to the user's wallet.
-- **External Wallets**: These tokens include the wallet address instead of the public key.
+- **Social logins**: These tokens include a public key linked to the user's wallet.
+- **External wallets**: These tokens include the wallet address instead of the public key.
 
-### 2. Verify the `JWT`
+### Step 2. Verify the `JWT`
 
 Use the public key/address provided to verify the `JWT`'s authenticity. This step confirms that the token is valid and the information it contains about the user can be trusted.
 
-### 3. Authenticate the User
+### Step 3. Authenticate the user
 
 Based on the verified claims within the `JWT`, including wallet address ownership, authenticate the user in your backend system.
 
-:::info
+## Next steps
 
-Head over to our [Identity Token](/embedded-wallets/authentication/id-token) documentation to learn more about the `JWT` and how to verify it.
-
-:::
+See the [Identity Token](/embedded-wallets/authentication/id-token) documentation to learn more about the `JWT` and how to verify it.

embedded-wallets/features/session-management.mdx

@@ -6,21 +6,21 @@ description: 'Session Management | Embedded Wallets'
 
 SDKs provide session management to minimize repeated logins, enhancing user experience by maintaining login state for a specified duration. This seamless experience offers several advantages, including:
 
-- **User Experience:** Reduces login frequency for a smoother experience.
+- **User experience:** Reduces login frequency for a smoother experience.
 - **Efficiency:** Session restoration is quick, occurring in milliseconds.
 - **Integration:** Easy to implement with minimal impact on user flow.
 
-### Session Key
+### Session key
 
 Upon login, a unique session key is generated. The user state is then encrypted with this session key and stored on the Web3Auth metadata server.
 
-### Secure Storage
+### Secure storage
 
-Session keys are stored securely in the client's environment (e.g., browser local storage, Android Encrypted Shared Preferences, iOS Keychain Services).
+Session keys are stored securely in the client's environment (for example, browser local storage, Android encrypted shared preferences, or iOS keychain services).
 
 ### Restoration
 
-1. **Retrieve Key:** SDK retrieves the session key from secure storage.
-2. **Server Communication:** SDK requests user state restoration from the metadata server.
+1. **Retrieve key:** SDK retrieves the session key from secure storage.
+2. **Server communication:** SDK requests user state restoration from the metadata server.
 3. **Decryption:** Encrypted user state is decrypted with the session key.
 4. **Fallback:** If no active session, user proceeds with standard login.