From a35eab1601c54042900cd546cf8f1e7385dcd3f0 Mon Sep 17 00:00:00 2001 From: Martin Hofmann Date: Fri, 20 Dec 2024 16:40:09 +0100 Subject: [PATCH] Update build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md Co-authored-by: Dawn Kelly <83190195+dawnkelly09@users.noreply.github.com> --- .../deployment-process/deploy-to-solana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md index ceb6e658..46512eb3 100644 --- a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md +++ b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md @@ -88,7 +88,7 @@ Initialize a new `deployment.json` file specifying the network: ### Hub Chain Requirements -For hub chain deployments on Solana, the token can be either an SPL or Token2022 token. No additional configuration, such as setting the mint authority, is required for hub chain tokens. +For hub chain deployments on Solana, the token can be either an SPL or Token2022. Hub chain tokens do not require additional configuration, such as setting the mint authority. For more detailed information, see the [Deployment Models](/docs/learn/messaging/native-token-transfers/deployment/){target=\_blank} page.