Minor doc fix for syntax and typo

Signed-off-by: Duffie Cooley <[email protected]>

content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md

@@ -114,7 +114,7 @@ option. Your cluster requirements may need a different configuration.
     - The `--upload-certs` flag is used to upload the certificates that should be shared
     across all the control-plane instances to the cluster. If instead, you prefer to copy certs across
     control-plane nodes manually or using automation tools, please remove this flag and refer to [Manual
-    certificate distribution](#manual-certs) section bellow.
+    certificate distribution](#manual-certs) section below.
 
 {{< note >}}
 The `kubeadm init` flags `--config` and `--certificate-key` cannot be mixed, therefore if you want
@@ -128,9 +128,9 @@ To add a pod CIDR pass the flag `--pod-network-cidr`, or if you are using a kube
 set the `podSubnet` field under the `networking` object of `ClusterConfiguration`.
 {{< /note >}}
 
-    After the command completes you should see something like so:
+- After the command completes you should see something like so:
 
-    ```sh
+  ```sh
     ...
     You can now join any number of control-plane node by running the following command on each as a root:
       kubeadm join 192.168.0.200:6443 --token 9vr73a.a8uxyaju799qwdjv --discovery-token-ca-cert-hash sha256:7c2e69131a36ae2a042a339b33381c6d0d43887e2de83720eff5359e26aec866 --control-plane --certificate-key f8902e114ef118304e561c3ecd4d0b543adc226b7a07f675f56564185ffe0c07
@@ -140,24 +140,24 @@ set the `podSubnet` field under the `networking` object of `ClusterConfiguration
 
     Then you can join any number of worker nodes by running the following on each as root:
       kubeadm join 192.168.0.200:6443 --token 9vr73a.a8uxyaju799qwdjv --discovery-token-ca-cert-hash sha256:7c2e69131a36ae2a042a339b33381c6d0d43887e2de83720eff5359e26aec866
-    ```
+  ```
 
-    - Copy this output to a text file. You will need it later to join control plane and worker nodes to the cluster.
-    - When `--upload-certs` is used with `kubeadm init`, the certificates of the primary control plane
-    are encrypted and uploaded in the `kubeadm-certs` Secret.
-    - To re-upload the certificates and generate a new decryption key, use the following command on a control plane
-    node that is already joined to the cluster:
+- Copy this output to a text file. You will need it later to join control plane and worker nodes to the cluster.
+- When `--upload-certs` is used with `kubeadm init`, the certificates of the primary control plane
+  are encrypted and uploaded in the `kubeadm-certs` Secret.
+- To re-upload the certificates and generate a new decryption key, use the following command on a control plane
+  node that is already joined to the cluster:
 
-      ```sh
-      sudo kubeadm init phase upload-certs --upload-certs
-      ```
+  ```sh
+  sudo kubeadm init phase upload-certs --upload-certs
+  ```
 
-    - You can also specify a custom `--certificate-key` during `init` that can later be used by `join`.
-    To generate such a key you can use the following command:
+- You can also specify a custom `--certificate-key` during `init` that can later be used by `join`.
+  To generate such a key you can use the following command:
 
-      ```sh
-      kubeadm alpha certs certificate-key
-      ```
+  ```sh
+  kubeadm alpha certs certificate-key
+  ```
 
 {{< note >}}
 The `kubeadm-certs` Secret and decryption key expire after two hours.
@@ -250,13 +250,13 @@ a configuration file with the etcd endpoints under the `external` object for `et
 In the case of the stacked etcd topology this is managed automatically.
 {{< /note >}}
 
-    -  Replace the following variables in the config template with the appropriate values for your cluster:
+-  Replace the following variables in the config template with the appropriate values for your cluster:
 
-        - `LOAD_BALANCER_DNS`
-        - `LOAD_BALANCER_PORT`
-        - `ETCD_0_IP`
-        - `ETCD_1_IP`
-        - `ETCD_2_IP`
+    - `LOAD_BALANCER_DNS`
+    - `LOAD_BALANCER_PORT`
+    - `ETCD_0_IP`
+    - `ETCD_1_IP`
+    - `ETCD_2_IP`
 
 The following steps are similar to the stacked etcd setup: