Fix picky lint errors.

content/docs/tasks/security/mutual-tls.md

@@ -59,7 +59,7 @@ and send request to other services by curl.
 There are several steps:
 
 1. get the productpage pod name
-   
+
     ```command
     $ kubectl get pods -l app=productpage
     NAME                              READY     STATUS    RESTARTS   AGE
@@ -69,36 +69,36 @@ There are several steps:
     Make sure the pod is "Running".
 
 1. ssh into the Envoy container
-   
+
     ```command
     $ kubectl exec -it productpage-v1-4184313719-5mxjc -c istio-proxy /bin/bash
     ```
 
 1. make sure the key/cert is in /etc/certs/ directory
-   
+
     ```command
     $ ls /etc/certs/
     cert-chain.pem   key.pem   root-cert.pem
     ```
 
     > `cert-chain.pem` is Envoy's cert that needs to present to the other side. `key.pem` is Envoy's private key
-    paired with Envoy's cert in `cert-chain.pem`. `root-cert.pem` is the root cert to verify the peer's cert.
-    In this example, we only have one Citadel in a cluster, so all Envoys have the same `root-cert.pem`.
+    > paired with Envoy's cert in `cert-chain.pem`. `root-cert.pem` is the root cert to verify the peer's cert.
+    > In this example, we only have one Citadel in a cluster, so all Envoys have the same `root-cert.pem`.
+
+1. make sure 'curl' is installed by entering:
 
-1. make sure 'curl' is installed by
-   
     ```command
     $ curl
     ```
-    
+
     If curl is installed, you should see something like
-   
+
     ```plain
     curl: try 'curl --help' or 'curl --manual' for more information
     ```
 
     Otherwise run the command below to start over
-   
+
     ```command
     $ kubectl apply -f <(istioctl kube-inject --debug -f samples/bookinfo/kube/bookinfo.yaml)
     ```
@@ -106,7 +106,7 @@ There are several steps:
     > Istio proxy image does not have curl installed while the debug image does. The "--debug" flag in above command redeploys the service with debug image.
 
 1. send requests to another service, for example, details.
-   
+
     ```command
     $ curl https://details:9080/details/0 -v --key /etc/certs/key.pem --cert /etc/certs/cert-chain.pem --cacert /etc/certs/root-cert.pem -k
     ...

content/docs/tasks/traffic-management/ingress.md

@@ -208,7 +208,7 @@ In this subsection we add to our gateway the port 443 to handle the HTTPS traffi
     will automatically load the secret.
 
     > The secret MUST be called `istio-ingressgateway-certs` in the `istio-system` namespace, or it will not
-    be mounted and available to the Istio gateway.
+    > be mounted and available to the Istio gateway.
 
     ```command
     $ kubectl create -n istio-system secret tls istio-ingressgateway-certs --key /tmp/tls.key --cert /tmp/tls.crt