Merge pull request #11118 from ErikJiang/upd_doc_typos

📖 Fix typos in clusterctl doc

docs/book/src/clusterctl/commands/alpha-topology-plan.md

@@ -39,7 +39,7 @@ to support use cases where other controllers are co-authoring the same objects,
 in a dry-run scenario.
 
 As a consequence Dry-Run can give some false positives/false negatives when trying to have a preview of
-changes to a set of existing topology owned objects. In other worlds this limitation impacts all the use cases described
+changes to a set of existing topology owned objects. In other words this limitation impacts all the use cases described
 below except for "Designing a new ClusterClass".
 
 More specifically:

docs/book/src/clusterctl/commands/upgrade.md

@@ -131,7 +131,7 @@ In this case, all the provider's versions must be explicitly stated.
 
 Use `clusterctl` CLI options to target the [desired version](https://github.com/kubernetes-sigs/cluster-api/releases).  
 
-The following shows an example of upgrading `bootrap`, `kubeadm` and `core` components to version `v1.6.0-rc.1`:
+The following shows an example of upgrading `bootstrap`, `kubeadm` and `core` components to version `v1.6.0-rc.1`:
 
 ```bash
 TARGET_VERSION=v1.6.0-rc.1
@@ -148,7 +148,7 @@ clusterctl upgrade apply \
 
 <h1> Deploying nightly release images </h1>
 
-Cluster API publishes nightly versions of the project components' manifests from the `main` branch to a Google storage bucket for user consumption. The syntax for the URL is: `https://storage.googleapis.com/k8s-staging-cluster-api/components/nightly_main_<YYYYMMDD>/<COMPENENT_NAME>-components.yaml`.
+Cluster API publishes nightly versions of the project components' manifests from the `main` branch to a Google storage bucket for user consumption. The syntax for the URL is: `https://storage.googleapis.com/k8s-staging-cluster-api/components/nightly_main_<YYYYMMDD>/<COMPONENT_NAME>-components.yaml`.
 
 Please note that these files are deleted after a certain period, at the time of this writing 60 days after file creation.