Code snippents shouldn't include the command prompt (#12779)

content/en/docs/tasks/debug-application-cluster/debug-application.md

@@ -31,7 +31,7 @@ your Service?
 The first step in debugging a Pod is taking a look at it.  Check the current state of the Pod and recent events with the following command:
 
 ```shell
-$ kubectl describe pods ${POD_NAME}
+kubectl describe pods ${POD_NAME}
 ```
 
 Look at the state of the containers in the pod.  Are they all `Running`?  Have there been recent restarts?
@@ -68,19 +68,19 @@ First, take a look at the logs of
 the current container:
 
 ```shell
-$ kubectl logs ${POD_NAME} ${CONTAINER_NAME}
+kubectl logs ${POD_NAME} ${CONTAINER_NAME}
 ```
 
 If your container has previously crashed, you can access the previous container's crash log with:
 
 ```shell
-$ kubectl logs --previous ${POD_NAME} ${CONTAINER_NAME}
+kubectl logs --previous ${POD_NAME} ${CONTAINER_NAME}
 ```
 
 Alternately, you can run commands inside that container with `exec`:
 
 ```shell
-$ kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}
+kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}
 ```
 
 {{< note >}}
@@ -90,7 +90,7 @@ $ kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${
 As an example, to look at the logs from a running Cassandra pod, you might run
 
 ```shell
-$ kubectl exec cassandra -- cat /var/log/cassandra/system.log
+kubectl exec cassandra -- cat /var/log/cassandra/system.log
 ```
 
 If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host,
@@ -145,7 +145,7 @@ First, verify that there are endpoints for the service. For every Service object
 You can view this resource with:
 
 ```shell
-$ kubectl get endpoints ${SERVICE_NAME}
+kubectl get endpoints ${SERVICE_NAME}
 ```
 
 Make sure that the endpoints match up with the number of containers that you expect to be a member of your service.
@@ -168,7 +168,7 @@ spec:
 You can use:
 
 ```shell
-$ kubectl get pods --selector=name=nginx,type=frontend
+kubectl get pods --selector=name=nginx,type=frontend
 ```
 
 to list pods that match this selector.  Verify that the list matches the Pods that you expect to provide your Service.

content/en/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md

@@ -39,7 +39,9 @@ Now, when you create a cluster, a message will indicate that the Fluentd log
 collection daemons that run on each node will target Elasticsearch:
 
 ```shell
-$ cluster/kube-up.sh
+cluster/kube-up.sh
+```
+```
 ...
 Project: kubernetes-satnam
 Zone: us-central1-b
@@ -63,7 +65,9 @@ all be running in the kube-system namespace soon after the cluster comes to
 life.
 
 ```shell
-$ kubectl get pods --namespace=kube-system
+kubectl get pods --namespace=kube-system
+```
+```
 NAME                                           READY     STATUS    RESTARTS   AGE
 elasticsearch-logging-v1-78nog                 1/1       Running   0          2h
 elasticsearch-logging-v1-nj2nb                 1/1       Running   0          2h

content/en/docs/tasks/debug-application-cluster/logging-stackdriver.md

@@ -145,7 +145,9 @@ kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
 You can observe the running pod:
 
 ```shell
-$ kubectl get pods
+kubectl get pods
+```
+```
 NAME                                           READY     STATUS    RESTARTS   AGE
 counter                                        1/1       Running   0          5m
 ```
@@ -155,7 +157,9 @@ has to download the container image first. When the pod status changes to `Runni
 you can use the `kubectl logs` command to view the output of this counter pod.
 
 ```shell
-$ kubectl logs counter
+kubectl logs counter
+```
+```
 0: Mon Jan  1 00:00:00 UTC 2001
 1: Mon Jan  1 00:00:01 UTC 2001
 2: Mon Jan  1 00:00:02 UTC 2001
@@ -169,21 +173,27 @@ if the pod is evicted from the node, log files are lost. Let's demonstrate this
 by deleting the currently running counter container:
 
 ```shell
-$ kubectl delete pod counter
+kubectl delete pod counter
+```
+```
 pod "counter" deleted
 ```
 
 and then recreating it:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
+kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
+```
+```
 pod/counter created
 ```
 
 After some time, you can access logs from the counter pod again:
 
 ```shell
-$ kubectl logs counter
+kubectl logs counter
+```
+```
 0: Mon Jan  1 00:01:00 UTC 2001
 1: Mon Jan  1 00:01:01 UTC 2001
 2: Mon Jan  1 00:01:02 UTC 2001
@@ -226,7 +236,9 @@ It uses Stackdriver Logging [filtering syntax](https://cloud.google.com/logging/
 to query specific logs. For example, you can run the following command:
 
 ```none
-$ gcloud beta logging read 'logName="projects/$YOUR_PROJECT_ID/logs/count"' --format json | jq '.[].textPayload'
+gcloud beta logging read 'logName="projects/$YOUR_PROJECT_ID/logs/count"' --format json | jq '.[].textPayload'
+```
+```
 ...
 "2: Mon Jan  1 00:01:02 UTC 2001\n"
 "1: Mon Jan  1 00:01:01 UTC 2001\n"