Tweak indentation on portforward page

This PR fixes the indentation nits in the
`port-forward-access-application-cluster` page.
We are not supposed to indent lines by 4 spaces because such
indentations may mislead the markdown parser to render them as code
snippets.

content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md

@@ -11,180 +11,169 @@ This page shows how to use `kubectl port-forward` to connect to a MongoDB
 server running in a Kubernetes cluster. This type of connection can be useful
 for database debugging.
 
-
-
-
 ## {{% heading "prerequisites" %}}
 
-
 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
-
 * Install [MongoDB Shell](https://www.mongodb.com/try/download/shell).
 
-
-
-
 <!-- steps -->
 
 ## Creating MongoDB deployment and service
 
 1. Create a Deployment that runs MongoDB:
 
-    ```shell
-    kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-deployment.yaml
-    ```
-
-    The output of a successful command verifies that the deployment was created:
+   ```shell
+   kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-deployment.yaml
+   ```
 
-    ```
-    deployment.apps/mongo created
-    ```
+   The output of a successful command verifies that the deployment was created:
 
-    View the pod status to check that it is ready:
+   ```
+   deployment.apps/mongo created
+   ```
 
-    ```shell
-    kubectl get pods
-    ```
+   View the pod status to check that it is ready:
 
-    The output displays the pod created:
+   ```shell
+   kubectl get pods
+   ```
 
-    ```
-    NAME                     READY   STATUS    RESTARTS   AGE
-    mongo-75f59d57f4-4nd6q   1/1     Running   0          2m4s
-    ```
+   The output displays the pod created:
 
-    View the Deployment's status:
+   ```
+   NAME                     READY   STATUS    RESTARTS   AGE
+   mongo-75f59d57f4-4nd6q   1/1     Running   0          2m4s
+   ```
 
-    ```shell
-    kubectl get deployment
-    ```
+   View the Deployment's status:
 
-    The output displays that the Deployment was created:
+   ```shell
+   kubectl get deployment
+   ```
 
-    ```
-    NAME    READY   UP-TO-DATE   AVAILABLE   AGE
-    mongo   1/1     1            1           2m21s
-    ```
+   The output displays that the Deployment was created:
 
-    The Deployment automatically manages a ReplicaSet.
-    View the ReplicaSet status using:
+   ```
+   NAME    READY   UP-TO-DATE   AVAILABLE   AGE
+   mongo   1/1     1            1           2m21s
+   ```
 
-    ```shell
-    kubectl get replicaset
-    ```
+   The Deployment automatically manages a ReplicaSet.
+   View the ReplicaSet status using:
 
-    The output displays that the ReplicaSet was created:
+   ```shell
+   kubectl get replicaset
+   ```
 
-    ```
-    NAME               DESIRED   CURRENT   READY   AGE
-    mongo-75f59d57f4   1         1         1       3m12s
-    ```
+   The output displays that the ReplicaSet was created:
 
+   ```
+   NAME               DESIRED   CURRENT   READY   AGE
+   mongo-75f59d57f4   1         1         1       3m12s
+   ```
 
 2. Create a Service to expose MongoDB on the network:
 
-    ```shell
-    kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-service.yaml
-    ```
+   ```shell
+   kubectl apply -f https://k8s.io/examples/application/mongodb/mongo-service.yaml
+   ```
 
-    The output of a successful command verifies that the Service was created:
+   The output of a successful command verifies that the Service was created:
 
-    ```
-    service/mongo created
-    ```
+   ```
+   service/mongo created
+   ```
 
-    Check the Service created:
+   Check the Service created:
 
-    ```shell
-    kubectl get service mongo
-    ```
+   ```shell
+   kubectl get service mongo
+   ```
 
-    The output displays the service created:
+   The output displays the service created:
 
-    ```
-    NAME    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
-    mongo   ClusterIP   10.96.41.183   <none>        27017/TCP   11s
-    ```
+   ```
+   NAME    TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
+   mongo   ClusterIP   10.96.41.183   <none>        27017/TCP   11s
+   ```
 
 3. Verify that the MongoDB server is running in the Pod, and listening on port 27017:
 
-    ```shell
-    # Change mongo-75f59d57f4-4nd6q to the name of the Pod
-    kubectl get pod mongo-75f59d57f4-4nd6q --template='{{(index (index .spec.containers 0).ports 0).containerPort}}{{"\n"}}'
-    ```
+   ```shell
+   # Change mongo-75f59d57f4-4nd6q to the name of the Pod
+   kubectl get pod mongo-75f59d57f4-4nd6q --template='{{(index (index .spec.containers 0).ports 0).containerPort}}{{"\n"}}'
+   ```
 
-    The output displays the port for MongoDB in that Pod:
+   The output displays the port for MongoDB in that Pod:
 
-    ```
-    27017
-    ```
+   ```
+   27017
+   ```
 
-    (this is the TCP port allocated to MongoDB on the internet).
+   27017 is the TCP port allocated to MongoDB on the internet.
 
 ## Forward a local port to a port on the Pod
 
-1.  `kubectl port-forward` allows using resource name, such as a pod name, to select a matching pod to port forward to.
+1. `kubectl port-forward` allows using resource name, such as a pod name, to select a matching pod to port forward to.
 
 
-    ```shell
-    # Change mongo-75f59d57f4-4nd6q to the name of the Pod
-    kubectl port-forward mongo-75f59d57f4-4nd6q 28015:27017
-    ```
+   ```shell
+   # Change mongo-75f59d57f4-4nd6q to the name of the Pod
+   kubectl port-forward mongo-75f59d57f4-4nd6q 28015:27017
+   ```
 
-    which is the same as
+   which is the same as
 
-    ```shell
-    kubectl port-forward pods/mongo-75f59d57f4-4nd6q 28015:27017
-    ```
+   ```shell
+   kubectl port-forward pods/mongo-75f59d57f4-4nd6q 28015:27017
+   ```
 
-    or
+   or
 
-    ```shell
-    kubectl port-forward deployment/mongo 28015:27017
-    ```
+   ```shell
+   kubectl port-forward deployment/mongo 28015:27017
+   ```
 
-    or
+   or
 
-    ```shell
-    kubectl port-forward replicaset/mongo-75f59d57f4 28015:27017
-    ```
+   ```shell
+   kubectl port-forward replicaset/mongo-75f59d57f4 28015:27017
+   ```
 
-    or
+   or
 
-    ```shell
-    kubectl port-forward service/mongo 28015:27017
-    ```
+   ```shell
+   kubectl port-forward service/mongo 28015:27017
+   ```
 
-    Any of the above commands works. The output is similar to this:
+   Any of the above commands works. The output is similar to this:
 
-    ```
-    Forwarding from 127.0.0.1:28015 -> 27017
-    Forwarding from [::1]:28015 -> 27017
-    ```
+   ```
+   Forwarding from 127.0.0.1:28015 -> 27017
+   Forwarding from [::1]:28015 -> 27017
+   ```
 
-{{< note >}}
-
-`kubectl port-forward` does not return. To continue with the exercises, you will need to open another terminal.
+   {{< note >}}
+   `kubectl port-forward` does not return. To continue with the exercises, you will need to open another terminal.
+   {{< /note >}}
 
-{{< /note >}}
+2. Start the MongoDB command line interface:
 
-2.  Start the MongoDB command line interface:
+   ```shell
+   mongosh --port 28015
+   ```
 
-    ```shell
-    mongosh --port 28015
-    ```
+3. At the MongoDB command line prompt, enter the `ping` command:
 
-3.  At the MongoDB command line prompt, enter the `ping` command:
+   ```
+   db.runCommand( { ping: 1 } )
+   ```
 
-    ```
-    db.runCommand( { ping: 1 } )
-    ```
+   A successful ping request returns:
 
-    A successful ping request returns:
-
-    ```
-    { ok: 1 }
-    ```
+   ```
+   { ok: 1 }
+   ```
 
 ### Optionally let _kubectl_ choose the local port {#let-kubectl-choose-local-port}
 
@@ -204,7 +193,6 @@ Forwarding from 127.0.0.1:63753 -> 27017
 Forwarding from [::1]:63753 -> 27017
 ```
 
-
 <!-- discussion -->
 
 ## Discussion
@@ -219,9 +207,7 @@ The support for UDP protocol is tracked in
 [issue 47862](https://github.com/kubernetes/kubernetes/issues/47862).
 {{< /note >}}
 
-
-
-
 ## {{% heading "whatsnext" %}}
 
 Learn more about [kubectl port-forward](/docs/reference/generated/kubectl/kubectl-commands/#port-forward).
+