Documentation Updates:

examples/openshift-origin/.gitignore

+config/
+secret.json

examples/openshift-origin/README.md

@@ -84,7 +84,7 @@ Ensure you have a valid PUBLIC_IP address before continuing in the example.
 We now need to run a command on your host to generate a proper OpenShift configuration.  To do this, we will volume mount the configuration directory that holds your Kubernetes kubeconfig file from the prior step.
 
 ```shell
-docker run --privileged -v ${OPENSHIFT_CONFIG}:/config openshift/origin start master --write-config=/config --kubeconfig=/config/kubeconfig --master=https://localhost:8443 --public-master=https://${PUBLIC_IP}:8443
+docker run --privileged -v ${OPENSHIFT_CONFIG}:/config openshift/origin start master --write-config=/config --kubeconfig='/config/kubeconfig' --master='https://localhost:8443' --public-master='https://${PUBLIC_IP}:8443'
 ```
 
 You should now see a number of certificates minted in your configuration directory, as well as a master-config.yaml file that tells the OpenShift master how to execute.  In the next step, we will bundle this into a Kubernetes Secret that our OpenShift master pod will consume.
@@ -98,7 +98,7 @@ OpenShift includes an experimental command to make this easier.
 First, update the ownership for the files previously generated:
 
 ```
-$ sudo -E chown ${USER} -R ${OPENSHIFT_CONFIG}
+$ sudo -E chown -R ${USER} ${OPENSHIFT_CONFIG}
 ```
 
 Then run the following command to collapse them into a Kubernetes secret.

examples/redis/README.md

@@ -9,7 +9,7 @@ This example assumes that you have a Kubernetes cluster installed and running, a
 This is a somewhat long tutorial.  If you want to jump straight to the "do it now" commands, please see the [tl; dr](#tl-dr) at the end.
 
 ### Turning up an initial master/sentinel pod.
-is a [_Pod_](http://docs.k8s.io/pods.md).  A Pod is one or more containers that _must_ be scheduled onto the same host.  All containers in a pod share a network namespace, and may optionally share mounted volumes.
+What is a [_Pod_](http://docs.k8s.io/pods.md)?  A Pod is one or more containers that _must_ be scheduled onto the same host.  All containers in a pod share a network namespace, and may optionally share mounted volumes.
 
 We will used the shared network namespace to bootstrap our Redis cluster.  In particular, the very first sentinel needs to know how to find the master (subsequent sentinels just ask the first sentinel).  Because all containers in a Pod share a network namespace, the sentinel can simply look at ```$(hostname -i):6379```.