Update setup-masternodes.md

doc/setup-masternodes.md

@@ -81,7 +81,7 @@ In order to participate in the staking algorithm, you must broadcast to the netw
 ~/.defi/defi-cli createmasternode address
 ```
 
-where `address` for both operator and collateral address should be the new legacy address you created.
+where `address` for both operator and collateral address should be the new legacy address you created. Please note that it costs 10 DFI to run this command.
 
 ### Step 6 - Configure the masternode and restart
 
@@ -120,7 +120,7 @@ In order to participate in the staking algorithm, you must broadcast to the netw
 ~/.defi/defi-cli createmasternode OWNER_ADDRESS OPERATOR_ADDRESS
 ``` 
 
-where `OWNER_ADDRESS` is the address for the collateral/owner node and `OPERATOR_ADDRESS` is the address for the operator.
+where `OWNER_ADDRESS` is the address for the collateral/owner node and `OPERATOR_ADDRESS` is the address for the operator. Please note that it costs 10 DFI to run this command.
 
 ### Step 6 - Configure the masternode and restart
 
@@ -171,4 +171,4 @@ Masternodes can exist in these states:
 - `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)
-- `BANNED` - masternode deactivated, collateral unlocked and can be reclaimed (same as RESIGNED, but forced through deactivation)
+- `BANNED` - masternode deactivated, collateral unlocked and can be reclaimed (same as RESIGNED, but forced through deactivation)