diff --git a/doc/setup-masternodes.md b/doc/setup-masternodes.md
index 852bdfb8dbc..ccc7cf2ff72 100644
--- a/doc/setup-masternodes.md
+++ b/doc/setup-masternodes.md
@@ -2,7 +2,7 @@
 
 ## Introduction
 
-Setting up a masternode on Defichain allows you to participate in the consensus protocol and receive staking awards. One thing to note is that in order to set up a masternode, you must have a minimum of 1 million DFI tokens.
+Setting up a masternode on DefiChain allows you to participate in the consensus protocol and receive staking awards. One thing to note is that in order to set up a masternode, you must have a minimum of 1 million DFI tokens.
 
 > NOTE: This how-to expects some basic familiarity with the Linux terminal
 
@@ -57,7 +57,7 @@ into the file and hit `Ctrl-X` then enter to save the file.
 
 ### Step 4 - Setting up owner address with sufficient funds
 
-In order to run a masternode, you must own atleast 1 million DFI tokens. Let's set up an address with sufficient funds to use as an owner. Masternodes currently only support legacy addresses, so create a masternode address using:
+In order to run a masternode, you must own at least 1 million DFI tokens. Let's set up an address with sufficient funds to use as an owner. Masternodes currently only support legacy addresses, so create a masternode address using:
 
 ```
 ~/.defi/defi-cli getnewaddress "<label>" legacy
@@ -93,7 +93,7 @@ masternode_operator=OPERATOR_ADDRESS
 masternode_owner=OWNER_ADDRESS
 ```
 
-Because we have decided to run owner and operator on the same address, just substitue the same legacy address you created for `OPERATOR_ADDRESS` and `OWNER_ADDRESS`.
+Because we have decided to run owner and operator on the same address, just substitute the same legacy address you created for `OPERATOR_ADDRESS` and `OWNER_ADDRESS`.
 
 Now the final step is to restart the node. Since we have crontab running, we just have to kill the process and crontab will start it again for us after one minute. We can do this final step by running `killall defi-init`. One minute later, we should have our masternode running and minting coins.
 
@@ -170,5 +170,5 @@ Masternodes can exist in these states:
 - `ENABLED` - masternode is in fully operable state, can mint blocks and sign anchors
 - `PRE_RESIGNED` - masternode is still operable, but have received a 'resign' transaction and will wait for a special delay to get resigned
 - `RESIGNED` - masternode resigned, collateral unlocked and is available to be reclaimed
-- `PRE_BANNED` - masternode was caught as a 'criminal' (signing two blocks from parrallel forks on close heights and we got special proofing tx on chain) but still operable (waiting, as in the case of PRE_RESIGNED)
+- `PRE_BANNED` - masternode was caught as a 'criminal' (signing two blocks from parallel forks on close heights and we got special proofing tx on chain) but still operable (waiting, as in the case of PRE_RESIGNED)
 - `BANNED` - masternode deactivated, collateral unlocked and can be reclaimed (same as RESIGNED, but forced through deactivation)