From f250833d69ca3aee7147146f4305ff6e8e58f400 Mon Sep 17 00:00:00 2001
From: Frank <32797520+Frank1016@users.noreply.github.com>
Date: Fri, 8 Mar 2024 11:35:47 -0500
Subject: [PATCH] Update 2-define-a-token.md (#1796)

update terminal command based on current Near CLI version
---
 docs/3.tutorials/fts/2-define-a-token.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/3.tutorials/fts/2-define-a-token.md b/docs/3.tutorials/fts/2-define-a-token.md
index 5bb140c505f..043e97d6228 100644
--- a/docs/3.tutorials/fts/2-define-a-token.md
+++ b/docs/3.tutorials/fts/2-define-a-token.md
@@ -106,7 +106,7 @@ Verify that the correct account ID is printed in the terminal. If everything loo
 In the root of your FT project run the following command to deploy your smart contract.
 
 ```bash
-near deploy --wasmFile out/contract.wasm --accountId $FT_CONTRACT_ID
+near deploy $FT_CONTRACT_ID out/contract.wasm
 ```
 
 At this point, the contract should have been deployed to your account and you're ready to move onto creating your personalized fungible token.