Updating documents

Author: StanleyGoldman

docs/contributing/coding-conventions.md

@@ -1,6 +1,6 @@
-#Contributing to GitHub for Unity
+# Contributing to GitHub for Unity
 
-##Coding Conventions
+## Coding Conventions
 - PascalCase for all types regardless of visibility
 - PascalCase for public members and const members
 - camelCase for private members, parameters and variables

docs/contributing/how-to-build.md

@@ -1,9 +1,18 @@
 # Contributing to GitHub for Unity
 
-## How to Build
+## Build Requirements
+To build GitHub for Unity we recommend using Visual Studio 2015 or Mono 4.x and bash.
 
+## How to Build
+    
 ### Visual Studio
 
+To build with Visual Studio 2015 open the solution file `GitHub.Unity.sln`. Select `Build Solution` in the `Build` menu.
+
 ### Mono and Bash
 
+To build with Mono 4.x and Bash execute `build.sh` in a bash shell.
+
 ## Build Output
+
+Building the project creates an output folder named `github-unity-test` that is a sibling to the cloned repository. For instance, if the solution is located at `c:\Projects\Unity` the test output can be foud at `c:\Projects\github-unity-test`. The output folder contains a blank Unity project folder named `GitHubExtensionProject`. This folder is a blank Unity 5.5 project with GitHub for Unity installed.