Address feedback

Author: fabriziopandini

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

@@ -67,7 +67,7 @@ The following proposal have been implemented in the Cluster API v1.12 release:
 - The new `spec.taint` field has been added.
 - The `HealthCheckSucceeded` condition reports a new `UnhealthyMachine` reason when `unhealthyMachineConditions` checks fail 
 - The `UpToDate` condition reports a new `Updating` reason when a machine is performing in-place updates
-- The new `Updating` condition has been added. It reports status `true` when a machine is performing in-place updates. 
+- The new `Updating` condition has been added. It reports status `True` when a machine is performing in-place updates 
   - Supported reasons are `NotUpdating`, `InPlaceUpdating`, `InPlaceUpdateFailed`
 - The field `status.phases` reports a new `Updating` phase when a machine is performing in-place updates
 
@@ -113,26 +113,26 @@ KubeadmControlPlaneTemplate `spec.template.spec` has been aligned to changes in
 ## Runtime hooks Changes
 
 - Lifecycle hooks
-  - The request message for the `BeforeClusterUpgrade` hook has been extended to include info about the upgrade plan.
-  - The new `BeforeControlPlaneUpgrade` hook has been added; the hook is called before each "upgrade control plane" step;
-  - The request message for the `AfterControlPlaneUpgrade` hook have been extended to include info about the upgrade plan. 
-    - The `AfterControlPlaneUpgrade` hook is now called after each "upgrade control plane" step.
+  - The request message for the `BeforeClusterUpgrade` hook has been extended to include info about the upgrade plan
+  - The new `BeforeControlPlaneUpgrade` hook has been added; the hook is called before each "upgrade control plane" step
+  - The request message for the `AfterControlPlaneUpgrade` hook have been extended to include info about the upgrade plan 
+    - The `AfterControlPlaneUpgrade` hook is now called after each "upgrade control plane" step
   - The new `BeforeWorkersUpgrade`, `AfterWorkersUpgrade` hooks have been added; the hooks are called before/after each "upgrade workers" step
   - The `AfterClusterUpgrade` has been transformed into a blocking hook (it blocks next upgrade)
 - Upgrade plan hooks (new!)
   - The new `GenerateUpgradePlan` has been added; the hook is called by the topology controller when it is required 
-    to compute the upgrade plan for a cluster.
+    to compute the upgrade plan for a cluster
 - In-place extension hooks (new!)
   - the new `CanUpdateMachine` hook has been added; the hook is called by the KubeadmControlPlane controller to perform the 
-    "can update in-place" decision for a machine that is not up-to-date.
+    "can update in-place" decision for a machine that is not up-to-date
   - the new `CanUpdateMachineSet` hook has been added; the hook is called by the MachineDeployment controller to perform the 
-    "can update in-place" decision for a MachineSet that is not up-to-date.
-  - the new `UpdateMachine` hook has been added; the hook is called by the Machine controller to perform in-place upgrades.
-- Some optimization have been implemented to ensure that hooks are called only when necessary. 
+    "can update in-place" decision for a MachineSet that is not up-to-date
+  - the new `UpdateMachine` hook has been added; the hook is called by the Machine controller to perform in-place upgrades
+- Some optimization have been implemented to ensure that hooks are called only when necessary 
   - e.g. if a lifecycle hook response, e.g. the `BeforeClusterUpgradeResponse`, informs CAPI to retry after X seconds, 
     CAPI is going to not call the runtime extension until X expires, no matter if the underlying controller reconciles 
-    one or more times in the between.
-  - `GenerateUpgradePlan`, `CanUpdateMachine`, `CanUpdateMachineSet` hooks will use slightly different caching strategy.
+    one or more times in the between
+  - `GenerateUpgradePlan`, `CanUpdateMachine`, `CanUpdateMachineSet` hooks will use slightly different caching strategy
 
 ## Cluster API Contract changes
 
@@ -146,7 +146,7 @@ KubeadmControlPlaneTemplate `spec.template.spec` has been aligned to changes in
 
 ## Deprecation
 
-- The following reasons for the `TopologyReconciled` condition on the `Cluster`object are now deprecated
+- The following reasons for the `TopologyReconciled` condition on the `Cluster` object are now deprecated
   - `ControlPlaneUpgradePending` 
   - `MachineDeploymentsCreatePending`
   - `MachineDeploymentsUpgradePending`
@@ -180,7 +180,7 @@ KubeadmControlPlaneTemplate `spec.template.spec` has been aligned to changes in
         will implement temporarily compatibility with the deprecated v1beta1 version of the Cluster API contract
           - Compatibility is only intended to ease the transition for providers, and it has some limitations; please
             read details in following paragraphs.
-      - Compatibility support for the v1beta1 version of the Cluster API contract will be removed tentatively in August 2026
+      - Compatibility support for the v1beta1 version of the Cluster API contract will be removed tentatively in August 2026.
       - After compatibility support for the v1beta1 version of the Cluster API contract is removed, providers
         which are implementing the v1beta1 contract will stop to work (they will work only with older versions of Cluster API).