diff --git a/docs-main/integrations/wallets-and-exchanges/canton-network-overview.mdx b/docs-main/integrations/wallets-and-exchanges/canton-network-overview.mdx
index 3562313cb..ee1fc58f9 100644
--- a/docs-main/integrations/wallets-and-exchanges/canton-network-overview.mdx
+++ b/docs-main/integrations/wallets-and-exchanges/canton-network-overview.mdx
@@ -53,7 +53,7 @@ Parties are formatted as `name::fingerprint`. The party name or hint is freely c
 
 If you want to be able to derive your Party IDs from the public key, you can either use a static Party Name, and therefore derive the key from the fingerprint, or derive Party Name from the public key, too.
 
-To use a party, you must **onboard** it by submitting a topology transaction that authorizes a node to host it. The designated node must then submit a matching transaction to officially accept the hosting request. Instructions on how to do that can be found here.
+To use a party, you must **onboard** it by submitting a topology transaction that authorizes a node to host it. The designated node must then submit a matching transaction to officially accept the hosting request. See [Creating an External Party](/sdks-tools/sdks/wallet-sdk/guides/creating-an-external-party) for step-by-step instructions.
 
 #### Party Hosting