update Documentation

Documentation/EnvironmentVariables.md

@@ -1,7 +1,7 @@
 ## Environment Variables Setup
 
 
-### For clients targeting the ARM (V2) Azure API following environment variables need to be setup
+### For clients targeting the ARM (V2) Azure API that are generated using [AutoRest](https://github.com/Azure/autorest) should setup following environment variables:
 From an admin cmd console/terminal, at the root directory of your cloned repo, run the following for environment setup:
 * **Windows**
 ```

Documentation/RunTests.md

@@ -9,3 +9,5 @@
 
 * Running selective tests:
   Comment out the unrequired tests in azure-sdk-for-node/test/testlist.txt file by putting "# " at the beginning of line and run the tests by executing: ```npm test```
+
+* For running arm tests, execute `npm run unit-arm`

Documentation/SetupRepo.md

@@ -6,17 +6,17 @@ Setting up the Node SDK repo
 ```
 git clone git@github.com:your-github-username/azure-sdk-for-node.git
 cd azure-sdk-for-node
-git checkout dev
+git checkout master
 git remote add upstream git@github.com:Azure/azure-sdk-for-node.git
-git pull upstream dev
-git push origin dev (if there are any updates)
+git pull upstream master
+git push origin master (if there are any updates)
 
-Note: It is a best practice to create a separate branch for your feature from the dev branch. 
-In this way the dev branch in your fork can always be synced easily with upstream and is 
+Note: It is a best practice to create a separate branch for your feature from the master branch. 
+In this way the master branch in your fork can always be synced easily with upstream and is 
 not polluted with your current changes.
 
-git checkout -b mybranch 
-git push origin mybranch
+git checkout -b myFeatureBranch 
+git push origin myFeatureBranch
 ```
 
 * Installing the required npm modules from the root directory```npm install```