2483d embedded wallets pass (#2603)

* reviews infrastructure section

* reviews infrastructure section

* completes first pass of review, several items wip, see inline comments

* puts table differentiator into play

* rmvs partial from front matter

* fix for merge conflict

* completes review round

---------

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

Author: m4sterbunny

docusaurus.config.js

@@ -803,6 +803,14 @@ const config = {
         },
       },
     }),
+  stylesheets: [
+    {
+      href: "https://cdn.jsdelivr.net/npm/katex@0.16.25/dist/katex.min.css",
+      type: "text/css",
+      integrity: "sha384-WcoG4HRXMzYzfCgiyfrySxx90XSl2rxY5mnVY5TwtWE6KLrArNKn0T/mOgNL0Mmi",
+      crossorigin: "anonymous",
+    },
+  ],
 }
 
 module.exports = config

embedded-wallets/_partials/_sdk-key-model-table.mdx

@@ -0,0 +1,5 @@
+| SDK Family | Key Model | Available from |
+| ---------- | --------- | -------------- |
+| [**Embedded Wallet SDKs**](/embedded-wallets/sdk/) | [SSS](/embedded-wallets/infrastructure/sss-architecture) <br/>(key reconstruction) | [Base, Growth, and Scale plans](https://web3auth.io/pricing.html) |
+| **MPC Core Kit SDK** | [TSS/MPC](/embedded-wallets/infrastructure/mpc-architecture#threshold-signature-scheme-key) <br/> (no key reconstruction) | [Enterprise plan](https://web3auth.io/pricing.html) |
+

embedded-wallets/how-it-works.mdx

@@ -1,5 +1,5 @@
 ---
-title: How do Embedded Wallets work?
+title: How Embedded Wallets Work
 image: 'img/metamaskog.jpg'
 sidebar_label: How it works
 description: 'How MetaMask Embedded Wallets Work? | Documentation - Embedded Wallets'
@@ -12,7 +12,7 @@ MetaMask Embedded Wallets (formerly Web3Auth) operate as wallet infrastructure,
 
 ## High-level architecture
 
-The Embedded Wallet SDKs live solely on the user/application's front-end client and handle the interactions between OAuth providers and the Web3Auth Network.
+The Embedded Wallet SDKs live solely on the user/application's frontend client and handle the interactions between OAuth providers and the Embedded Wallet network.
 
 The diagram below describes the relationship between the SDKs and integrating applications. It also depicts the difference between the products that power the infrastructure for a developer-friendly integration.
 
@@ -28,15 +28,13 @@ The diagram below describes the relationship between the SDKs and integrating ap
 
 ## Wallet management infrastructure
 
-The [wallet management infrastructure](/embedded-wallets/infrastructure/) enhances security by distributing a user's wallet across various key shares, thereby avoiding direct exposure of seed phrases. These key shares form a 'web of trust' and enable wallet management akin to multi-factor account handling. Users employ OAuth logins, trusted devices, and other factors to manage their cryptographic key pairs. Importantly, the complete private keys are not stored anywhere within the Wallet Infrastructure system, including our databases or any participating nodes.
+The [wallet management infrastructure](./infrastructure/README.mdx) enhances security by distributing a user's wallet across various key shares, thereby avoiding direct exposure of seed phrases. These key shares form a 'web of trust' and enable wallet management akin to multi-factor account handling. Users employ OAuth logins, trusted devices, and other factors to manage their cryptographic key pairs. Importantly, the complete private keys are not stored anywhere within the wallet infrastructure system, including our databases or any participating nodes.
 
-To create a social login share, users interact with the Web3Auth Network, where key generation operates via a 5/9 consensus system. This setup guarantees that wallets remain non-custodial, ensuring that neither MetaMask, Social Login Providers, nor any other party holding a key share can claim full ownership.
+To create a social login share, users interact with the Embedded Wallets network, where key generation operates via a 5/9 consensus system. This setup guarantees that wallets remain non-custodial, ensuring that neither MetaMask, social login providers, nor any other party holding a key share can claim full ownership.
 
 :::tip managing wallets
 
-For managing wallets, our infrastructure uses various cryptographic techniques such as Shamir's Secret Sharing, Threshold Cryptography, and Multi Party Computation. 
-
-Learn more about [wallet management and the security of our infrastructure](/embedded-wallets/infrastructure/).
+For managing wallets, our infrastructure uses various cryptographic techniques such as [Shamir's Secret Sharing](./infrastructure/sss-architecture.mdx), threshold cryptography, and [Multi Party Computation (MPC)](./infrastructure/mpc-architecture.mdx). To learn more about how we manage wallets, please refer to our [Wallet Management and Security of our Infrastructure](./infrastructure/README.mdx).
 
 :::
 
@@ -46,9 +44,9 @@ MetaMask Embedded Wallets is not a wallet, but rather a wallet infrastructure th
 
 Unlike traditional wallets that can limit user experience, MetaMask Embedded Wallets enables developers to create tailored flows without requiring users to understand complex blockchain concepts. It provides a cryptographic key provider that can be used to build custom wallets or integrate with existing ones through Web3Auth's external wallet adapters.
 
-## Is it scalable?
+## Is MetaMask Embedded Wallets scalable?
 
-The infrastructure is built to handle millions of users. Our architecture provides:
+The MetaMask Embedded Wallets infrastructure is built to handle millions of users. Our architecture provides:
 
 - Global availability across multiple regions with consistent low-latency performance worldwide
 - Automatic horizontal scaling that adjusts capacity based on demand, eliminating bottlenecks and ensuring uninterrupted service