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 3bf8714d..9722f6d1 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
@@ -41,8 +41,6 @@ Initialize a new `deployment.json` file specifying the network:
 
 ## Deploy Your Solana Token
 
-Tokens used in Wormhole’s NTT can operate in burning mode or as hub chain tokens in hub-and-spoke mode. These modes differ in how tokens are managed and configured for cross-chain transfers.
-
 ???- interface "Deploy an SPL Token"
 
     1. Generate a new Solana key pair to create a wallet:
@@ -85,7 +83,6 @@ Tokens used in Wormhole’s NTT can operate in burning mode or as hub chain toke
     spl-token mint INSERT_TOKEN_ADDRESS 1000
     ```
 
-
 !!! note
     NTT versions `>=v2.0.0+solana` support SPL tokens with transfer hooks.
 
@@ -93,7 +90,7 @@ Tokens used in Wormhole’s NTT can operate in burning mode or as hub chain toke
 
 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.
 
-This means you can deploy your token using the standard SPL or Token2022 creation process without modifying its mint authority or adding custom functionality.
+For more detailed information about deployment models, see the [Deployment Models](/docs/learn/messaging/native-token-transfers/deployment/){target=\_blank} page.
 
 ### Burning Mode Requirements