Replace `` with when emphasizing something inline in docs/

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

@@ -33,10 +33,10 @@ Documentation for other releases can be found at
 
 ## Installing a Kubernetes Master Node via Docker
 
-We'll begin by setting up the master node.  For the purposes of illustration, we'll assume that the IP of this machine is ```${MASTER_IP}```
+We'll begin by setting up the master node.  For the purposes of illustration, we'll assume that the IP of this machine is `${MASTER_IP}`
 
 There are two main phases to installing the master:
-   * [Setting up ```flanneld``` and ```etcd```](#setting-up-flanneld-and-etcd)
+   * [Setting up `flanneld` and `etcd`](#setting-up-flanneld-and-etcd)
    * [Starting the Kubernetes master components](#starting-the-kubernetes-master)
 
 
@@ -48,9 +48,9 @@ Please install Docker 1.6.2 or wait for Docker 1.7.1.
 
 ### Setup Docker-Bootstrap
 
-We're going to use ```flannel``` to set up networking between Docker daemons.  Flannel itself (and etcd on which it relies) will run inside of
+We're going to use `flannel` to set up networking between Docker daemons.  Flannel itself (and etcd on which it relies) will run inside of
 Docker containers themselves.  To achieve this, we need a separate "bootstrap" instance of the Docker daemon.  This daemon will be started with
-```--iptables=false``` so that it can only run containers with ```--net=host```.  That's sufficient to bootstrap our system.
+`--iptables=false` so that it can only run containers with `--net=host`.  That's sufficient to bootstrap our system.
 
 Run:
 
@@ -122,7 +122,7 @@ sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from
 
 You now need to edit the docker configuration to activate new flags.  Again, this is system specific.
 
-This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
+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:
 
@@ -132,14 +132,14 @@ Regardless, you need to add the following to the docker command line:
 
 #### Remove the existing Docker bridge
 
-Docker creates a bridge named ```docker0``` by default.  You need to remove this:
+Docker creates a bridge named `docker0` by default.  You need to remove this:
 
 ```sh
 sudo /sbin/ifconfig docker0 down
 sudo brctl delbr docker0
 ```
 
-You may need to install the ```bridge-utils``` package for the ```brctl``` binary.
+You may need to install the `bridge-utils` package for the `brctl` binary.
 
 #### Restart Docker
 
@@ -190,7 +190,7 @@ NAME        LABELS                             STATUS
 127.0.0.1   kubernetes.io/hostname=127.0.0.1   Ready
 ```
 
-If the status of the node is ```NotReady``` or ```Unknown``` please check that all of the containers you created are successfully running.
+If the status of the node is `NotReady` or `Unknown` please check that all of the containers you created are successfully running.
 If all else fails, ask questions on IRC at [#google-containers](http://webchat.freenode.net/?channels=google-containers).
 
 

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

@@ -47,8 +47,8 @@ NAME           LABELS                                 STATUS
 127.0.0.1      kubernetes.io/hostname=127.0.0.1       Ready
 ```
 
-If the status of any node is ```Unknown``` or ```NotReady``` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on IRC at
-[```#google-containers```](http://webchat.freenode.net/?channels=google-containers) for advice.
+If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on IRC at
+[`#google-containers`](http://webchat.freenode.net/?channels=google-containers) for advice.
 
 ### Run an application
 
@@ -56,7 +56,7 @@ If the status of any node is ```Unknown``` or ```NotReady``` your cluster is bro
 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.
+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
 

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

@@ -37,10 +37,10 @@ Documentation for other releases can be found at
 
 These instructions are very similar to the master set-up above, but they are duplicated for clarity.
 You need to repeat these instructions for each node you want to join the cluster.
-We will assume that the IP address of this node is ```${NODE_IP}``` and you have the IP address of the master in ```${MASTER_IP}``` that you created in the [master instructions](master.md).
+We will assume that the IP address of this node is `${NODE_IP}` and you have the IP address of the master in `${MASTER_IP}` that you created in the [master instructions](master.md).
 
 For each worker node, there are three steps:
-   * [Set up ```flanneld``` on the worker node](#set-up-flanneld-on-the-worker-node)
+   * [Set up `flanneld` on the worker node](#set-up-flanneld-on-the-worker-node)
    * [Start kubernetes on the worker node](#start-kubernetes-on-the-worker-node)
    * [Add the worker to the cluster](#add-the-node-to-the-cluster)
 
@@ -106,7 +106,7 @@ sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from
 
 You now need to edit the docker configuration to activate new flags.  Again, this is system specific.
 
-This may be in ```/etc/default/docker``` or ```/etc/systemd/service/docker.service``` or it may be elsewhere.
+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:
 
@@ -116,14 +116,14 @@ Regardless, you need to add the following to the docker command line:
 
 #### Remove the existing Docker bridge
 
-Docker creates a bridge named ```docker0``` by default.  You need to remove this:
+Docker creates a bridge named `docker0` by default.  You need to remove this:
 
 ```sh
 sudo /sbin/ifconfig docker0 down
 sudo brctl delbr docker0
 ```
 
-You may need to install the ```bridge-utils``` package for the ```brctl``` binary.
+You may need to install the `bridge-utils` package for the `brctl` binary.
 
 #### Restart Docker
 
@@ -143,7 +143,7 @@ systemctl start docker
 
 #### Run the kubelet
 
-Again this is similar to the above, but the ```--api_servers``` now points to the master we set up in the beginning.
+Again this is similar to the above, but the `--api_servers` now points to the master we set up in the beginning.
 
 ```sh
 sudo docker run --net=host -d -v /var/run/docker.sock:/var/run/docker.sock  gcr.io/google_containers/hyperkube:v0.21.2 /hyperkube kubelet --api_servers=http://${MASTER_IP}:8080 --v=2 --address=0.0.0.0 --enable_server --hostname_override=$(hostname -i)
@@ -151,7 +151,7 @@ sudo docker run --net=host -d -v /var/run/docker.sock:/var/run/docker.sock  gcr.
 
 #### Run the service proxy
 
-The service proxy provides load-balancing between groups of containers defined by Kubernetes ```Services```
+The service proxy provides load-balancing between groups of containers defined by Kubernetes `Services`
 
 ```sh
 sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v0.21.2 /hyperkube proxy --master=http://${MASTER_IP}:8080 --v=2