apply changes

docs/devel/development.md

@@ -109,6 +109,7 @@ source control system).  Use ```apt-get install mercurial``` or ```yum install m
 directly from mercurial.
 
 2) Create a new GOPATH for your tools and install godep:
+
 ```
 export GOPATH=$HOME/go-tools
 mkdir -p $GOPATH
@@ -116,6 +117,7 @@ go get github.com/tools/godep
 ```
 
 3) Add $GOPATH/bin to your path. Typically you'd add this to your ~/.profile:
+
 ```
 export GOPATH=$HOME/go-tools
 export PATH=$PATH:$GOPATH/bin
@@ -125,6 +127,7 @@ export PATH=$PATH:$GOPATH/bin
 Here's a quick walkthrough of one way to use godeps to add or update a Kubernetes dependency into Godeps/_workspace. For more details, please see the instructions in [godep's documentation](https://github.com/tools/godep).
 
 1) Devote a directory to this endeavor:
+
 ```
 export KPATH=$HOME/code/kubernetes
 mkdir -p $KPATH/src/github.com/GoogleCloudPlatform/kubernetes
@@ -134,6 +137,7 @@ git clone https://path/to/your/fork .
 ```
 
 2) Set up your GOPATH.
+
 ```
 # Option A: this will let your builds see packages that exist elsewhere on your system.
 export GOPATH=$KPATH:$GOPATH
@@ -143,12 +147,14 @@ export GOPATH=$KPATH
 ```
 
 3) Populate your new GOPATH.
+
 ```
 cd $KPATH/src/github.com/GoogleCloudPlatform/kubernetes
 godep restore
 ```
 
 4) Next, you can either add a new dependency or update an existing one.
+
 ```
 # To add a new dependency, do:
 cd $KPATH/src/github.com/GoogleCloudPlatform/kubernetes
@@ -218,6 +224,7 @@ KUBE_COVER=y hack/test-go.sh
 At the end of the run, an the HTML report will be generated with the path printed to stdout.
 
 To run tests and collect coverage in only one package, pass its relative path under the `kubernetes` directory as an argument, for example:
+
 ```
 cd kubernetes
 KUBE_COVER=y hack/test-go.sh pkg/kubectl
@@ -230,6 +237,7 @@ Coverage results for the project can also be viewed on [Coveralls](https://cover
 ## Integration tests
 
 You need an [etcd](https://github.com/coreos/etcd/releases/tag/v2.0.0) in your path, please make sure it is installed and in your ``$PATH``.
+
 ```
 cd kubernetes
 hack/test-integration.sh
@@ -238,12 +246,14 @@ hack/test-integration.sh
 ## End-to-End tests
 
 You can run an end-to-end test which will bring up a master and two nodes, perform some tests, and then tear everything down. Make sure you have followed the getting started steps for your chosen cloud platform (which might involve changing the `KUBERNETES_PROVIDER` environment variable to something other than "gce".
+
 ```
 cd kubernetes
 hack/e2e-test.sh
 ```
 
 Pressing control-C should result in an orderly shutdown but if something goes wrong and you still have some VMs running you can force a cleanup with this command:
+
 ```
 go run hack/e2e.go --down
 ```
@@ -281,6 +291,7 @@ hack/ginkgo-e2e.sh --ginkgo.focus=Pods.*env
 ```
 
 ### Combining flags
+
 ```sh
 # Flags can be combined, and their actions will take place in this order:
 # -build, -push|-up|-pushup, -test|-tests=..., -down