Update README.md

Author: devbugging

README.md

@@ -22,11 +22,10 @@
 You've come to the right place. We will help you develop your first Flow application.
 
 ### 🔨 Getting started
-Starting your project is very simple.
-
-1. Run flow setup command `flow setup`
-2. Run flow development command `flow dev`
-3. Start writing your contracts, we will take care of the rest
+Start your new project simply by following these steps:
+1. run flow setup command `flow setup`,
+2. run flow development command `flow dev` and make sure you have emulator running (`flow emulator`),
+3. start writing your contracts, the dev command will make sure everything gets deployed.
 
 ### 💿 Flow Setup
 Flow setup is the initial command you run to start your new Flow project.
@@ -38,15 +37,16 @@ The command will generate standard Flow proejct structure with the following res
 - **/contracts** all your contract source code goes in this folder, you can read more about Cadence contracts here.
 - **/scripts** all your scripts goes here, you can read more about Cadence scripts here.
 - **/transactions** all the transactions goes in this folder, you can read more about Cadence transactions here.
+- **/tests** all the integration tests for your dapp and Cadence tests go into this folder.
 - **flow.json** this is a configuration file for your project, but you don't need to worry about it, we will configure everything for you as you go.
 
 
 ### 📦 Flow Develop
-Flow develop command can be run after you created the project using the above flow setup command. You can run it like so:
+After creating the project using the flow setup command you should then start the emulator and run the development command in the newly created project directory like so:
 ```shell
 > flow dev
 ```
-Running this command will start up a local emulator, which behaves similar to the real Flow network so you can use it during testing. It will then automatically watch your project files and make sure to automatically sync all the contracts on the network.
+After the command is started it will automatically watch any changes you make to Cadence files and make sure to continiously sync those changes on the emulator network. If you make any mistakes it will report the errors as well.
 
 You should see something similar to:
 ```shell
@@ -72,12 +72,15 @@ create an account with that name and deploy the contract in that account.
   |- Moo contracts/Moo.cdc
 ```
 
-When you want to import the contract you just created you can simply do by writing the import statement:
+**Importing Contracts**
+When you want to import the contracts you've just created you can simply do so by writing the import statement:
 ```
 import Foo
 ```
-We will automatically find your contract named `Foo` and make sure it's deployed and imported ready to be used.
-If you want to deploy a contract to a specific account you can just create a folder inside the contracts folder and we will create the account for you which will have the same name as the folder you created. All the contracts inside this folder will be deployed automatically to that account.
+We will automatically find your project contract named `Foo` and handle the importing for you. 
+
+**Deploying to specific accounts**
+By default all contracts are deployed to a default account. If you want to seperate contracts to different accounts you can easily do so by creating a folder inside the contracts folder and we will create the account for you which will have the same name as the folder you just created. All the contracts inside that folder will be deployed automatically to the newly created account.
 
 Example deploying to charlie account:
 
@@ -104,7 +107,7 @@ flow exec sendToken
 The command will automatically search for that file in scripts and contracts and will execute it for you.
 
 
-### 🎉 Flow Migrate
+### 🎉 Flow Migrate WIP
 After you finish writing your project and you are ready to move on to testnet or mainnet we got you covered ther as well.
 
 You can easily migrate your just created project by running: