More comments

Author: fabriziopandini

docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md

@@ -19,6 +19,7 @@ proposal because most of the changes described below are a consequence of the wo
     * [MachineSet](#machineset)
     * [MachinePool](#machinepool)
     * [Machine](#machine)
+    * [MachineHealthCheck](#machinehealthcheck)
     * [ClusterClass](#clusterclass)
     * [KubeadmConfig](#kubeadmconfig)
     * [KubeadmControlPlane](#kubeadmcontrolplane)
@@ -57,9 +58,9 @@ proposal because most of the changes described below are a consequence of the wo
 - v1beta2 API version has been introduced; see following paragraphs for more details
 - If you are using the `runtime.cluster.x-k8s.io` API group, please be aware that
   - `ExtensionConfig` v1alpha1 has been deprecated, and it will be removed in a following release.
-  - `ExtensionConfig` v1beta2 been has created (thus aligning with other Cluster API resources)
+  - `ExtensionConfig` v1beta2 has been created (thus aligning with other Cluster API resources)
 
- ### All CRDs
+### All CRDs
 
 - The transition to the new K8s aligned conditions using `metav1.Conditions` types and the new condition semantic
   has been completed for all Kinds:
@@ -313,7 +314,7 @@ As documented in [Suggested changes for providers](#suggested-changes-for-provid
   Please refer to [API Changes](#api-changes) for more details about the changes introduced by this release.
 
   Note: it is technically possible for providers to keep using v1beta1 types from CAPI v1.11, but this is 
-  not recommanded (this approach was not tested during the implementation, we don't know if there are road blockers). 
+  not recommended (this approach was not tested during the implementation, we don't know if there are road blockers). 
 
 - If providers are using Conditions from Cluster API resources, e.g. by looking at the ControlPlaneInitialized condition
   on the Cluster object, we highly recommend providers to use new conditions instead of old ones.