diff --git a/docs/dapps/standards/non-fungible-tokens.md b/docs/dapps/standards/non-fungible-tokens.md
index b508ba04..a1068458 100644
--- a/docs/dapps/standards/non-fungible-tokens.md
+++ b/docs/dapps/standards/non-fungible-tokens.md
@@ -73,7 +73,7 @@ Interface INFT {
 ### NFT Collection
 
 An NFT collection has its own metadata such as `name`, `description`
-and `image`. It also contain a set of NFTs. The
+and `image`. It also contains a set of NFTs. The
 [INFTCollection](https://github.com/alephium/alephium-web3/blob/master/packages/web3/std/nft_collection_interface.ral)
 interface defines methods to return URI for the NFT collection
 metadata and the total supply of the collection. It also defines
@@ -141,7 +141,7 @@ Interface INFTCollectionWithRoyalty extends INFTCollection {
 Official [wallets](/wallet) and explorer have native support for
 non-fungible tokens.
 
-Following is an example of displaying and transfering a NFT in the
+Following is an example of displaying and transferring a NFT in the
 `Imagine Collection` in the extension wallet:
 
 <img
diff --git a/docs/dapps/tutorials/deep-dive.md b/docs/dapps/tutorials/deep-dive.md
index ed48a78c..a13a1b45 100644
--- a/docs/dapps/tutorials/deep-dive.md
+++ b/docs/dapps/tutorials/deep-dive.md
@@ -272,7 +272,7 @@ the arguments for our `TokenFaucet` contract.
 With `issueTokenAmount` you can define how many tokens you want to
 issue, this is required if you want to create a token, otherwise no
 tokens will be created. You can also use `issueTokenTo` to send the
-issued token to an recipient.
+issued token to a recipient.
 
 
 Now, let's deploy!
@@ -444,7 +444,7 @@ async function withdraw() {
   //Connect our wallet, typically in a real application you would connect your web-extension or desktop wallet
   const wallet = new PrivateKeyWallet({privateKey: '672c8292041176c9056bb0dd1d91d34711ceed2493b5afc83f2012b27df2c559' })
 
-  //.deployments contains the info of our `TokenFaucet` deployement, as we need to now the contractId and address
+  //.deployments contains the info of our `TokenFaucet` deployment, as we need to know the contractId and address
   //This was auto-generated with the `cli deploy` of our `scripts/0_deploy_faucet.ts`
   const deployments = await Deployments.load(configuration, 'devnet')
 
@@ -458,7 +458,7 @@ async function withdraw() {
     const tokenAddress = deployed.contractInstance.address
 
     // Submit a transaction to use the transaction script
-    // It uses our `wallet` to sing the transaction.
+    // It uses our `wallet` to sign the transaction.
     await Withdraw.execute(wallet, {
       initialFields: { token: tokenId, amount: 1n },
       attoAlphAmount: DUST_AMOUNT
diff --git a/docs/full-node/full-node-more.md b/docs/full-node/full-node-more.md
index 6dc676e4..e30f5642 100644
--- a/docs/full-node/full-node-more.md
+++ b/docs/full-node/full-node-more.md
@@ -121,7 +121,7 @@ Here are the steps to prune the Alephium full node:
 
 1. Make sure the Alephium full node is stopped
 2. Download `alephium-tools-x.y.z.jar` from https://github.com/alephium/alephium/releases
-3. If you changed the default Alephium home directory, set the the `ALEPHIUM_HOME` environment variable
+3. If you changed the default Alephium home directory, set the `ALEPHIUM_HOME` environment variable
 4. Run the following command `java -cp alephium-tools-x.y.z.jar org.alephium.tools.PruneStorage` to start pruning
 5. Wait until the command finishes execution, the disk space should be reduced to around 20 GB
 6. Restart the Alephium full node