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

content/en/docs/setup/minikube.md

@@ -47,30 +47,49 @@ Note that the IP below is dynamic and can change. It can be retrieved with `mini
 * none (Runs the Kubernetes components on the host and not in a VM. Using this driver requires Docker ([docker install](https://docs.docker.com/install/linux/docker-ce/ubuntu/)) and a Linux environment)
 
 ```shell
-$ minikube start
+minikube start
+```
+```
 Starting local Kubernetes cluster...
 Running pre-create checks...
 Creating machine...
 Starting local Kubernetes cluster...
-
-$ kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
+```
+```shell
+kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
+```
 deployment.apps/hello-minikube created
-$ kubectl expose deployment hello-minikube --type=NodePort
-service/hello-minikube exposed
+```
 
+```shell
+kubectl expose deployment hello-minikube --type=NodePort
+```
+```
+service/hello-minikube exposed
+```
+```
 # We have now launched an echoserver pod but we have to wait until the pod is up before curling/accessing it
 # via the exposed service.
 # To check whether the pod is up and running we can use the following:
-$ kubectl get pod
+kubectl get pod
+```
+```
 NAME                              READY     STATUS              RESTARTS   AGE
 hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
+```
+```
 # We can see that the pod is still being created from the ContainerCreating status
-$ kubectl get pod
+kubectl get pod
+```
+```
 NAME                              READY     STATUS    RESTARTS   AGE
 hello-minikube-3383150820-vctvh   1/1       Running   0          13s
+```
+```
 # We can see that the pod is now Running and we will now be able to curl it:
-$ curl $(minikube service hello-minikube --url)
-
+curl $(minikube service hello-minikube --url)
+```
+```
 
 Hostname: hello-minikube-7c77b68cff-8wdzq
 
@@ -96,13 +115,26 @@ Request Headers:
 
 Request Body:
 	-no body in request-
+```
 
-
-$ kubectl delete services hello-minikube
+```shell
+kubectl delete services hello-minikube
+```
+```
 service "hello-minikube" deleted
-$ kubectl delete deployment hello-minikube
+```
+
+```shell
+kubectl delete deployment hello-minikube
+```
+```
 deployment.extensions "hello-minikube" deleted
-$ minikube stop
+```
+
+```shell
+minikube stop
+```
+```
 Stopping local Kubernetes cluster...
 Stopping "minikube"...
 ```
@@ -114,7 +146,7 @@ Stopping "minikube"...
 To use [containerd](https://github.com/containerd/containerd) as the container runtime, run:
 
 ```bash
-$ minikube start \
+minikube start \
     --network-plugin=cni \
     --enable-default-cni \
     --container-runtime=containerd \
@@ -124,7 +156,7 @@ $ minikube start \
 Or you can use the extended version:
 
 ```bash
-$ minikube start \
+minikube start \
     --network-plugin=cni \
     --enable-default-cni \
     --extra-config=kubelet.container-runtime=remote \
@@ -138,7 +170,7 @@ $ minikube start \
 To use [CRI-O](https://github.com/kubernetes-incubator/cri-o) as the container runtime, run:
 
 ```bash
-$ minikube start \
+minikube start \
     --network-plugin=cni \
     --enable-default-cni \
     --container-runtime=cri-o \
@@ -148,7 +180,7 @@ $ minikube start \
 Or you can use the extended version:
 
 ```bash
-$ minikube start \
+minikube start \
     --network-plugin=cni \
     --enable-default-cni \
     --extra-config=kubelet.container-runtime=remote \
@@ -162,7 +194,7 @@ $ minikube start \
 To use [rkt](https://github.com/rkt/rkt) as the container runtime run:
 
 ```shell
-$ minikube start \
+minikube start \
     --network-plugin=cni \
     --enable-default-cni \
     --container-runtime=rkt
@@ -379,7 +411,7 @@ To do this, pass the required environment variables as flags during `minikube st
 For example:
 
 ```shell
-$ minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \
+minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \
                  --docker-env https_proxy=https://$YOURPROXY:PORT
 ```
 
@@ -387,7 +419,7 @@ If your Virtual Machine address is 192.168.99.100, then chances are your proxy s
 To by-pass proxy configuration for this IP address, you should modify your no_proxy settings. You can do so with:
 
 ```shell
-$ export no_proxy=$no_proxy,$(minikube ip)
+export no_proxy=$no_proxy,$(minikube ip)
 ```
 
 ## Known Issues