Skip to content

Commit 31c314e

Browse files
author
Duffie Cooley
committed
Minor doc fix for syntax and typo
Signed-off-by: Duffie Cooley <cooleyd@vmware.com>
1 parent 0044acb commit 31c314e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

+3-3
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ option. Your cluster requirements may need a different configuration.
114114
- The `--upload-certs` flag is used to upload the certificates that should be shared
115115
across all the control-plane instances to the cluster. If instead, you prefer to copy certs across
116116
control-plane nodes manually or using automation tools, please remove this flag and refer to [Manual
117-
certificate distribution](#manual-certs) section bellow.
117+
certificate distribution](#manual-certs) section below.
118118

119119
{{< note >}}
120120
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
128128
set the `podSubnet` field under the `networking` object of `ClusterConfiguration`.
129129
{{< /note >}}
130130

131-
After the command completes you should see something like so:
131+
- After the command completes you should see something like so:
132132

133133
```sh
134134
...
@@ -153,7 +153,7 @@ set the `podSubnet` field under the `networking` object of `ClusterConfiguration
153153
```
154154

155155
- You can also specify a custom `--certificate-key` during `init` that can later be used by `join`.
156-
To generate such a key you can use the following command:
156+
To generate such a key you can use the following command:
157157

158158
```sh
159159
kubeadm alpha certs certificate-key

0 commit comments

Comments
 (0)