docs: fix broken anchor links

src/pages/docs/guide/issuance/create-a-stablecoin.mdx

@@ -43,7 +43,7 @@ Ensure that you have set up your project with Wagmi, a Tempo chain config, and a
 Before we send off a transaction to deploy our stablecoin to the Tempo testnet, we need to make sure our account is funded with a stablecoin to cover the transaction fee. 
 
 As we have configured our project to use `AlphaUSD` (`0x20c000…0001`) 
-as the [default fee token](/docs/quickstart/integrate-tempo#default-fee-token), we will need to add some `AlphaUSD` to our account.
+as the [default fee token](/docs/quickstart/evm-compatibility#consideration-1-setting-a-user-default-fee-token), we will need to add some `AlphaUSD` to our account.
 
 Luckily, the built-in Tempo testnet faucet supports funding accounts with `AlphaUSD`.
 

src/pages/docs/guide/issuance/manage-stablecoin.mdx

@@ -22,7 +22,7 @@ import { Cards, Card } from 'vocs'
 
 Configure your stablecoin's permissions, supply limits, and compliance policies after deployment. This guide covers granting roles to manage token operations, setting supply caps, configuring transfer policies, and controlling token transfers through pause/unpause functionality.
 
-TIP-20 tokens use a role-based access control system that allows you to delegate different administrative functions to different addresses. For detailed information about the role system, see the [TIP-20 specification](/docs/protocol/tip20/spec#role-based-access-control).
+TIP-20 tokens use a role-based access control system that allows you to delegate different administrative functions to different addresses. For detailed information about the role system, see the [TIP-20 specification](/docs/protocol/tip20/spec#tip-20-roles).
 
 ## Stablecoin management steps
 
@@ -638,7 +638,7 @@ Ensure pause and unpause roles are assigned to trusted addresses and that your t
 <Cards>
   <Card
     description="Learn about the role-based access control system and all available roles"
-    to="/docs/protocol/tip20/spec#role-based-access-control"
+    to="/docs/protocol/tip20/spec#tip-20-roles"
     icon="lucide:shield"
     title="Role-Based Access Control"
   />

src/pages/docs/guide/issuance/use-for-fees.mdx

@@ -311,7 +311,7 @@ Regularly check your token's fee pool reserves to ensure users can consistently
 
 Keep sufficient validator token reserves in your fee pool to handle expected transaction volume. Consider your user base size and typical transaction frequency when determining reserve levels.
 
-As fees accrue in your token, the pool will run low on validator tokens and need to be rebalanced. Use [`rebalanceSwap`](/docs/guide/stablecoin-dex/managing-fee-liquidity#rebalance-liquidity) to replenish validator token reserves when they become depleted.
+As fees accrue in your token, the pool will run low on validator tokens and need to be rebalanced. Use [`rebalanceSwap`](/docs/guide/stablecoin-dex/managing-fee-liquidity#rebalance-pools) to replenish validator token reserves when they become depleted.
 
 ### Test before launch
 

src/pages/docs/guide/stablecoin-dex/providing-liquidity.mdx

@@ -198,7 +198,7 @@ For more details on querying orders, see the [`Hooks.dex.useOrder`](https://wagm
 
 Cancel an order using its order ID.
 
-When you cancel an order, any remaining funds are credited to your exchange balance (not directly to your wallet). To move funds back to your wallet, you can [withdraw them to your wallet](/docs/protocol/exchange/exchange-balance#withdrawing-funds).
+When you cancel an order, any remaining funds are credited to your exchange balance (not directly to your wallet). To move funds back to your wallet, you can [withdraw them to your wallet](/docs/protocol/exchange/exchange-balance#withdrawing-from-the-dex).
 
 <Demo.Container name="Place and Cancel an Order" footerVariant="source" src="tempoxyz/examples/tree/main/examples/exchange">
   <Connect stepNumber={1} />

src/pages/docs/protocol/tip20/overview.mdx

@@ -98,13 +98,13 @@ Tempo has dedicated payment lanes: reserved blockspace for payment TIP-20 transa
 
 ### Role-Based Access Control (RBAC)
 
-TIP-20 includes a built-in [RBAC system](/docs/protocol/tip403/spec#tip-20-token-roles) that separates administrative responsibilities:
+TIP-20 includes a built-in [RBAC system](/docs/protocol/tip20/spec#tip-20-roles) that separates administrative responsibilities:
 
 - **ISSUER_ROLE**: Grants permission to mint and burn tokens, enabling controlled token issuance
 - **PAUSE_ROLE** / **UNPAUSE_ROLE**: Allows pausing and unpausing token transfers for emergency controls
 - **BURN_BLOCKED_ROLE**: Permits burning tokens from blocked addresses (e.g., for compliance actions)
 
-Roles can be granted, revoked, and delegated without custom contract changes. This enables issuers to separate operational roles (e.g., who can mint) from administrative roles (e.g., who can pause). Learn more in the [TIP-20 specification](/docs/protocol/tip20/spec#roles).
+Roles can be granted, revoked, and delegated without custom contract changes. This enables issuers to separate operational roles (e.g., who can mint) from administrative roles (e.g., who can pause). Learn more in the [TIP-20 specification](/docs/protocol/tip20/spec#tip-20-roles).
 
 ### Tempo Policy Registry (TIP-403)
 

src/pages/docs/protocol/tips/tip-1007.mdx

@@ -50,7 +50,7 @@ interface IFeeManager {
 
 ### Fee Token Resolution
 
-The fee token returned by `getFeeToken()` is the same token that was resolved by the protocol during transaction validation, following the [fee token preference rules](/docs/protocol/fees/spec-fee#fee-token-resolution).
+The fee token returned by `getFeeToken()` is the same token that was resolved by the protocol during transaction validation, following the [fee token preference rules](/docs/protocol/fees/spec-fee#fee-token-preferences).
 
 ### Storage
 

src/pages/docs/quickstart/connection-details.mdx

@@ -19,7 +19,7 @@ Click on your browser wallet below to automatically connect it to the Tempo netw
 <ConnectWallet network="mainnet" />
 
 :::warning
-Note that on some wallets, you might see an unusually high "balance". This is because, historically, blockchain wallets have always assumed that a blockchain has a "native gas token". On Tempo, there is no native gas token, and so the value shown is a placeholder. See [EVM Differences](/docs/quickstart/evm-compatibility#handling-eth-balance-checks) for more information on this quirk.
+Note that on some wallets, you might see an unusually high "balance". This is because, historically, blockchain wallets have always assumed that a blockchain has a "native gas token". On Tempo, there is no native gas token, and so the value shown is a placeholder. See [EVM Differences](/docs/quickstart/evm-compatibility#handling-eth-native-token-balance-checks) for more information on this quirk.
 :::
 
 ## Connect via CLI

src/pages/docs/quickstart/developer-tools.mdx

@@ -98,7 +98,7 @@ Get started with the [Squid docs](https://docs.squidrouter.com/) or try the [bri
 
 [TIDX](/docs/api/indexer-api) is Tempo's hosted indexer for querying blocks, transactions, logs, token balances, and decoded events through SQL. Use the public mainnet endpoint at `https://indexer.tempo.xyz` or the testnet endpoint at `https://indexer.testnet.tempo.xyz`.
 
-The hosted indexer powers explorer-style reads and supports ClickHouse-backed analytical queries for expensive reads like holder lists and token activity. Try the [interactive TIDX example](/docs/api/indexer-api#interactive-tidx-sql-example) or read the [TIDX README](https://github.com/tempoxyz/tidx) to run your own indexer.
+The hosted indexer powers explorer-style reads and supports ClickHouse-backed analytical queries for expensive reads like holder lists and token activity. Try the [interactive TIDX example](/docs/api/indexer-api#interactive-example) or read the [TIDX README](https://github.com/tempoxyz/tidx) to run your own indexer.
 
 ### Allium
 

src/pages/docs/quickstart/evm-compatibility.mdx

@@ -90,7 +90,7 @@ If the user is calling a contract that is not a TIP-20 token, the EVM transactio
 
 On the Tempo Testnet, pathUSD is available from the [faucet](/docs/quickstart/faucet).
 
-If a wallet wants to submit a non-TIP20 transaction without having to submit the above transaction, we recommend investing in using [Tempo Transactions](/docs/quickstart/integrate-tempo#tempo-transactions) instead.
+If a wallet wants to submit a non-TIP20 transaction without having to submit the above transaction, we recommend investing in using [Tempo Transactions](/docs/guide/tempo-transaction) instead.
 
 ## VM Layer Differences