fix build

docs/developers/omnichain/overview.md

@@ -80,8 +80,8 @@ connected chain.
 To call on omnichain contract the only thing a user has to do is send a
 transaction to a connected chain to ZetaChain's TSS address. The transaction
 `amount` becomes available to the sender on ZetaChain as
-[ZRC-20](/developers/omnichain/zrc-20) and the `data` byte array (containing an
-the omnichain contract `address` and `message`) is used to call the omnichain
+[ZRC-20](/developers/tokens/zrc20) and the `data` byte array (containing an the
+omnichain contract `address` and `message`) is used to call the omnichain
 contract by `address` and pass arguments from the `message`.
 
 Omnichain Smart Contracts are ideal for more complex applications where state

docs/developers/omnichain/tutorials/curve.md

@@ -7,7 +7,7 @@ sidebar_position: 7
 ## Overview
 
 Assuming you have familiarized yourself with
-[ZRC-20 Tokens](/developers/omnichain/zrc-20) and
+[ZRC-20 Tokens](/developers/tokens/zrc20) and
 [zEVM](/developers/omnichain/zeta-evm), this example walks through how you'd
 create an omnichain Curve pool! This means you can leverage the existing Curve
 contracts and orchestrate external, native assets as if they were all on one
@@ -47,4 +47,4 @@ function simply extracts params from the message, calls the Curve pool's
 logic remains in the core Curve contract deployment. Users can interact by
 depositing and calling this zEVM contract from an external chain. You can see
 how you'd call this for a user programmatically
-[here](/developers/omnichain/zrc-20/).
+[here](/developers/tokens/zrc20/).

docs/developers/omnichain/tutorials/swap.md

@@ -289,7 +289,7 @@ swapping native gETH from Goerli for tMATIC on Polygon Mumbai. The contract will
 deposit gETH to ZetaChain as ZRC-20, swap it for ZRC-20 tMATIC and then withdraw
 native tMATIC Polygon Mumbai. To get the value of the `--target-token` find the
 ZRC-20 contract address of the destination token in the
-[ZRC-20 section of the docs](/developers/omnichain/zrc-20).
+[ZRC-20 section of the docs](/developers/tokens/zrc20).
 
 ```
 npx hardhat interact --contract 0xf6CDd83AB44E4d947FE52c2637ee4A04F330328E --amount 0.01 --network goerli_testnet --target-token 0x48f80608B672DC30DC7e3dbBd0343c5F02C738Eb --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1
@@ -320,7 +320,7 @@ npx hardhat cctx 0x6b4156c195d955d1325a5e6275214db63ff2e3642838607333e74abd74b8f
 Now let's swap USDC from Goerli to MATIC on Polygon Mumbai. To send USDC specify
 the ERC-20 token contract address (on Goerli) in the `--token` parameter. You
 can find the address of the token in the
-[ZRC-20 section of the docs](/developers/omnichain/zrc-20).
+[ZRC-20 section of the docs](/developers/tokens/zrc20).
 
 ```
 npx hardhat interact --contract 0xf6CDd83AB44E4d947FE52c2637ee4A04F330328E --amount 10 --token 0x07865c6e87b9f70255377e024ace6630c1eaa37f --network goerli_testnet --target-token 0x48f80608B672DC30DC7e3dbBd0343c5F02C738Eb --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1

docs/developers/omnichain/zeta-evm.md

@@ -14,6 +14,6 @@ chain.
 
 ![zeta-evm](/img/graphs/omnichain-smart-contracts-orchestrate-graph.svg)
 
-Contracts on zEVM can be called via [ZRC-20](/developers/omnichain/zrc-20) from
+Contracts on zEVM can be called via [ZRC-20](/developers/tokens/zrc20) from
 external chains. To connect to zEVM directly, check out the network info
 [here](/reference/contracts).

docs/developers/overview.md

@@ -48,9 +48,9 @@ referred to as a Threshold Signature Scheme (TSS) address.
   contract, and the contract is called with the message data as an argument.
 
 Assets transferred to a TSS address on ZetaChain are represented as
-[ZRC-20](/developers/omnichain/zrc-20) tokens. ZRC-20 is an extension of ERC-20
-that supports additional functionality for deposits from and withdrawals to
-connected chains.
+[ZRC-20](/developers/tokens/zrc20) tokens. ZRC-20 is an extension of ERC-20 that
+supports additional functionality for deposits from and withdrawals to connected
+chains.
 
 The state of your whole dApp can be stored in this omnichain contract.
 

docs/reference/get-testnet-zeta.mdx

@@ -47,7 +47,7 @@ You will be prompted to authenticate with your GitHub account to use the faucet.
 
 Please note that using this faucet you can get only ZETA tokens on ZetaChain. If
 you want to transfer ZETA tokens between connected chain or to/from ZetaChain,
-use the built-in [`send-zeta`](/developers/tokens) command.
+use the built-in `send-zeta` command.
 
 If you need gas assets on connected chains (like Bitcoin, Goerli, Mumbai or BSC
 testnet), you can use the other faucets listed below.
@@ -77,8 +77,7 @@ ZETA balance.
 
 After receiving ZETA tokens on Goerli, you can either switch to another testnet
 network (like Mumbai or BSC testnet) to swap ZETA there, or use the built-in
-[`send-zeta`](/developers/tokens) command to transfer ZETA between connected
-networks.
+`send-zeta` command to transfer ZETA between connected networks.
 
 ### Using a Hardhat template
 

docusaurus.config.js

@@ -82,6 +82,10 @@ const config = {
             from: "/reference/mainnet/",
             to: "/reference/contracts",
           },
+          {
+            from: "/developers/omnichain/zrc-20",
+            to: "/developers/tokens/zrc20",
+          },
         ],
       },
     ],