fix: broken links

content/tutorials/cross-chain-governance/30.cross-chain-transactions.md

@@ -69,7 +69,6 @@ Now, let's call the `increment` method on Layer 2 from Layer 1.
 
     - GOVERNANCE-ADDRESS: the address of the contract deployed in L1.
     - COUNTER-ADDRESS: the address of the contract deployed in L2.
-    - WALLET-PRIVATE-KEY: the private key of your account.
     - RPC-URL: the same url you used in the `.env` file of the `L1-governance` folder.
 
     ```ts [L2-counter/scripts/increment-counter.ts]
@@ -214,6 +213,6 @@ Now, let's call the `increment` method on Layer 2 from Layer 1.
 - To learn more about L1->L2 interaction on ZKsync, check out the
   [documentation](https://docs.zksync.io/build/developer-reference/l1-l2-interoperability).
 - To learn more about the `zksync-ethers` SDK, check out its
-  [documentation](https://docs.zksync.io/sdk/ethers/v6/getting-started).
+  [documentation](https://docs.zksync.io/sdk/js/ethers).
 - To learn more about the ZKsync hardhat plugins, check out their
   [documentation](https://docs.zksync.io/build/tooling/hardhat/getting-started).

content/tutorials/daily-spend-limit-account/10.index.md

@@ -19,7 +19,7 @@ The daily limit feature prevents an account from spending more ETH than the limi
   contracts. You can get Sepolia ETH from the [network faucets](https://docs.zksync.io/ecosystem/network-faucets).
   - Get testnet `ETH` for ZKsync Era using [bridges](https://zksync.io/explore#bridges) to bridge funds to ZKsync.
 - You know how to get your [private key from your MetaMask wallet](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key).
-- We encourage you to read [the basics of account abstraction on ZKsync Era](https://docs.zksync.io/build/developer-reference/account-abstraction/introduction)
+- We encourage you to read [the basics of account abstraction on ZKsync Era](https://docs.zksync.io/build/developer-reference/account-abstraction/)
   and complete the [multisig account tutorial](/tutorials/native-aa-multisig) before attempting this tutorial.
 
 :display-partial{path="/_partials/_callout-zksync-cli"}
@@ -1118,7 +1118,7 @@ Let's test the `SpendLimit` contract works to make it refuse ETH transfers that
 - To learn more about L1->L2 interaction on ZKsync, check out the
   [documentation](https://docs.zksync.io/build/developer-reference/l1-l2-interoperability).
 - To learn more about the `zksync-ethers` SDK, check out its
-  [documentation](https://docs.zksync.io/sdk/ethers/v6/getting-started).
+  [documentation](https://docs.zksync.io/sdk/js/ethers).
 - To learn more about the ZKsync hardhat plugins, check out their
   [documentation](https://docs.zksync.io/build/tooling/hardhat/getting-started).
 

content/tutorials/erc20-paymaster/10.index.md

@@ -578,6 +578,6 @@ As a workaround, try including a specific `gasLimit` value in the transaction.
 - To learn more about L1->L2 interaction on ZKsync, check out the
   [documentation](https://docs.zksync.io/build/developer-reference/l1-l2-interoperability).
 - To learn more about the `zksync-ethers` SDK, check out its
-  [documentation](https://docs.zksync.io/sdk/ethers/v6/getting-started).
+  [documentation](https://docs.zksync.io/sdk/js/ethers).
 - To learn more about the ZKsync hardhat plugins, check out their
   [documentation](https://docs.zksync.io/build/tooling/hardhat/getting-started).

content/tutorials/frontend-paymaster/10.index.md

@@ -541,9 +541,9 @@ Now you should be able to update the greeting message with ETH or any of the ava
 ## Next steps
 
 - For an overview of security and best practices for developing on ZKsync Era,
-  refer to the [Security and best practices page](https://docs.zksync.io/build/developer-reference/.best-practices).
+  refer to the [Security and best practices page](https://docs.zksync.io/build/developer-reference/best-practices).
 - To learn more about the `zksync-ethers` SDK, check out its
-  [documentation](https://docs.zksync.io/sdk/ethers/v6/getting-started).
+  [documentation](https://docs.zksync.io/sdk/js/ethers).
 - To learn more about the ZKsync hardhat plugins, check out their
   [documentation](https://docs.zksync.io/build/tooling/hardhat/getting-started).
 - If you have a project, check out our [migration guide](https://docs.zksync.io/build/tooling/hardhat/migrating-to-zksync).

content/tutorials/guide-viem/10.index.md

@@ -6,7 +6,7 @@ description: Learn how to use the viem/zksync plugin to interact with ZKsync.
 [viem](https://viem.sh/) is a TypeScript interface for Ethereum that now includes support for ZKsync,
 offering low-level stateless primitives for interacting with both Ethereum and ZKsync.
 You can use viem to interact seamlessly with smart contracts deployed on ZKsync.
-For more information on ZKsync specific support please refer to viem documentation [here](https://viem.sh/docs/chains/zksync).
+For more information on ZKsync specific support please refer to viem documentation [here](https://viem.sh/zksync).
 
 You can use viem to interact with smart contracts deployed on ZKsync.
 

content/tutorials/guide-walletconnect/10.index.md

@@ -36,7 +36,7 @@ You can find more details about the installation in the [WalletConnect documenta
 You can start Web3Modal configuration using either **default** or **custom** mode.
 
 Default mode will implement WalletConnect, Browser Wallets (injected),
-[Wagmi's public provider](https://wagmi.sh/react/providers/public) and [WalletConnect's provider](https://docs.walletconnect.com/cloud/blockchain-api).
+[Wagmi's public provider](https://wagmi.sh/core/getting-started) and [WalletConnect's provider](https://docs.walletconnect.com/cloud/blockchain-api).
 
 Start by importing `createWeb3Modal`, `defaultWagmiConfig` and wagmi packages,
 then create `wagmiConfig` using `defaultWagmiConfig` function as shown below.

content/tutorials/native-aa-multisig/10.index.md

@@ -964,8 +964,8 @@ export default async function (hre: HardhatRuntimeEnvironment) {
 
 ::callout{icon="i-heroicons-light-bulb"}
 ZKsync has different address derivation rules from Ethereum.
-Always use the [`createAddress`](https://docs.zksync.io/sdk/ethers/v6/utils#createaddress)
-and [`create2Address`](https://docs.zksync.io/sdk/ethers/v6/utils#create2address) utility functions of the `zksync-ethers` SDK.
+Always use the [`createAddress`](https://docs.zksync.io/sdk/js/ethers/api/v6/utilities/utils#createaddress)
+and [`create2Address`](https://docs.zksync.io/sdk/js/ethers/api/v6/utilities/utils#create2address) utility functions of the `zksync-ethers` SDK.
 
 Read the documentation for more information on [address derivation differences between Ethereum and ZKsync](https://docs.zksync.io/build/developer-reference/ethereum-differences/evm-instructions#address-derivation).
 ::
@@ -1206,6 +1206,6 @@ so it has enough funds to pay for the transaction fees.
 - To learn more about L1->L2 interaction on ZKsync, check out the
   [documentation](https://docs.zksync.io/build/developer-reference/l1-l2-interoperability).
 - To learn more about the `zksync-ethers` SDK, check out its
-  [documentation](https://docs.zksync.io/sdk/ethers/v6/getting-started).
+  [documentation](https://docs.zksync.io/sdk/js/ethers).
 - To learn more about the ZKsync hardhat plugins, check out their
   [documentation](https://docs.zksync.io/build/tooling/hardhat/getting-started).