Updating contributing instructions. (#763)

Author: divolgin

CONTRIBUTING.md

@@ -10,36 +10,44 @@ Issues
 Pull Requests
 ------------------------
 
-Before submitting a pull request, please ensure you have enabled your fork on CircleCI, so that unit and acceptance tests can be run against the request.
+All pull requests must be made from forks enabled on CircleCI, so that unit and acceptance tests can be executed prior to code being merged.
 
 Build & Run the Project
 ------------------------
 
 ### Prerequisites
 
-Ensure you have (min versions to be added):
+The following tools must be installed before the project can be built.  The specified version are recommended.
 
-- `yarn`
-- `go`
-- `node`
+- `yarn` version 1.12
+- `node` version 8.11
+- `go` version 1.10
+- `dep` version 0.5 (https://github.com/golang/dep#installation)
 
 ### First time build
 
-The first time you build ship, you'll need to run the following
+Run the following commands before building ship for the first time:
 
 ```
-make build
+./hack/get_build_deps.sh
+make deps
 ```
 
-If you're planning to only work on "headless" mode, and don't need the UI built, you can just run
+To build ship executable, run
 
 ```
 make bin/ship
 ```
 
+To rebuild everything, including tests, run
+
+```
+make build
+```
+
 ### Running
 
-To run your locally-built copy of ship, use
+To run locally-built copy of ship, use
 
 ```
 ./bin/ship init <chart-path>
@@ -51,17 +59,9 @@ for example,
 ./bin/ship init github.com/helm/charts/stable/nginx-ingress
 ```
 
-### Iterating
-
-You can run
-
-```
-make build
-```
-
-to re-build the project.
+### Using the UI
 
-For iterating on the ui, you can start a webpack development server with
+A webpack development server can be started for iterating on the ui with the following command:
 
 ```
 make -C web serve_ship
@@ -70,16 +70,15 @@ make -C web serve_ship
 The go binary serves the UI on `localhost:8800`, the webpack dev server will serve on `localhost:8880`.
 
 ### A note on node modules
-On rare occasions, you may need to refresh your node modules. If `make build` gives you an error of the following flavor:
+On rare occasions, node modules may need to be refreshed. If `make build` results in an error of the following flavor:
 ```
 ...
 make[1]: *** [.state/build_ship] Error 2
 make: *** [build-ui] Error 2
-``` 
-and/or if `make -C web serve_ship` gives you a `Failed to compile` error, the following commands should get you back up and running. From the root of the project:
+```
+and/or if `make -C web serve_ship` gives results in a `Failed to compile` error, the following commands should get everything back up and running. From the root of the project:
 ```
 cd web
 rm -rf node_modules
 yarn
 ```
-