diff --git a/docs/smart-contracts/tokens/stellar-asset-contract.mdx b/docs/smart-contracts/tokens/stellar-asset-contract.mdx
index 518c10db5..a2512ed73 100644
--- a/docs/smart-contracts/tokens/stellar-asset-contract.mdx
+++ b/docs/smart-contracts/tokens/stellar-asset-contract.mdx
@@ -50,9 +50,9 @@ Some functionality available on the Stellar network in transaction operations, s
 
 Every Stellar asset on Stellar has reserved a contract address that the Stellar Asset Contract can be deployed to. Anyone can initiate the deploy and the Stellar asset issuer does not need to be involved.
 
-It can be deployed using the `InvokeHostFunctionOp` with `HOST_FUNCTION_TYPE_CREATE_CONTRACT` and `CONTRACT_ID_FROM_ASSET` specified [here](../../learn/smart-contract-internals/contract-interactions/stellar-transaction.mdx). The resulting token will have a deterministic identifier, which will be the sha256 hash of `HashIDPreimage::ENVELOPE_TYPE_CONTRACT_ID_FROM_ASSET` xdr specified [here][contract_id].
+It can be deployed using the [Soroban-CLI] as shown [here](../guides/cli/deploy-stellar-asset-contract.mdx).
 
-Or the [Soroban-CLI] can be used as showed [here](../guides/cli/deploy-stellar-asset-contract.mdx).
+Or the [Stellar SDK] can be used as shown [here](../../learn/smart-contract-internals/contract-interactions/stellar-transaction.mdx#xdr-usage) by calling `InvokeHostFunctionOp` with `HOST_FUNCTION_TYPE_CREATE_CONTRACT` and `CONTRACT_ID_FROM_ASSET`. The resulting token will have a deterministic identifier, which will be the sha256 hash of `HashIDPreimage::ENVELOPE_TYPE_CONTRACT_ID_FROM_ASSET` xdr specified [here][contract_id].
 
 Anyone can deploy the instances of Stellar Asset Contract. Note, that the initialization of the Stellar Asset Contracts happens automatically during the deployment. Asset Issuer will have the administrative permissions after the contract has been deployed.