diff --git a/contracts/gateway/INTEGRATION.md b/contracts/gateway/INTEGRATION.md
index bac46f8d..8fed122f 100644
--- a/contracts/gateway/INTEGRATION.md
+++ b/contracts/gateway/INTEGRATION.md
@@ -243,7 +243,7 @@ A multisig might be used for certain privileged roles in the smart contracts, e.
 
 For EVM chains, a custom [Multisig contract](../governance/Multisig.sol) is being used. However, another approach might make sense for other chain integrations. If the chain supports native multisig accounts, that might be preferrable. If it doesn't or it's capability is limited, we recommend using the preferred Multisig contract that's standard in the ecosystem (e.g. for EVM chains, [Safe](https://github.com/safe-global/safe-smart-account) is the most popular multisig). If this isn't available, then a custom contract needs to be written.
 
-For contracts that live on Axelar Amplifier itself, the Axelar governance can be the owner. For other privileged roles, the native multisig accounts on Axelar can be used if needed.
+For CosmWasm contracts that live on Axelar itself, the Axelar governance can be the owner. For other privileged roles, the [native multisig accounts](https://docs.cosmos.network/main/user/run-node/multisig-guide) on Axelar can be used if needed.
 
 Requirements:
 1. Supports a `k`-of-`n` signer set. `n` is not expected to be greater than 10.