Replace ``` with ` when emphasizing something inline in docs/

api-conventions.md

@@ -498,7 +498,7 @@ The following HTTP status codes may be returned by the API.
 * `429 StatusTooManyRequests`
   * Indicates that the either the client rate limit has been exceeded or the server has received more requests then it can process.
   * Suggested client recovery behavior:
-    * Read the ```Retry-After``` HTTP header from the response, and wait at least that long before retrying.
+    * Read the `Retry-After` HTTP header from the response, and wait at least that long before retrying.
 * `500 StatusInternalServerError`
   * Indicates that the server can be reached and understood the request, but either an unexpected internal error occurred and the outcome of the call is unknown, or the server cannot complete the action in a reasonable time (this maybe due to temporary server load or a transient communication issue with another server).
   * Suggested client recovery behavior:
@@ -514,12 +514,12 @@ The following HTTP status codes may be returned by the API.
 
 ## Response Status Kind
 
-Kubernetes will always return the ```Status``` kind from any API endpoint when an error occurs.
+Kubernetes will always return the `Status` kind from any API endpoint when an error occurs.
 Clients SHOULD handle these types of objects when appropriate.
 
-A ```Status``` kind will be returned by the API in two cases:
+A `Status` kind will be returned by the API in two cases:
   * When an operation is not successful (i.e. when the server would return a non 2xx HTTP status code).
-  * When a HTTP ```DELETE``` call is successful.
+  * When a HTTP `DELETE` call is successful.
 
 The status object is encoded as JSON and provided as the body of the response.  The status object contains fields for humans and machine consumers of the API to get more detailed information for the cause of the failure. The information in the status object supplements, but does not override, the HTTP status code's meaning. When fields in the status object have the same meaning as generally defined HTTP headers and that header is returned with the response, the header should be considered as having higher priority.
 
@@ -555,17 +555,17 @@ $ curl -v -k -H "Authorization: Bearer WhCDvq4VPpYhrcfmF6ei7V9qlbqTubUc" https:/
 }
 ```
 
-```status``` field contains one of two possible values:
+`status` field contains one of two possible values:
 * `Success`
 * `Failure`
 
 `message` may contain human-readable description of the error
 
-```reason``` may contain a machine-readable description of why this operation is in the `Failure` status. If this value is empty there is no information available. The `reason` clarifies an HTTP status code but does not override it.
+`reason` may contain a machine-readable description of why this operation is in the `Failure` status. If this value is empty there is no information available. The `reason` clarifies an HTTP status code but does not override it.
 
-```details``` may contain extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.
+`details` may contain extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.
 
-Possible values for the ```reason``` and ```details``` fields:
+Possible values for the `reason` and `details` fields:
 * `BadRequest`
   * Indicates that the request itself was invalid, because the request doesn't make any sense, for example deleting a read-only object.
   * This is different than `status reason` `Invalid` above which indicates that the API call could possibly succeed, but the data was invalid.

developer-guides/vagrant.md

@@ -133,7 +133,7 @@ vagrant destroy
 
 Once your Vagrant machines are up and provisioned, the first thing to do is to check that you can use the `kubectl.sh` script.
 
-You may need to build the binaries first, you can do this with ```make```
+You may need to build the binaries first, you can do this with `make`
 
 ```sh
 $ ./cluster/kubectl.sh get nodes
@@ -374,7 +374,7 @@ export KUBERNETES_MINION_MEMORY=2048
 
 #### I ran vagrant suspend and nothing works!
 
-```vagrant suspend``` seems to mess up the network.  It's not supported at this time.
+`vagrant suspend` seems to mess up the network.  It's not supported at this time.
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

development.md

@@ -106,10 +106,10 @@ Kubernetes uses [godep](https://github.com/tools/godep) to manage dependencies.
 
 ### Installing godep
 
-There are many ways to build and host go binaries. Here is an easy way to get utilities like ```godep``` installed:
+There are many ways to build and host go binaries. Here is an easy way to get utilities like `godep` installed:
 
 1) Ensure that [mercurial](http://mercurial.selenic.com/wiki/Download) is installed on your system. (some of godep's dependencies use the mercurial
-source control system).  Use ```apt-get install mercurial``` or ```yum install mercurial``` on Linux, or [brew.sh](http://brew.sh) on OS X, or download
+source control system).  Use `apt-get install mercurial` or `yum install mercurial` on Linux, or [brew.sh](http://brew.sh) on OS X, or download
 directly from mercurial.
 
 2) Create a new GOPATH for your tools and install godep:
@@ -174,7 +174,7 @@ go get -u path/to/dependency
 godep update path/to/dependency
 ```
 
-5) Before sending your PR, it's a good idea to sanity check that your Godeps.json file is ok by re-restoring: ```godep restore```
+5) Before sending your PR, it's a good idea to sanity check that your Godeps.json file is ok by re-restoring: `godep restore`
 
 It is sometimes expedient to manually fix the /Godeps/godeps.json file to minimize the changes.
 

flaky-tests.md

@@ -41,7 +41,7 @@ Running a test 1000 times on your own machine can be tedious and time consuming.
 
 _Note: these instructions are mildly hacky for now, as we get run once semantics and logging they will get better_
 
-There is a testing image ```brendanburns/flake``` up on the docker hub.  We will use this image to test our fix.
+There is a testing image `brendanburns/flake` up on the docker hub.  We will use this image to test our fix.
 
 Create a replication controller with the following config:
 
@@ -74,7 +74,7 @@ kubectl create -f ./controller.yaml
 ```
 
 This will spin up 24 instances of the test.  They will run to completion, then exit, and the kubelet will restart them, accumulating more and more runs of the test.
-You can examine the recent runs of the test by calling ```docker ps -a``` and looking for tasks that exited with non-zero exit codes. Unfortunately, docker ps -a only keeps around the exit status of the last 15-20 containers with the same image, so you have to check them frequently.
+You can examine the recent runs of the test by calling `docker ps -a` and looking for tasks that exited with non-zero exit codes. Unfortunately, docker ps -a only keeps around the exit status of the last 15-20 containers with the same image, so you have to check them frequently.
 You can use this script to automate checking for failures, assuming your cluster is running on GCE and has four nodes:
 
 ```sh
@@ -93,7 +93,7 @@ Eventually you will have sufficient runs for your purposes. At that point you ca
 kubectl stop replicationcontroller flakecontroller
 ```
 
-If you do a final check for flakes with ```docker ps -a```, ignore tasks that exited -1, since that's what happens when you stop the replication controller.
+If you do a final check for flakes with `docker ps -a`, ignore tasks that exited -1, since that's what happens when you stop the replication controller.
 
 Happy flake hunting!
 

making-release-notes.md

@@ -55,14 +55,14 @@ release.  It is likely long and many PRs aren't worth mentioning.  If any of the
 PRs were cherrypicked into patches on the last minor release, you should exclude
 them from the current release's notes.
 
-Open up ```candidate-notes.md``` in your favorite editor.
+Open up `candidate-notes.md` in your favorite editor.
 
 Remove, regroup, organize to your hearts content.
 
 
 ### 4) Update CHANGELOG.md
 
-With the final markdown all set, cut and paste it to the top of ```CHANGELOG.md```
+With the final markdown all set, cut and paste it to the top of `CHANGELOG.md`
 
 ### 5) Update the Release page
 

profiling.md

@@ -71,7 +71,7 @@ to get 30 sec. CPU profile.
 
 ## Contention profiling
 
-To enable contention profiling you need to add line ```rt.SetBlockProfileRate(1)``` in addition to ```m.mux.HandleFunc(...)``` added before (```rt``` stands for ```runtime``` in ```master.go```). This enables 'debug/pprof/block' subpage, which can be used as an input to ```go tool pprof```.
+To enable contention profiling you need to add line `rt.SetBlockProfileRate(1)` in addition to `m.mux.HandleFunc(...)` added before (`rt` stands for `runtime` in `master.go`). This enables 'debug/pprof/block' subpage, which can be used as an input to `go tool pprof`.
 
 
 <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->