Correcting minikube quickstart steps (#14355)

* Correcting minikube quickstart steps

In minikube quickstart section , it was difficult to differentiate between command and its output. Also, There was no details given for each steps and its expected output. This PR fixes these issues.

* Correcting number formatting

Correcting number formatting

* Correcting numbering

Correcting numbering

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>

* Update content/en/docs/setup/minikube.md

Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>

* Corrected formatting 

Corrected formatting

* Correcting number sequence 

Correcting number sequence

content/en/docs/setup/minikube.md

@@ -45,56 +45,74 @@ Note that the IP below is dynamic and can change. It can be retrieved with `mini
 * vmware ([driver installation](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#vmware-unified-driver)) (VMware unified driver)
 * 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
+1. Start a minikube 
+
+    ```        
     minikube start
     ```    
+    The output shows that the kubernetes cluster is started:
+   
     ```
     Starting local Kubernetes cluster...
     Running pre-create checks...
     Creating machine...
     Starting local Kubernetes cluster...
     ```
-```shell
+        
+2. Create an echo server deployment
+
+    ```
     kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
     ```        
+    The output of a successful command verifies that the deployment is created:
+   
     ```
     deployment.apps/hello-minikube created
     ```
         
-```shell
+3. Expose an echo server deployment to create service       
+
+    ```
     kubectl expose deployment hello-minikube --type=NodePort
     ```
+    The output of a successful command verifies that the service is created:
+   
     ```
     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
+4. Check whether the pod is up and running
-via the exposed service.
-To check whether the pod is up and running we can use the following:
 
     ```
     kubectl get pod
     ```
+    The output displays the pod is still being created:     
+         
     ```
     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
+5. Wait for while and then check again, whether the pod is up and running using same command
+
+    ```
     kubectl get pod
+    ```
+    Now the output displays the pod is created and it is running:     
    
     ```
     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:
+6. Curl service which we have created
 
     ```
     curl $(minikube service hello-minikube --url)
     ```        
-```
+    Output looks similer to this:
    
+    ```
     Hostname: hello-minikube-7c77b68cff-8wdzq
 
     Pod Information:
@@ -120,24 +138,33 @@ Request Headers:
     Request Body:
       -no body in request-
     ```
+7. Delete the service which we have created
 
-```shell
+    ```
     kubectl delete services hello-minikube
     ```
+    The output of a successful command verifies that the service is deleted:  
+   
     ```
     service "hello-minikube" deleted
     ```
+8. Delete the deployment which we have created
 
-```shell
+    ```
     kubectl delete deployment hello-minikube
     ```
+    The output of a successful command verifies that the deployment is deleted:
+   
     ```
     deployment.extensions "hello-minikube" deleted
     ```
+9. Stop a minikube
 
-```shell
+    ```
     minikube stop
    ```
+   The output displays the kubernetes cluster is stopping:
+   
    ```
    Stopping local Kubernetes cluster...
    Stopping "minikube"...