Merge pull request #356 from maticnetwork/deploy-readme-update

Update README.md in contract deployment

Author: ssandeep

deploy-migrations/README.md

@@ -45,18 +45,17 @@ We need to deploy our set of contracts on 2 chains:
 - Child Chain: EVM compatible chain to work as our sidechain. For testing note that using `ganache` for child-chain is not recommended, instead invoking `npm run bor:simulate` would be better.
 
 ```
-mv migrations dev-migrations && cp -r deploy-migrations migrations
 
 // Root contracts are deployed on base chain
-npm run truffle:migrate -- --reset --to 3 --network <base_chain_network_name>
+npm run truffle:migrate -- --reset --to 4 --network <base_chain_network_name>
 
 // Contracts like ChildERC20Token are deployed on child chain aka BOR chain
 // NOTE: You need to deploy or simulate BOR before running the below command
-npm run truffle:migrate -- --reset -f 4 --to 4 --network <child_chain_network_name>
+npm run truffle:migrate -- --reset -f 5 --to 5 --network <child_chain_network_name>
 
 
 // Contracts deployed on BOR are mapped to the registry contract deployed on-chain
-npm run truffle:migrate -- -f 5 --to 5 --network <base_chain_network_name>
+npm run truffle:migrate -- -f 6 --to 6 --network <base_chain_network_name>
 ```
 
 Post successfull deployment all contract addresses will be written to a `contractAddresses.json` file.