fleet update orchestration doc updates

Author: shashankbarsin

articles/kubernetes-fleet/concepts-update-orchestration.md

@@ -21,9 +21,10 @@ Platform admins managing large number of clusters often have problems with stagi
 * **Update group**: Each update stage contains one or more update groups, which are used to select the member clusters to be updated. Update groups are also used to order the application of updates to member clusters. Within an update stage, updates are applied to all the different update groups in parallel; within an update group, member clusters update sequentially. Each member cluster of the fleet can only be a part of one update group.
 * **Update strategy**: An update strategy describes the update sequence with stages and groups. You can reuse a strategy in your update runs instead of defining the sequence repeatedly in each run.
 
-Currently, the supported update operations on the cluster are upgrades. There are two types of upgrades you can choose from:
+Currently, the supported update operations on the cluster are upgrades. There are three types of upgrades you can choose from:
 
 - Upgrade Kubernetes versions for the Kubernetes control plane and the nodes (which includes upgrading the node images).
+- Upgrade Kubernetes versions for only the control planes of the clusters
 - Upgrade only the node images.
 
 You can specify the target Kubernetes version to upgrade to, but you can't specify the exact target node image versions as the latest available node image versions may vary depending on the region of the cluster (check [release tracker](../aks/release-tracker.md) for more information).

articles/kubernetes-fleet/update-orchestration.md

@@ -54,7 +54,7 @@ Platform admins managing Kubernetes fleets with large number of clusters often h
 
 1. On the page for your Azure Kubernetes Fleet Manager resource, go to the **Multi-cluster update** menu and select **Create**.
 
-1. Choosing **One by one** would result in upgrading the member clusters present in the update run in a sequential manner one-by-one.
+1. Choosing **One by one** upgrades all member clusters of the fleet in sequence one-by-one.
 
     :::image type="content" source="./media/update-orchestration/update-run-one-by-one.png" alt-text="Screenshot of the Azure portal pane for creating update runs that update clusters one by one in Azure Kubernetes Fleet Manager." lightbox="./media/update-orchestration/update-run-one-by-one.png":::
 
@@ -97,7 +97,7 @@ When creating an update run, you have the ability to control the scope of the up
 - `Full` upgrades Kubernetes version for control plane and node pools along with the node images.
 - `NodeImageOnly` only upgrades the node images.
 
-Also, the `--node-image-selection` flag supports choosing the behavior for the target node images used for upgrades in an update run
+Also, `--node-image-selection` flag supports the following values:
 - **Latest**: Updates every AKS cluster in the update run to the latest image available for that cluster in its region.
 - **Consistent**: As it's possible for an update run to have AKS clusters across multiple regions where the latest available node images can be different (check [release tracker](../aks/release-tracker.md) for more information). The update run picks the **latest common** image across all these regions to achieve consistency.
 
@@ -254,7 +254,7 @@ You can define an update run using update stages in order to sequentially order
     - `Full` upgrades Kubernetes version for control plane and node pools along with the node images.
     - `NodeImageOnly` only upgrades the node images.
 
-    Also, the `--node-image-selection` flag supports choosing the behavior for the target node images used for upgrades in an update run
+    Also, `--node-image-selection` flag supports the following values:
     - **Latest**: Updates every AKS cluster in the update run to the latest image available for that cluster in its region.
     - **Consistent**: As it's possible for an update run to have AKS clusters across multiple regions where the latest available node images can be different (check [release tracker](../aks/release-tracker.md) for more information). The update run picks the **latest common** image across all these regions to achieve consistency.