fixed broken links and fixed some whats-nexts

Author: ManuGodzilla

src/content/docs/en/developers/guides/contract-deployment-tutorial.mdx

@@ -5,7 +5,7 @@ title: "Contract Deployment Tutorial"
 lang: "en"
 permalink: "developers/guides/contract-deployment-tutorial"
 excerpt: "The Scroll Sepolia Testnet allows the community to deploy smart contracts on Scroll. In this tutorial, we will teach you how to deploy a contract on Scroll Sepolia."
-whatsnext: { "Contract Deployment Tutorial": "/developers/developer-quickstart/" }
+whatsnext: { "Scroll Messenger Cross-chain Interaction": "/developers/guides/scroll-messenger-cross-chain-interaction/" }
 ---
 
 import Aside from "../../../../../components/Aside.astro"

src/content/docs/en/developers/guides/scroll-messenger-cross-chain-interaction.mdx

@@ -4,6 +4,7 @@ date: Last Modified
 title: "Scroll Messenger Cross-chain Interaction"
 lang: "en"
 permalink: "developers/guides/scroll-messenger-cross-chain-interaction"
+whatsnext: { "Bridge ERC20 through the Custom Gateway": "/developers/guides/bridge-erc20-through-the-custom-gateway" }
 excerpt: "In this example, we will launch a dummy smart contract on either Sepolia or Scroll Sepolia testnet and interact with it from the opposite chain."
 ---
 

src/content/docs/en/developers/scroll-contracts.mdx

@@ -4,6 +4,7 @@ date: Last Modified
 title: "Scroll Sepolia Contracts"
 lang: "en"
 permalink: "developers/scroll-contracts"
+whatsnext: { "Ethereum & Scroll Differences": "/developers/ethereum-and-scroll-differences" }
 excerpt: "The network info and contract addresses you need to start with Scroll Sepolia Testnet."
 ---
 

src/content/docs/en/technology/chain/transactions.mdx

@@ -62,15 +62,15 @@ First, users can directly submit transactions to L2 sequencers. To do so, users
 
 Second, deposit and enforced transactions are originated on L1. Scroll L1 bridge contract provides three entry points for users and smart contracts to send transactions from the L1. All messages sent through these three entry points will be appended to the `L1MessageQueue` contract.
 
-- The `ScrollGatewayRouter` contract and several standard token gateways allow users and contracts to deposit standard tokens to L2. See more details in the [Deposit Token Gateways](/-oscADc8SoKAOxjtpcEqKg).
-- The `L1ScrollMessenger` contract allows users and contracts to send arbitrary messages to L2. See more details in the [Sending Arbitrary Messages](/UPyw7afFQE6q-9CIdIRBag#Sending-Arbitrary-Messages).
-- The `EnforcedTxGateway` contract allows EOAs to initiate an enforced transaction from the same address to withdraw tokens or call other contracts on L2. See more details in the [Sending Enforced Transaction](/UPyw7afFQE6q-9CIdIRBag#Sending-Enforced-Transactions).
+- The `ScrollGatewayRouter` contract and several standard token gateways allow users and contracts to deposit standard tokens to L2. See more details in the [Deposit Token Gateways](/technology/bridge/deposit-gateways).
+- The `L1ScrollMessenger` contract allows users and contracts to send arbitrary messages to L2. See more details in the [Sending Arbitrary Messages](/technology/bridge/cross-domain-messaging#sending-arbitrary-messages).
+- The `EnforcedTxGateway` contract allows EOAs to initiate an enforced transaction from the same address to withdraw tokens or call other contracts on L2. See more details in the [Sending Enforced Transaction](/technology/bridge/cross-domain-messaging#sending-enforced-transactions).
 
 The Scroll sequencer periodically starts a new mining job. It pulls the L1 messages from the `L1MessageQueue` contract and transactions in the L2 mempool and seals a block. Once a transaction is included in a L2 block, its status becomes `Confirmed`.
 
 ### Commit Transaction Data
 
-The rollup node collects new L2 blocks and packs them into chunks and batches (see more details in [Transaction Batching](/RxRWLFtiQ7W_wbc0jMnQNA)). Periodically it sends a _Commit Transaction_ that posts the data of a batch of transactions to the L1 `ScrollChain` contract. After the Commit Transaction is finalized in a L1 block, the status of the transactions in this batch becomes `Committed`. At this time, users can reconstruct L2 state themselves completely based on the committed data from the L1 contract.
+The rollup node collects new L2 blocks and packs them into chunks and batches (see more details in [Transaction Batching](/technology/chain/transactions#transaction-batching)). Periodically it sends a _Commit Transaction_ that posts the data of a batch of transactions to the L1 `ScrollChain` contract. After the Commit Transaction is finalized in a L1 block, the status of the transactions in this batch becomes `Committed`. At this time, users can reconstruct L2 state themselves completely based on the committed data from the L1 contract.
 
 ### Finalize Transactions
 

src/content/docs/en/technology/zkevm/zkevm-overview.mdx

@@ -5,7 +5,6 @@ title: "zkEVM Overview"
 lang: "en"
 permalink: "technology/zkevm-overview"
 excerpt: "In order to understand how to build a zkEVM, which proves the execution of the EVM, we need to first look at the EVM itself."
-whatsnext: { "Bridge Overview": "/technology/bridge/bridge-overview" }
 ---
 
 import ClickToZoom from "../../../../../components/ClickToZoom.astro"

src/content/docs/en/user-guide/bridge.mdx

@@ -20,7 +20,7 @@ excerpt: "To start bridging assets from Sepolia, navigate to the portal bridge a
 {/* TODO: Update all instructions after being able to walk through the whole flow. */}
 
 Visit our [Bridge](https://scroll.io/bridge) app to get started![^thanks-hop] The Bridge supports both **Deposit** and **Withdraw** operations, allowing users to trustlessly move assets from Sepolia Testnet to Scroll Sepolia Testnet.
-[^thanks-hop]: Forked from [Hop Exchange]('https://hop.exchange/')'s UI 🙌
+[^thanks-hop]: Forked from [Hop Exchange](https://hop.exchange/)'s UI 🙌
 
 Deposits can take up to 15 minutes to be available on Scroll.