diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md b/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md
index c20fcf16f5bcb..46dea2099b63a 100644
--- a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md
+++ b/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,7 +128,7 @@ 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
     ...
@@ -153,7 +153,7 @@ set the `podSubnet` field under the `networking` object of `ClusterConfiguration
       ```
 
     - 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:
+       To generate such a key you can use the following command:
 
       ```sh
       kubeadm alpha certs certificate-key