fix all broken links + warnings

ZERO broken links

Author: shahbaz17

docs/connect-blockchain/connect-blockchain.mdx

@@ -15,7 +15,7 @@ blockchain. Providers take JSON-RPC requests and return the response. This is no
 submitting the request to an HTTP or IPC socket-based server. With Web3Auth, you get two types of
 providers, depending on the product you use:
 
-1. [Shamir Secret Sharing based Private Key Providers](#private-key-providers-pnp--sfa)
+1. [Shamir Secret Sharing based Private Key Providers](#for-web3auth-pnp-web-sdk)
 2. [Threshold Signature Scheme based MPC Providers](#mpc-core-kit-providers)
 
 ## Web3Auth is Chain Agnostic

docs/features/external-wallets.mdx

@@ -33,14 +33,3 @@ products, enhancing Web3Auth’s flexibility and reach.
 Using the `@web3auth/web3auth-wagmi-connector`, developers can incorporate Web3Auth into WAGMI’s
 React Hooks for Ethereum. This connector supports the Plug and Play Web SDKs of Web3Auth, enabling
 integration with products like RainbowKit, ConnectKit, and Web3Modal.
-
-:::tip
-
-You can follow this guide to integrate [Web3Auth Wagmi Connector](/sdk/pnp/web/wagmi-connector)
-within your dApp.
-
-For highly customised integrations, you can follow the source code of the
-[`@web3auth/web3auth-wagmi-connector`](https://github.com/Web3Auth/web3auth-wagmi-connector) to
-create your own Wagmi Connector.
-
-:::

docs/features/interoperability.mdx

@@ -8,11 +8,6 @@ description: "Interoperability | Documentation - Web3Auth"
 Web3Auth Wallet Services' interoperability feature is designed to provide users and developers with
 a fluid, cohesive blockchain experience. We offer interoperability via
 
-- **Ecosystem Wallets:** Build your own wallet ecosystem that dApps can seamlessly integrate with.
-  Users on any of dApps that integrate your wallet ecosystem will have a unified account. This
-  allows users to access and utilize their assets and NFTs across multiple dApps within your
-  ecosystem. To learn more, see [here](./ecosystem-wallets).
-
 - **WalletConnect Support:** Web3Auth enhances interoperability by integrating with WalletConnect.
   This integration enables users of Web3Auth to connect their wallets to a vast array of dApps such
   as NFT marketplaces, DeFi, etc.

docs/features/mpc.mdx

@@ -6,14 +6,14 @@ description: "Multi-Party Computation | Documentation - Web3Auth"
 
 import KeyManagementDark from "@site/static/images/key-management-dark.png";
 import KeyManagementLight from "@site/static/images/key-management-light.png";
-import { mpccorekitjs } from "@site/src/components/SDKReferenceCards";
+import { mpccorekit } from "@site/src/components/SDKReferenceCards";
 
 Multi-Party Computation (MPC) forms the backbone of Web3Auth's advanced wallet infrastructure,
 offering a secure and non-custodial way to manage digital assets. This document provides a
 high-level overview, with links to more in-depth technical documentation for those who wish to
 explore further.
 
-{mpccorekitjs}
+{mpccorekit}
 
 ## Understanding MPC in Web3Auth
 

docs/features/wallet-ui.mdx

@@ -20,7 +20,7 @@ However, you can use this feature for projects on `sapphire_devnet` for free.
 
 ## UI components
 
-- **Fiat On-Ramps:** Let users purchase crypto directly with localised on-ramps.
+- **Fiat On-Ramps:** Let users purchase crypto directly with localized on-ramps.
 
 - **Assets Display:** Show balances, tokens, NFTs, and other digital assets in a clean,
   user-friendly layout.
@@ -52,6 +52,6 @@ application.
 - [PnP iOS SDK](/sdk/mobile/pnp/ios/usage#launch-wallet-services)
 - [PnP React Native SDK](/sdk/mobile/pnp/react-native/usage#launching-wallet-services-ui)
 - [PnP Flutter SDK](/sdk/mobile/pnp/flutter/usage#launch-wallet-services)
-- [PnP Unity SDK](/sdk/pnp/unity/usage#launch-wallet-services)
+- [PnP Unity SDK](/sdk/gaming/unity/usage#launch-wallet-services)
 
 :::

docs/migration-guides/no-modal-v7-to-v8.mdx

@@ -117,8 +117,8 @@ introduced which can be used to define whether the network is testnet or not.
 :::note
 
 From v8, parameters apart from `chainId`, `rpcTarget`, and `chainNamespace` are now optional. Please
-note, while using [Wallet Services](/sdk/pnp/web/wallet-services) you have to also pass the optional
-parameters.
+note, while using [Wallet Services](/sdk/web/react/advanced/wallet-services) you have to also pass
+the optional parameters.
 
 :::
 

docs/migration-guides/sfa-android-v1.2.0-to-v2.0.0.mdx

@@ -15,7 +15,7 @@ In v2, we try to improve the developer experience by renaming the `SFAParams` to
 It has been renamed to align with naming conventions across Web3Auth SDKs. Along with this, there
 has been change in the positional parameter.
 
-[Checkout Web3AuthOptions for available parameters](/docs/sdk/sfa/sfa-android/initialize#parameters).
+[Checkout Web3AuthOptions for available parameters](/docs/sdk/mobile/sfa/android/initialize#parameters).
 
 ```kotlin
 // remove-start

docs/migration-guides/sfa-android-v2-to-v3.mdx

@@ -13,8 +13,8 @@ SDK. The guide outlines significant changes and enhancements.
 
 In v3, the `initialize` method will now return void upon successful initialization instead of
 returning `SessionData`. After successful initialization, you can use the
-[getSessionData](/docs/sdk/sfa/sfa-android/usage/#get-session-data) method to check if the user is
-logged in or not.
+[getSessionData](/docs/sdk/mobile/sfa/android/usage/#get-session-data) method to check if the user
+is logged in or not.
 
 ```kotlin
 val initializeCF = singleFactoreAuth.initialize(this.applicationContext)

docs/migration-guides/sfa-ios-v8-to-v9.mdx

@@ -32,7 +32,7 @@ renamed couple of constructor parameters.
 - `web3AuthClientId` is renamed to `clientId`.
 - `network` is renamed to `web3AuthNetwork`.
 
-[Checkout Web3AuthOptions for available parameters](/docs/sdk/sfa/sfa-ios/initialize#parameters).
+[Checkout Web3AuthOptions for available parameters](/docs/sdk/mobile/sfa/ios/initialize#parameters).
 
 ```swift
 // remove-start