fix wrong algo mention

Author: yashovardhan

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

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

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