fix typo + add warnings

Author: shahbaz17

docs/infrastructure/mpc-architecture.mdx

@@ -183,7 +183,7 @@ Signaures.
 
 The TSS signing requires information from two sections:
 
-- shared information (eg. public key, share commitments, theshold, unique identifiers)
+- shared information (eg. public key, share commitments, theeshold, unique identifiers)
 - local information (eg. TSS key share).
 
 The shared information is stored on metadata and replicated, whereas the local information is kept

docs/product-fit.mdx

@@ -46,11 +46,37 @@ your project requirements and find out which Web3Auth product is the best fit fo
 | **Out-of-box Authentication**    | ✅                                 | ❌                                             | ❌                                                            |
 | **Custom Auth Provider Support** | ✅                                 | ✅                                             | ✅                                                            |
 | **Bring your own Auth**          | ✅                                 | ✅                                             | ✅                                                            |
-| **Wallet management Algorithm**  | Shamir's Secret Sharing            | Shamir's Secret Sharing                        | Theshold Signature Scheme                                     |
-| **Import Private Key**           | ❌                                 | ❌                                             | ✅                                                            |
+| **Wallet management Algorithm**  | Shamir's Secret Sharing            | Shamir's Secret Sharing                        | Threshold Signature Scheme                                    |
+| **Import Private Key**           | ❌                                 | ❌                                             | ✅ \*                                                         |
 | **Export Private Key**           | ✅                                 | ✅                                             | ✅                                                            |
 | **External Wallet Support**      | ✅                                 | ❌                                             | ❌                                                            |
 
+<details>
+
+<summary>
+  <b>* Import Private Key in MPC Core Kit</b>
+</summary>
+
+<div>
+  We do not encourage the use of the import flow due to the associated security risks. As a
+  non-custodial solution leveraging MPC (Multi-Party Computation) for key generation, maintaining
+  the highest level of key security is a core principle. The import flow introduces uncertainty
+  regarding the origin and custody of the private key, potentially exposing it to unauthorized
+  access and undermining the security guarantees of our system.
+</div>
+
+<br />
+
+<div>
+  However, if the import private key flow is deemed essential for your dApp, it is crucial to ensure
+  thorough user education around the associated security risks. Users must be made aware that
+  importing a key— especially from an unknown or potentially compromised source—can expose them to
+  significant vulnerabilities, as it falls outside the secure key generation and management process
+  provided by our MPC-based, non-custodial architecture.
+</div>
+
+</details>
+
 ### Platform Support
 
 | Platform               | Plug and Play | Single Factor Auth | MPC Core Kit |