Minor improvements

docs/src/capi/explanation/in-place-upgrades.md

@@ -2,7 +2,7 @@
 
 Regularly upgrading the Kubernetes version of the machines in a cluster 
 is important. While rolling upgrades a popular strategy, certain situations 
-may demand in-place upgrades:
+will require in-place upgrades:
 
 - Resource constraints (i.e. cost of additional machines).
 - Expensive manual setup process for nodes.
@@ -139,12 +139,9 @@ in-place upgrades:
 
 #### (Optional) Locking The Upgrade Process
 
-The controllers ensure that only a limited 
-number of machines are going to get upgraded at the same time. An example 
-might be upgrading control plane machines. If multiple nodes become 
-unavailable due to getting upgraded, quorum might be lost, severe 
-downtime might be experienced, or the system might end up in an undesirable 
-state that is very costly to get out of.
+The controllers ensure that only a single machine 
+is going to get upgraded at the same time.
+This is to prevent undesirable situations like quorum loss or severe downtimes. 
 
 {{product}} CAPI uses a lock to ensure only 1 control plane machine is 
 getting upgraded at a given time.