add basic issue tempaltes. fix minor types and style issues

Author: maleck13

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,10 @@
+**This form is for bug reports and feature requests. Major features will go through a [proposal process](https://github.com/aerogear/mobile-cli/blob/master/CONTRIBUTING.adoc).**
+
+> # Feature:
+> # Bug:
+
+**What happened**:
+
+**What you expected to happen**:
+
+**How to reproduce it**:

CONTRIBUTING.adoc

@@ -1,4 +1,4 @@
-= Contributing to the mobile cli
+= Contributing to the mobile CLI
 
 This document explains how to set up a development environment and get involved with Mobile CLI project.
 
@@ -13,7 +13,7 @@ Before anything else, https://help.github.com/articles/fork-a-repo/[fork] the Mo
 == Set Up OpenShift
 
 The Mobile CLI targets Kubernetes and is intended to be developed against a running Kubernetes cluster,
-we use OpenShift as our Kuberentes distribution. The Mobile CLI is intended to help you work with Mobile Services running ontop of OpenShift.
+we use OpenShift as our Kubernetes distribution. The Mobile CLI is intended to help you work with Mobile Services running ontop of OpenShift.
 To provision these services, we levarage the https://github.com/kubernetes-incubator/service-catalog[Service Catalog] and the https://github.com/openshift/ansible-service-broker[Ansible Service Broker].
 To help get this infrastructure set up there is a https://github.com/aerogear/mobile-core#installing-from-a-development-release[ansible based installer] provided.
 
@@ -22,15 +22,15 @@ To help get this infrastructure set up there is a https://github.com/aerogear/mo
 As we are using Go, the path you clone this repo into is important.
 
 * create the directory `mkdir -p $GOPATH/src/github.com/aerogear`
-* clone the repo `cd $GOPATH/src/github.com/aerogear && git clone git@github.com:aerogear/mobile-cli.git`
+* clone the repo `cd $GOPATH/src/github.com/aerogear && git clone git@github.com:aerogear/mobile-CLI.git`
 * add your own fork as the upstream target `git add remote upstream <your fork>`
 
 == Building the Mobile CLI
 
-To build the cli locally you can run `make build` this command will run a set of checks and the unit tests before compiling the binary and outputting it into the current directory,
+To build the CLI locally you can run `make build` this command will run a set of checks and the unit tests before compiling the binary and outputting it into the current directory,
 if you only want to build the binary itself you can simply run `make build_binary`.
 Once built, you can access this binary and use it from the command line `./mobile`
-Remember however that the CLI is intended as a Kubernetes plugin so expects to kind kube configuration in `~/.kube/config`. If you have setup OpenShift this should
+Remember however that the CLI is intended as a Kubernetes plugin so expects to find kube configuration in `~/.kube/config`. If you have setup OpenShift this should
 already be in place.
 
 == Submitting changes to the Mobile CLI
@@ -39,9 +39,9 @@ already be in place.
 
 There are a few things you should keep in mind before creating a PR.
 
-* New code should have corresponding unit tests. An example of how we approach unit testing can be found in https://github.com/aerogear/mobile-cli/blob/master/pkg/cmd/clients_test.go[clients_test.go].
+* New code should have corresponding unit tests. An example of how we approach unit testing can be found in https://github.com/aerogear/mobile-CLI/blob/master/pkg/cmd/clients_test.go[clients_test.go].
 
-* Ensure for new commands to read the https://github.com/aerogear/mobile-cli/doc/adding_new_cmd.md[adding a new command] doc before hand.
+* Ensure for new commands to read the https://github.com/aerogear/mobile-CLI/doc/adding_new_cmd.md[adding a new command] doc before hand.
 
 * You Must run ```make build``` before creating the PR and ensure it must execute with no errors.
 
@@ -53,7 +53,7 @@ Make a https://help.github.com/articles/using-pull-requests[pull request (PR)] i
 
 Use [WIP] at the beginning of the title (ie. [WIP] Add feature to the CLI) to mark a PR as a Work in Progress.
 
-Your PR will then be reviewed, questions may be asked and changes asked for.
+Your PR will then be reviewed, questions may be asked and changes requested.
 
 Upon successful review, someone will approve the PR in the review thread. Depending on the size of the change, we may wait for 2 LGTM from reviewers before merging.
 
@@ -71,4 +71,4 @@ The proposal process also requires two approvals from the community before mergi
 == Stay in touch
 
 * IRC: Join the conversation on Freenode: #aerogear
-* Email: Subscribe to the https://github.com/aerogear/mobile-cli/doc/adding_new_cmd.md[aerogear mailing list]
+* Email: Subscribe to the https://github.com/aerogear/mobile-CLI/doc/adding_new_cmd.md[aerogear mailing list]

doc/adding_new_cmd.md

@@ -1,4 +1,4 @@
-# Adding a new cli command
+# Adding a new CLI command
 
 
 The mobile CLI uses the [cobra](https://github.com/spf13/cobra) library to provide a consistent framework for building out the CLI tool.
@@ -15,7 +15,7 @@ Once this is done, then you should follow the patterns in the other base command
 - Create a new type  ```<resourceName>Cmd```
 - Create new constructor ```New<resourceName>Cmd``` 
 - Dependencies such as the kubernetes clients should be passed to this constructor as their interface types to allow for simpler testing
-- The cobra commands should then be made methods from this the base type:
+- The cobra commands should then be returned from methods from this the base type. See below:
 
 ```
 type MyResourceCMD struct{}
@@ -30,7 +30,7 @@ If it is being added to an existing verb command then add this command in the sa
 
 If it is a new verb command then you will want to create a new block of it and its sub commands
 
-Eample of adding a new resource command:
+Example of adding a new resource command:
 
 ```
 var (