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

content/en/docs/concepts/overview/working-with-objects/field-selectors.md

@@ -12,15 +12,15 @@ _Field selectors_ let you [select Kubernetes resources](/docs/concepts/overview/
 This `kubectl` command selects all Pods for which the value of the [`status.phase`](/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase) field is `Running`:
 
 ```shell
-$ kubectl get pods --field-selector status.phase=Running
+kubectl get pods --field-selector status.phase=Running
 ```
 
 {{< note >}}
 Field selectors are essentially resource *filters*. By default, no selectors/filters are applied, meaning that all resources of the specified type are selected. This makes the following `kubectl` queries equivalent:
 
 ```shell
-$ kubectl get pods
-$ kubectl get pods --field-selector ""
+kubectl get pods
+kubectl get pods --field-selector ""
 ```
 {{< /note >}}
 
@@ -29,7 +29,9 @@ $ kubectl get pods --field-selector ""
 Supported field selectors vary by Kubernetes resource type. All resource types support the `metadata.name` and `metadata.namespace` fields. Using unsupported field selectors produces an error. For example:
 
 ```shell
-$ kubectl get ingress --field-selector foo.bar=baz
+kubectl get ingress --field-selector foo.bar=baz
+```
+```
 Error from server (BadRequest): Unable to find "ingresses" that match label selector "", field selector "foo.bar=baz": "foo.bar" is not a known field selector: only "metadata.name", "metadata.namespace"
 ```
 
@@ -38,7 +40,7 @@ Error from server (BadRequest): Unable to find "ingresses" that match label sele
 You can use the `=`, `==`, and `!=` operators with field selectors (`=` and `==` mean the same thing). This `kubectl` command, for example, selects all Kubernetes Services that aren't in the `default` namespace:
 
 ```shell
-$ kubectl get services --field-selector metadata.namespace!=default
+kubectl get services --field-selector metadata.namespace!=default
 ```
 
 ## Chained selectors
@@ -46,7 +48,7 @@ $ kubectl get services --field-selector metadata.namespace!=default
 As with [label](/docs/concepts/overview/working-with-objects/labels) and other selectors, field selectors can be chained together as a comma-separated list. This `kubectl` command selects all Pods for which the `status.phase` does not equal `Running` and the `spec.restartPolicy` field equals `Always`:
 
 ```shell
-$ kubectl get pods --field-selector=status.phase!=Running,spec.restartPolicy=Always
+kubectl get pods --field-selector=status.phase!=Running,spec.restartPolicy=Always
 ```
 
 ## Multiple resource types
@@ -54,5 +56,5 @@ $ kubectl get pods --field-selector=status.phase!=Running,spec.restartPolicy=Alw
 You use field selectors across multiple resource types. This `kubectl` command selects all Statefulsets and Services that are not in the `default` namespace:
 
 ```shell
-$ kubectl get statefulsets,services --field-selector metadata.namespace!=default
+kubectl get statefulsets,services --field-selector metadata.namespace!=default
 ```

content/en/docs/concepts/overview/working-with-objects/kubernetes-objects.md

@@ -46,7 +46,7 @@ One way to create a Deployment using a `.yaml` file like the one above is to use
 in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/application/deployment.yaml --record
+kubectl create -f https://k8s.io/examples/application/deployment.yaml --record
 ```
 
 The output is similar to this:

content/en/docs/concepts/overview/working-with-objects/labels.md

@@ -139,25 +139,25 @@ LIST and WATCH operations may specify label selectors to filter the sets of obje
 Both label selector styles can be used to list or watch resources via a REST client. For example, targeting `apiserver` with `kubectl` and using _equality-based_ one may write:
 
 ```shell
-$ kubectl get pods -l environment=production,tier=frontend
+kubectl get pods -l environment=production,tier=frontend
 ```
 
 or using _set-based_ requirements:
 
 ```shell
-$ kubectl get pods -l 'environment in (production),tier in (frontend)'
+kubectl get pods -l 'environment in (production),tier in (frontend)'
 ```
 
 As already mentioned _set-based_ requirements are more expressive.  For instance, they can implement the _OR_ operator on values:
 
 ```shell
-$ kubectl get pods -l 'environment in (production, qa)'
+kubectl get pods -l 'environment in (production, qa)'
 ```
 
 or restricting negative matching via _exists_ operator:
 
 ```shell
-$ kubectl get pods -l 'environment,environment notin (frontend)'
+kubectl get pods -l 'environment,environment notin (frontend)'
 ```
 
 ### Set references in API objects

content/en/docs/concepts/overview/working-with-objects/namespaces.md

@@ -46,7 +46,9 @@ for namespaces](/docs/admin/namespaces).
 You can list the current namespaces in a cluster using:
 
 ```shell
-$ kubectl get namespaces
+kubectl get namespaces
+```
+```
 NAME          STATUS    AGE
 default       Active    1d
 kube-system   Active    1d
@@ -66,8 +68,8 @@ To temporarily set the namespace for a request, use the `--namespace` flag.
 For example:
 
 ```shell
-$ kubectl --namespace=<insert-namespace-name-here> run nginx --image=nginx
-$ kubectl --namespace=<insert-namespace-name-here> get pods
+kubectl --namespace=<insert-namespace-name-here> run nginx --image=nginx
+kubectl --namespace=<insert-namespace-name-here> get pods
 ```
 
 ### Setting the namespace preference
@@ -76,9 +78,9 @@ You can permanently save the namespace for all subsequent kubectl commands in th
 context.
 
 ```shell
-$ kubectl config set-context $(kubectl config current-context) --namespace=<insert-namespace-name-here>
+kubectl config set-context $(kubectl config current-context) --namespace=<insert-namespace-name-here>
 # Validate it
-$ kubectl config view | grep namespace:
+kubectl config view | grep namespace:
 ```
 
 ## Namespaces and DNS
@@ -101,10 +103,10 @@ To see which Kubernetes resources are and aren't in a namespace:
 
 ```shell
 # In a namespace
-$ kubectl api-resources --namespaced=true
+kubectl api-resources --namespaced=true
 
 # Not in a namespace
-$ kubectl api-resources --namespaced=false
+kubectl api-resources --namespaced=false
 ```
 
 {{% /capture %}}