Remove colon from end of doc heading.

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

@@ -37,7 +37,7 @@ 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:
+### Expose it as a service
 ```sh
 kubectl expose rc nginx --port=80
 ```

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

@@ -26,7 +26,7 @@ For each worker node, there are three steps:
 ### Set up Flanneld on the worker node
 As before, the Flannel daemon is going to provide network connectivity.
 
-#### Set up a bootstrap docker:
+#### Set up a bootstrap docker
 As previously, we need a second instance of the Docker daemon running to bootstrap the flannel networking.
 
 Run:

docs/getting-started-guides/docker.md

@@ -88,7 +88,7 @@ kubectl -s http://localhost:8080 run-container 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:
+### Expose it as a service
 ```sh
 kubectl expose rc nginx --port=80
 ```

docs/getting-started-guides/rackspace.md

@@ -64,7 +64,7 @@ There is a specific `cluster/rackspace` directory with the scripts for the follo
 3. The master server and additional nodes will be created via the `nova` CLI. A `cloud-config.yaml` is generated and provided as user-data with the entire configuration for the systems.
 4. We then boot as many nodes as defined via `$NUM_MINIONS`.
 
-## Some notes:
+## Some notes
 - The scripts expect `eth2` to be the cloud network that the containers will communicate across.
 - A number of the items in `config-default.sh` are overridable via environment variables.
 - For older versions please either: