apply changes

docs/getting-started-guides/docker-multinode/master.md

@@ -50,6 +50,7 @@ Docker containers themselves.  To achieve this, we need a separate "bootstrap" i
 ```--iptables=false``` so that it can only run containers with ```--net=host```.  That's sufficient to bootstrap our system.
 
 Run:
+
 ```sh
 sudo sh -c 'docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null &'
 ```
@@ -61,6 +62,7 @@ across reboots and failures.
 
 ### Startup etcd for flannel and the API server to use
 Run:
+
 ```
 sudo docker -H unix:///var/run/docker-bootstrap.sock run --net=host -d gcr.io/google_containers/etcd:2.0.12 /usr/local/bin/etcd --addr=127.0.0.1:4001 --bind-addr=0.0.0.0:4001 --data-dir=/var/etcd/data
 ```
@@ -97,6 +99,7 @@ or it may be something else.
 #### Run flannel
 
 Now run flanneld itself:
+
 ```sh
 sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0
 ```
@@ -104,6 +107,7 @@ sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privile
 The previous command should have printed a really long hash, copy this hash.
 
 Now get the subnet settings from flannel:
+
 ```
 sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from-above-here> cat /run/flannel/subnet.env
 ```
@@ -114,6 +118,7 @@ You now need to edit the docker configuration to activate new flags.  Again, thi
 This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
 
 Regardless, you need to add the following to the docker command line:
+
 ```sh
 --bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
 ```
@@ -136,6 +141,7 @@ sudo /etc/init.d/docker start
 ```
 
 it may be:
+
 ```sh
 systemctl start docker
 ```
@@ -148,6 +154,7 @@ sudo docker run --net=host -d -v /var/run/docker.sock:/var/run/docker.sock  gcr.
 ```
 
 ### Also run the service proxy
+
 ```sh
 sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v0.21.2 /hyperkube proxy --master=http://127.0.0.1:8080 --v=2
 ```
@@ -166,6 +173,7 @@ kubectl get nodes
 ```
 
 This should print:
+
 ```
 NAME        LABELS                             STATUS
 127.0.0.1   kubernetes.io/hostname=127.0.0.1   Ready

docs/getting-started-guides/docker-multinode/testing.md

@@ -39,6 +39,7 @@ kubectl get nodes
 ```
 
 That should show something like:
+
 ```
 NAME           LABELS                                 STATUS
 10.240.99.26   kubernetes.io/hostname=10.240.99.26    Ready
@@ -49,6 +50,7 @@ If the status of any node is ```Unknown``` or ```NotReady``` your cluster is bro
 [```#google-containers```](http://webchat.freenode.net/?channels=google-containers) for advice.
 
 ### Run an application
+
 ```sh
 kubectl -s http://localhost:8080 run nginx --image=nginx --port=80
 ```
@@ -56,17 +58,20 @@ kubectl -s http://localhost:8080 run nginx --image=nginx --port=80
 now run ```docker ps``` you should see nginx running.  You may need to wait a few minutes for the image to get pulled.
 
 ### Expose it as a service
+
 ```sh
 kubectl expose rc nginx --port=80
 ```
 
 This should print:
+
 ```
 NAME      LABELS    SELECTOR              IP          PORT(S)
 nginx     <none>    run=nginx             <ip-addr>   80/TCP
 ```
 
 Hit the webserver:
+
 ```sh
 curl <insert-ip-from-above-here>
 ```

docs/getting-started-guides/docker-multinode/worker.md

@@ -55,6 +55,7 @@ Please install Docker 1.6.2 or wait for Docker 1.7.1.
 As previously, we need a second instance of the Docker daemon running to bootstrap the flannel networking.
 
 Run:
+
 ```sh
 sudo sh -c 'docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null &'
 ```
@@ -83,6 +84,7 @@ or it may be something else.
 #### Run flannel
 
 Now run flanneld itself, this call is slightly different from the above, since we point it at the etcd instance on the master.
+
 ```sh
 sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0 /opt/bin/flanneld --etcd-endpoints=http://${MASTER_IP}:4001
 ```
@@ -90,6 +92,7 @@ sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privile
 The previous command should have printed a really long hash, copy this hash.
 
 Now get the subnet settings from flannel:
+
 ```
 sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from-above-here> cat /run/flannel/subnet.env
 ```
@@ -101,6 +104,7 @@ You now need to edit the docker configuration to activate new flags.  Again, thi
 This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
 
 Regardless, you need to add the following to the docker command line:
+
 ```sh
 --bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
 ```
@@ -123,6 +127,7 @@ sudo /etc/init.d/docker start
 ```
 
 it may be:
+
 ```sh
 systemctl start docker
 ```