From e0e08884989d4abb00297b4a96a47eb6ea3d1a3b Mon Sep 17 00:00:00 2001
From: Yashovardhan Agrawal <21066442+yashovardhan@users.noreply.github.com>
Date: Mon, 14 Oct 2024 14:30:44 +0530
Subject: [PATCH] fix wrong algo mention

---
 docs/how-web3auth-works.mdx       | 2 +-
 src/pages/guides/mpc-core-kit.mdx | 2 +-
 src/pages/guides/tkey-js-mpc.mdx  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/how-web3auth-works.mdx b/docs/how-web3auth-works.mdx
index 042ed5114..5a6eb2b30 100644
--- a/docs/how-web3auth-works.mdx
+++ b/docs/how-web3auth-works.mdx
@@ -93,7 +93,7 @@ implementation of Web3Auth PnP and Core-Kit.
 With the Web3Auth infrastructure, your key is divided into multiple parts and stored across your
 devices and our Auth Network. This ensures that your key is always available and never stored in a
 single place. While in the traditional Web3Auth SDK, your key was dynamically reconstructed in the
-front end using threshold signatures.
+front end using shamir secret sharing.
 
 With the new Web3Auth MPC (Multi-Party Computation) architecture, it is **never reconstructed**.
 Instead, these partial keys are stored across different locations, and your device is used to make
diff --git a/src/pages/guides/mpc-core-kit.mdx b/src/pages/guides/mpc-core-kit.mdx
index 49507cdf4..dbab68593 100644
--- a/src/pages/guides/mpc-core-kit.mdx
+++ b/src/pages/guides/mpc-core-kit.mdx
@@ -46,7 +46,7 @@ npx degit Web3Auth/web3auth-core-kit-examples/mpc-core-kit-web/implicit-flow-exa
 With Web3Auth infrastructure, your key is divided into multiple parts and stored across your devices
 and our Auth Network. This ensures that your key is always available and never stored in a single
 place. While in the traditional Web3Auth SDK, your key was dynamically reconstructed in the frontend
-using threshold signatures, with the new Web3Auth MPC (Multi-Party Computation) architecture, it is
+using shamir secret sharing. With the new Web3Auth MPC (Multi-Party Computation) architecture, it is
 **never reconstructed**. Instead, these partial keys are stored across different locations, and your
 device is used to make partial signatures for your message/transaction. These are finally returned
 to the frontend where using TSS (Threshold Signature Scheme), these signatures are combined to make
diff --git a/src/pages/guides/tkey-js-mpc.mdx b/src/pages/guides/tkey-js-mpc.mdx
index f31df8a3b..093683c0e 100644
--- a/src/pages/guides/tkey-js-mpc.mdx
+++ b/src/pages/guides/tkey-js-mpc.mdx
@@ -49,7 +49,7 @@ used.
 With the Web3Auth infrastructure, your key is divided into multiple parts and stored across your
 devices and our Auth Network. This ensures that your key is always available and never stored in a
 single place. While in the traditional Web3Auth SDK, your key was dynamically reconstructed in the
-frontend using threshold signatures, with the new Web3Auth MPC (Multi Party Computation)
+frontend using shamir secret sharing. With the new Web3Auth MPC (Multi Party Computation)
 architecture, it is **never reconstructed**. Instead, these partial keys are stored across different
 locations, and your device is used to make partial signatures for your message/ transaction. These
 are finally returned to the frontend where using TSS (Threshold Signature Scheme), these signatures