feat(docs): add i18n support with Chinese translations

docs/alt-vm-implementations/overview.mdx

@@ -14,7 +14,7 @@ While our public documentation currently focuses on EVM compatibility, we offer
 
 ### CosmosSDK
 
-The Hyperlane Cosmos SDK module, enables direct integration with Cosmos SDK-based blockchains. See [Hyperlane - Cosmos SDK Module](docs/alt-vm-implementations/cosmos-sdk).
+The Hyperlane Cosmos SDK module, enables direct integration with Cosmos SDK-based blockchains. See [Hyperlane - Cosmos SDK Module](/docs/alt-vm-implementations/cosmos-sdk).
 
 ### CosmWasm[​](#cosmwasm "Direct link to CosmWasm")
 

docs/guides/quickstart/deploy-warp-route.mdx

@@ -161,6 +161,6 @@ You can test in either direction between where you have the HWR set. However, if
 
 ## Learn More
 
-- Check out the [HWR](docs/applications/warp-routes/overview) reference page for more information on the interface and security implications of a HWR. The [interface](docs/applications/warp-routes/overview#interface) section covers calling `transferRemote` to transfer tokens to a specified recipient on a destination chain. Note that you'll have to prompt for a token approval prior to calling `transferRemote`.
+- Check out the [HWR](/docs/applications/warp-routes/overview) reference page for more information on the interface and security implications of a HWR. The [interface](/docs/applications/warp-routes/overview#interface) section covers calling `transferRemote` to transfer tokens to a specified recipient on a destination chain. Note that you'll have to prompt for a token approval prior to calling `transferRemote`.
 
 - A HWR is a type of [router](/docs/reference/developer-tools/libraries/router) application, a pattern enabling you to link multiple contracts across chains together.

docs/guides/warp-routes/evm/transfer-and-call-pattern.mdx

@@ -6,7 +6,7 @@ title: "Transfer and Call Pattern"
 
 The **Transfer and Call Pattern** enables a contract to both bridge assets via [Hyperlane Warp Route (HWR)](/docs/protocol/warp-routes/warp-routes-overview) and execute an action on the destination chain after the assets arrive. This pattern is useful for cases where an action depends on token balances after bridging.
 
-While HWR handle cross-chain token transfers, this pattern extends their capabilities by using [Interchain Accounts (ICA)](docs/applications/interchain-account) to execute arbitrary logic on the destination chain.
+While HWR handle cross-chain token transfers, this pattern extends their capabilities by using [Interchain Accounts (ICA)](/docs/applications/interchain-account) to execute arbitrary logic on the destination chain.
 
 ### Use Cases
 
@@ -67,7 +67,7 @@ flowchart TB
 ## How It Works
 
 1. Tokens are transferred from the sender to the contract.
-2. An [Interchain Account (ICA)](docs/applications/interchain-account) is derived for the contract on the destination chain.
+2. An [Interchain Account (ICA)](/docs/applications/interchain-account) is derived for the contract on the destination chain.
 3. The HWR transfer is initiated, sending the tokens crosschain to the interchain account.
 4. A remote contract call is executed on the destination chain from the interchain account after the tokens arrive.
 

docs/protocol/core/interchain-gas-payment.mdx

@@ -50,7 +50,7 @@ flowchart LR
     IGP -. "value" .- Relayer
 ```
 
-For convenience, a [Relayer](docs/operate/relayer/run-relayer) watches for dispatched messages and will submit process transactions on behalf of the message sender if they receive sufficient payment on the origin chain. This is the _interchain gas payment_.
+For convenience, a [Relayer](/docs/operate/relayer/run-relayer) watches for dispatched messages and will submit process transactions on behalf of the message sender if they receive sufficient payment on the origin chain. This is the _interchain gas payment_.
 
 ```mermaid
 flowchart LR
@@ -103,4 +103,4 @@ There are no trust assumptions with respect to Relayers in the Hyperlane protoco
 ## Learn More
 
 - For details on gas limit calculations, benchmarking recommendations, gas oracles, and destination gas configuration, refer to [Interchain Gas Payment Details](/docs/reference/hooks/interchain-gas).
-- For Relayer setups and implementation guidance, see the [Relayer](docs/operate/relayer/run-relayer) section.
+- For Relayer setups and implementation guidance, see the [Relayer](/docs/operate/relayer/run-relayer) section.

docs/resources/glossary.mdx

@@ -42,13 +42,13 @@ A [middleware](/docs/resources/glossary#middleware) smart contract that allows u
 
 For example, DAOs can use interchain accounts to own contracts on remote chains.
 
-See [Interchain Accounts](docs/applications/interchain-account) for more information.
+See [Interchain Accounts](/docs/applications/interchain-account) for more information.
 
 ## Interchain gas paymaster
 
 A smart contract deployed by a [Relayer](/docs/resources/glossary#relayer) that accepts payments on an origin chain for message delivery on destination chains.
 
-See [interchain gas payments](docs/protocol/core/interchain-gas-payment) for more information
+See [interchain gas payments](/docs/protocol/core/interchain-gas-payment) for more information
 
 ## Interchain queries (IQS)
 
@@ -64,7 +64,7 @@ ISMs are responsible for verifying that interchain messages being delivered on t
 
 ## Mailbox
 
-Arguably the most important Hyperlane smart contract, the [mailbox](docs/protocol/core/interchain-gas-payment) exposes an interface that developers can use to [send](/docs/reference/messaging/send) and [receive](/docs/reference/messaging/receive) interchain messages.
+Arguably the most important Hyperlane smart contract, the [mailbox](/docs/protocol/core/interchain-gas-payment) exposes an interface that developers can use to [send](/docs/reference/messaging/send) and [receive](/docs/reference/messaging/receive) interchain messages.
 
 ## Middleware[​](#middleware "Direct link to Middleware")