Improve documentation format

docs/examples/PREREQUISITES.md

@@ -24,7 +24,7 @@ secret "tls-secret" created
 You can act as your very own CA, or use an existing one. As an exercise / learning, we're going to generate our
 own CA, and also generate a client certificate.
 
-These instructions are based on CoreOS OpenSSL [instructions](https://coreos.com/kubernetes/docs/latest/openssl.html)
+These instructions are based on CoreOS OpenSSL. [See live doc.](https://coreos.com/kubernetes/docs/latest/openssl.html)
 
 ### Generating a CA
 
@@ -119,7 +119,7 @@ the TLS Auth directive:
 $ kubectl create secret generic caingress --namespace=default --from-file=ca.crt=<ca.crt>
 ```
 
-Note: You can also generate the CA Authentication Secret along with the TLS Secret by using:
+__Note:__ You can also generate the CA Authentication Secret along with the TLS Secret by using:
 ```console
 $ kubectl create secret generic caingress --namespace=default --from-file=ca.crt=<ca.crt> --from-file=tls.crt=<tls.crt> --from-file=tls.key=<tls.key>
 ```

docs/examples/docker-registry/README.md

@@ -10,9 +10,10 @@ First we deploy the docker registry in the cluster:
 kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/docker-registry/deployment.yaml
 ```
 
-**Important:** DO NOT RUN THIS IN PRODUCTION.
-This deployment uses `emptyDir` in the `volumeMount` which means the contents of the registry will be deleted when the pod dies.
+!!! Important
+	**DO NOT RUN THIS IN PRODUCTION**
 
+	This deployment uses `emptyDir` in the `volumeMount` which means the contents of the registry will be deleted when the pod dies.
 
 The next required step is creation of the ingress rules. To do this we have two options: with and without TLS
 
@@ -24,8 +25,10 @@ Download and edit the yaml deployment replacing `registry.<your domain>` with a
 wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/docker-registry/ingress-without-tls.yaml
 ```
 
-**Important:** running a docker registry without TLS requires we configure our local docker daemon with the insecure registry flag.
-Please check [deploy a plain http registry](https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
+!!! Important
+	Running a docker registry without TLS requires we configure our local docker daemon with the insecure registry flag.
+
+	Please check [deploy a plain http registry](https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
 
 ### With TLS
 

docs/examples/external-auth/README.md

@@ -5,7 +5,8 @@
 The `auth-url` and `auth-signin` annotations allow you to use an external
 authentication provider to protect your Ingress resources.
 
-(Note, this annotation requires `nginx-ingress-controller v0.9.0` or greater.)
+!!! Important
+	this annotation requires `nginx-ingress-controller v0.9.0` or greater.)
 
 ### Key Detail
 
@@ -41,7 +42,7 @@ into a Kubernetes cluster and use it to protect the Kubernetes Dashboard using g
 kubectl create -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/kubernetes-dashboard/v1.5.0.yaml
 ```
 
-2. Create a custom Github OAuth application https://github.com/settings/applications/new
+2. Create a [custom Github OAuth application](https://github.com/settings/applications/new)
 
 ![Register OAuth2 Application](images/register-oauth-app.png)
 

docs/examples/static-ip/README.md

@@ -79,9 +79,9 @@ NAME            HOSTS     ADDRESS           PORTS     AGE
 nginx-ingress   *         104.154.109.191   80, 443   13m
 ```
 
-Note that unlike the GCE Ingress, the same loadbalancer IP is shared amongst all
-Ingresses, because all requests are proxied through the same set of nginx
-controllers.
+> Note that unlike the GCE Ingress, the same loadbalancer IP is shared amongst all
+> Ingresses, because all requests are proxied through the same set of nginx
+> controllers.
 
 ## Promote ephemeral to static IP