Replace `` with when emphasizing something inline in docs/

docs/user-guide/introspection-and-debugging.md

@@ -34,21 +34,21 @@ Documentation for other releases can be found at
 # Kubernetes User Guide: Managing Applications: Application Introspection and Debugging
 
 Once your application is running, you’ll inevitably need to debug problems with it.
-Earlier we described how you can use ```kubectl get pods``` to retrieve simple status information about
+Earlier we described how you can use `kubectl get pods` to retrieve simple status information about
 your pods. But there are a number of ways to get even more information about your application.
 
 **Table of Contents**
 <!-- BEGIN MUNGE: GENERATED_TOC -->
 
 - [Kubernetes User Guide: Managing Applications: Application Introspection and Debugging](#kubernetes-user-guide-managing-applications-application-introspection-and-debugging)
-  - [Using ```kubectl describe pod``` to fetch details about pods](#using-kubectl-describe-pod-to-fetch-details-about-pods)
+  - [Using `kubectl describe pod` to fetch details about pods](#using-kubectl-describe-pod-to-fetch-details-about-pods)
   - [Example: debugging Pending Pods](#example-debugging-pending-pods)
   - [Example: debugging a down/unreachable node](#example-debugging-a-downunreachable-node)
   - [What's next?](#whats-next)
 
 <!-- END MUNGE: GENERATED_TOC -->
 
-## Using ```kubectl describe pod``` to fetch details about pods
+## Using `kubectl describe pod` to fetch details about pods
 
 For this example we’ll use a ReplicationController to create two pods, similar to the earlier example.
 
@@ -87,7 +87,7 @@ my-nginx-gy1ij   1/1       Running   0          1m
 my-nginx-yv5cn   1/1       Running   0          1m
 ```
 
-We can retrieve a lot more information about each of these pods using ```kubectl describe pod```. For example:
+We can retrieve a lot more information about each of these pods using `kubectl describe pod`. For example:
 
 ```console
 $ kubectl describe pod my-nginx-gy1ij
@@ -150,7 +150,7 @@ my-nginx-iichp   0/1       Running   0          8s
 my-nginx-tc2j9   0/1       Running   0          8s
 ```
 
-To find out why the my-nginx-9unp9 pod is not running, we can use ```kubectl describe pod``` on the pending Pod and look at its events:
+To find out why the my-nginx-9unp9 pod is not running, we can use `kubectl describe pod` on the pending Pod and look at its events:
 
 ```console
 $ kubectl describe pod my-nginx-9unp9 
@@ -177,11 +177,11 @@ Events:
   Thu, 09 Jul 2015 23:56:21 -0700	Fri, 10 Jul 2015 00:01:30 -0700	21	{scheduler }			failedScheduling	Failed for reason PodFitsResources and possibly others
 ```
 
-Here you can see the event generated by the scheduler saying that the Pod failed to schedule for reason ```PodFitsResources``` (and possibly others). ```PodFitsResources``` means there were not enough resources for the Pod on any of the nodes. Due to the way the event is generated, there may be other reasons as well, hence "and possibly others."
+Here you can see the event generated by the scheduler saying that the Pod failed to schedule for reason `PodFitsResources` (and possibly others). `PodFitsResources` means there were not enough resources for the Pod on any of the nodes. Due to the way the event is generated, there may be other reasons as well, hence "and possibly others."
 
-To correct this situation, you can use ```kubectl scale``` to update your Replication Controller to specify four or fewer replicas. (Or you could just leave the one Pod pending, which is harmless.)
+To correct this situation, you can use `kubectl scale` to update your Replication Controller to specify four or fewer replicas. (Or you could just leave the one Pod pending, which is harmless.)
 
-In addition to ```kubectl describe pod```, another way to get extra information about a pod (beyond what is provided by ```kubectl get pod```) is to pass the ```-o yaml``` output format flag to ```kubectl get pod```. This will give you, in YAML format, even more information than ```kubectl describe pod```--essentially all of the information the system has about the Pod. Here you will see things like annotations (which are key-value metadata without the label restrictions, that is used internally by Kubernetes system components), restart policy, ports, and volumes.
+In addition to `kubectl describe pod`, another way to get extra information about a pod (beyond what is provided by `kubectl get pod`) is to pass the `-o yaml` output format flag to `kubectl get pod`. This will give you, in YAML format, even more information than `kubectl describe pod`--essentially all of the information the system has about the Pod. Here you will see things like annotations (which are key-value metadata without the label restrictions, that is used internally by Kubernetes system components), restart policy, ports, and volumes.
 
 ```yaml
 $ kubectl get pod my-nginx-i595c -o yaml
@@ -247,7 +247,7 @@ status:
 
 ## Example: debugging a down/unreachable node
 
-Sometimes when debugging it can be useful to look at the status of a node -- for example, because you've noticed strange behavior of a Pod that’s running on the node, or to find out why a Pod won’t schedule onto the node. As with Pods, you can use ```kubectl describe node``` and ```kubectl get node -o yaml``` to retrieve detailed information about nodes. For example, here's what you'll see if a node is down (disconnected from the network, or kubelet dies and won't restart, etc.). Notice the events that show the node is NotReady, and also notice that the pods are no longer running (they are evicted after five minutes of NotReady status).
+Sometimes when debugging it can be useful to look at the status of a node -- for example, because you've noticed strange behavior of a Pod that’s running on the node, or to find out why a Pod won’t schedule onto the node. As with Pods, you can use `kubectl describe node` and `kubectl get node -o yaml` to retrieve detailed information about nodes. For example, here's what you'll see if a node is down (disconnected from the network, or kubelet dies and won't restart, etc.). Notice the events that show the node is NotReady, and also notice that the pods are no longer running (they are evicted after five minutes of NotReady status).
 
 ```console
 $ kubectl get nodes