Fix minor docs typos

docs/addons.md

@@ -39,7 +39,7 @@ spec:
 
 **Warning: cert-manager only supports one installation per cluster. If you are already running cert-manager, you need to remove this installation prior to enabling this addon. As long as you are using v1 versions of the cert-manager resources, it is safe to remove existing installs and replace it with this addon**
 
-Read more about cert-managre in the [official documentation](https://cert-manager.io/docs/)
+Read more about cert-manager in the [official documentation](https://cert-manager.io/docs/)
 
 #### Metrics server
 {{ kops_feature_table(kops_added_default='1.19') }}

docs/contributing/homebrew.md

@@ -1,4 +1,4 @@
-# Installing kOps via Hombrew
+# Installing kOps via Homebrew
 
 Homebrew makes installing kOps [very simple for MacOS.](../install.md)
 ```bash

docs/contributing/testing.md

@@ -39,7 +39,7 @@ This assumes you have already built the kOps binary from source. The exact path
 GINKGO_PARALLEL=y kubetest --test --test_args="--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort" --provider=aws --deployment=kops --cluster=my.testcluster.com --kops-state=${KOPS_STATE_STORE} --kops ${GOPATH}/bin/kops --extract=ci/latest
 ```
 
-Note the `--extract` flag is only needed on first run or whenever you want to update the kubernetes build. You can omit this flag to run against the already extacted tree on subsequent runs. Just `cd` into the `kubernetes` directory first.
+Note the `--extract` flag is only needed on first run or whenever you want to update the kubernetes build. You can omit this flag to run against the already extracted tree on subsequent runs. Just `cd` into the `kubernetes` directory first.
 
 ### Running against a new cluster
 

docs/examples/coreos-kops-tests-multimaster.md

@@ -111,7 +111,7 @@ aws ec2 describe-images --image-id ami-32705b49 --output table
 ||+----------------------------------+---------------------------------+||
 ```
 
-Also, you can obtaing the image owner/name using the following aws-cli command:
+Also, you can obtain the image owner/name using the following aws-cli command:
 
 ```bash
 aws ec2 describe-images --region=us-east-1 --owner=595879546273 \

docs/networking/aws-vpc.md

@@ -1,6 +1,6 @@
 # Amazon VPC
 
-The Amazon VPC CNI uses the native AWS networking for Pods. Every pod gets an Elastic Network Interface (ENI) on the node it is running and an IP address beloning to the subnets assigned to the node.
+The Amazon VPC CNI uses the native AWS networking for Pods. Every pod gets an Elastic Network Interface (ENI) on the node it is running and an IP address belonging to the subnets assigned to the node.
 
 ## Installing
 

docs/networking/cilium.md

@@ -105,7 +105,7 @@ kops rolling-update cluster --yes
 
 This feature is in beta state as of kOps 1.18.
 
-As of kOps 1.18, you can have Cilium provision AWS managed adresses and attach them directly to Pods much like Lyft VPC and AWS VPC. See [the Cilium docs for more information](https://docs.cilium.io/en/v1.6/concepts/ipam/eni/)
+As of kOps 1.18, you can have Cilium provision AWS managed addresses and attach them directly to Pods much like Lyft VPC and AWS VPC. See [the Cilium docs for more information](https://docs.cilium.io/en/v1.6/concepts/ipam/eni/)
 
 When using ENI IPAM you need to disable masquerading in Cilium as well.
 

docs/state.md

@@ -160,7 +160,7 @@ The swift store can be configured by providing your OpenStack credentials and co
 - `OS_PASSWORD`: the password for the useraccount
 - `OS_TENANT_ID`: the tenant id
 - `OS_TENANT_NAME`: the tenant name
-- `OS_PROJECT_ID`: the poject id
+- `OS_PROJECT_ID`: the project id
 - `OS_PROJECT_NAME`: the project name
 - `OS_DOMAIN_ID`: the domain ID
 - `OS_DOMAIN_NAME`: the domain name

docs/tutorial/working-with-instancegroups.md

@@ -1,4 +1,4 @@
-# Managinging Instance Groups
+# Managing Instance Groups
 
 kOps has the concept of "instance groups", which are a group of similar machines. On AWS, they map to
 an Auto Scaling group.