Apply suggestions from code review

Co-authored-by: Erin Schaffer <[email protected]>

Author: shashankbarsin

articles/kubernetes-fleet/concepts-choosing-fleet.md

@@ -14,11 +14,11 @@ This article provides an overview of the various Azure Kubernetes Fleet Manager
 
 ## Fleet types
 
-Kubernetes Fleet can be created with or without a hub cluster. Hub cluster is a managed Azure Kubernetes Service (AKS) cluster that acts as a hub to store and propagate Kubernetes resources. 
+A Kubernetes Fleet resource can be created with or without a hub cluster. A hub cluster is a managed Azure Kubernetes Service (AKS) cluster that acts as a hub to store and propagate Kubernetes resources. 
 
-The following table compares the scenarios enabled by the hub cluster.
+The following table compares the scenarios enabled by the hub cluster:
 
-| Capability | Kubernetes Fleet without hub cluster | Kubernetes Fleet with hub cluster |
+| Capability | Kubernetes Fleet resource without hub cluster | Kubernetes Fleet resource with hub cluster |
 |----|----|----|
 |**Hub cluster hosting**|<span class='red-x'>&#10060;</span>|<span class='green-check'>&#9989;</span>|
 |**Member cluster limit**|Up to 100 clusters|Up to 20 clusters|
@@ -30,21 +30,21 @@ The following table compares the scenarios enabled by the hub cluster.
 
 ## Kubernetes Fleet resource without hub clusters
 
-Without a hub cluster, Fleet acts solely as a grouping entity in Azure Resource Manager. Certain scenarios, such as update runs, don't require a Kubernetes API and thus don't require a hub cluster. To take full advantage of all the features available, you need a Kubernetes Fleet resource with a hub cluster.
+Without a hub cluster, Kubernetes Fleet acts solely as a grouping entity in Azure Resource Manager (ARM). Certain scenarios, such as update runs, don't require a Kubernetes API and thus don't require a hub cluster. To take full advantage of all the features available, you need a Kubernetes Fleet resource with a hub cluster.
 
-For more information, see [Create a hubless fleet][create-fleet-without-hub].
+For more information, see [Create a Kubernetes Fleet resource without a hub cluster][create-fleet-without-hub].
 
 ## Kubernetes Fleet resource with hub clusters
 
-A Kubernetes Fleet resource with hub cluster has an associated AKS-managed cluster, which is used to store configuration for workload orchestration and layer-4 load balancing.
+A Kubernetes Fleet resource with a hub cluster has an associated AKS-managed cluster, which is used to store the configuration for workload orchestration and layer-4 load balancing.
 
-Upon the creation of a A Kubernetes Fleet resource with hub cluster, a hub AKS cluster is automatically created in the same subscription under a managed resource group named `FL_*`. To improve reliability, hub clusters are locked down by denying any user initiated mutations to the corresponding AKS clusters (under the Fleet-managed resource group `FL_*`) and their underlying Azure resources (under the AKS-managed resource group `MC_FL_*`), such as VMs, via Azure deny assignments. Control plane operations, such as changing the hub cluster's configuration through Azure Resource Manager (ARM) or deleting the cluster entirely, are denied. Data plane operations, such as connecting to the hub cluster's Kubernetes API server in order to configure workload orchestration, are not denied.
+Upon the creation of a Kubernetes Fleet resource with a hub cluster, a hub AKS cluster is automatically created in the same subscription under a managed resource group that begins with `FL_`. To improve reliability, hub clusters are locked down by denying any user-initiated mutations to the corresponding AKS clusters (under the Fleet-managed resource group `FL_`) and their underlying Azure resources (under the AKS-managed resource group `MC_FL_*`), such as virtual machines (VMs), via Azure deny assignments. Control plane operations, such as changing the hub cluster's configuration through Azure Resource Manager (ARM) or deleting the cluster entirely, are denied. Data plane operations, such as connecting to the hub cluster's Kubernetes API server in order to configure workload orchestration, are not denied.
 
 Hub clusters are exempted from [Azure policies][azure-policy-overview] to avoid undesirable policy effects upon hub clusters.
 
 ### Network access modes for hub cluster
 
-For Kubernetes Fleet resource with hub cluster, there are two network access modes:
+For a Kubernetes Fleet resource with a hub cluster, there are two network access modes:
 
 - **Public hub clusters** expose the hub cluster to the internet. This means that with the right credentials, anyone on the internet can connect to the hub cluster. This configuration can be useful during the development and testing phase, but represents a security concern, which is largely undesirable in production.
 
@@ -57,7 +57,7 @@ Some other details to consider:
 - Whether you choose a public or private hub, the type can't be changed after creation.
 - When using an AKS private cluster, you have the ability to configure fully qualified domain names (FQDNs) and FQDN subdomains. This functionality doesn't apply to the private hub cluster of the Kubernetes Fleet resource.
 - When you connect to a private hub cluster, you can use the same methods that you would use to [connect to any private AKS cluster][aks-private-cluster-connect]. However, connecting using AKS command invoke and private endpoints aren't currently supported.
-- When you use private hub clusters, you're required to specify the subnet in which the Fleet hub cluster's node VMs reside. This process differs slightly from the AKS private cluster equivalent. For more information, see [create a Kubernetes Fleet resource with a private hub cluster][create-private-hub-cluster].
+- When you use private hub clusters, you're required to specify the subnet in which the Kubernetes Fleet hub cluster's node VMs reside. This process differs slightly from the AKS private cluster equivalent. For more information, see [create a Kubernetes Fleet resource with a private hub cluster][create-private-hub-cluster].
 
 
 ## Next steps

articles/kubernetes-fleet/concepts-resource-propagation.md

@@ -64,7 +64,7 @@ For more information, see the [`ClusterResourcePlacement` API reference][cluster
 
 When creating the `ClusterResourcePlacement`, the following affinity types can be specified:
 
-- **requiredDuringSchedulingIgnoredDuringExecution**: As this affinity is of the required type during scheduling, it **filters** the clusters based on their properties
+- **requiredDuringSchedulingIgnoredDuringExecution**: As this affinity is of the required type during scheduling, it **filters** the clusters based on their properties.
 - **preferredDuringSchedulingIgnoredDuringExecution**: As this affinity is only of the preferred type, but is not required during scheduling, it provides preferential ranking to clusters based on properties specified by you such as cost or resource availability.
 
 Multiple placement types are available for controlling the number of clusters to which the Kubernetes resource needs to be propagated:

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

@@ -49,7 +49,7 @@ An update run can be in one of the following states:
 - **NotStarted**: State of the update run before it is started.
 - **Running**: Upgrade is in progress for at least one of the clusters in the update run.
 - **Pending**: 
-  - **Member cluster**: A member cluster can be in the pending state for any of the following reasons and are surfaced under the message field - 
+  - **Member cluster**: A member cluster can be in the pending state for any of the following reasons and are surfaced under the message field.
     - Maintenance window is not open. Message indicates next opening time.
     - Target Kubernetes version is not yet available in the region of the member. Message links to the release tracker so that you can check status of the release across regions.
     - Target node image version is not yet available in the region of the member. Message links to the release tracker so that you can check status of the release across regions.
@@ -64,7 +64,7 @@ An update run can be in one of the following states:
     - When consistent node image is chosen for an upgrade run, if it's not possible to find the target image version for one of the node pools, then upgrade is skipped for that cluster. An example situation for this is when a new node pool with a new VM SKU is added after an update run has started.
   - **Group**:
     - All member clusters were detected as `Skipped` by the system.
-    - You initiated a skip at the group level
+    - You initiated a skip at the group level.
   - **Stage**:
     - All groups in the stage where detected as `Skipped` by the system.
     - You initiated a skip at the stage level.

articles/kubernetes-fleet/intelligent-resource-placement.md

@@ -8,16 +8,16 @@ ms.author: shasb
 ms.service: kubernetes-fleet
 ---
 
-# Intelligent cross-cluster Kubernetes resource placement using Azure Kubernetes Fleet Manager (Preview).
+# Intelligent cross-cluster Kubernetes resource placement using Azure Kubernetes Fleet Manager (Preview)
 
 Application developers often need to deploy Kubernetes resources into multiple clusters. Fleet operators often need to pick the best clusters for placing the workloads based on heuristics such as cost of compute in the clusters or available resources such as memory and CPU. It's tedious to create, update, and track these Kubernetes resources across multiple clusters manually. This article covers how Azure Kubernetes Fleet Manager (Kubernetes Fleet) allows you to address these scenarios using the intelligent Kubernetes resource placement feature.
 
 ## Overview
 
 Kubernetes Fleet provides resource placement capability that can make scheduling decisions based on the following properties:
-- Node count.
-- Cost of compute in target member clusters.
-- Resource (CPU/Memory) availability in target member clusters.
+- Node count
+- Cost of compute in target member clusters
+- Resource (CPU/Memory) availability in target member clusters
 
 [!INCLUDE [preview-callout](./includes/preview/preview-callout.md)]
 
@@ -38,10 +38,10 @@ In each condition you specify:
 * **Name**: Name of the property, which should be in the following format:
 
     ```
-    resources.kubernetes-fleet.io/[CAPACITY-TYPE]-[RESOURCE-NAME]
+    resources.kubernetes-fleet.io/<CAPACITY-TYPE>-<RESOURCE-NAME>
     ```
 
-    `[CAPACITY-TYPE]` is one of `total`, `allocatable`, or `available`, depending on which capacity (usage information) you would like to check against, and `[RESOURCE-NAME]` is the name of the resource (CPU/memory).
+    `<CAPACITY-TYPE>` is one of `total`, `allocatable`, or `available`, depending on which capacity (usage information) you would like to check against, and `<RESOURCE-NAME>` is the name of the resource (CPU/memory).
 
     For example, if you would like to select clusters based on the available CPU capacity of a cluster, the name used in the property selector should be `resources.kubernetes-fleet.io/available-cpu`. For allocatable memory capacity, you can use `resources.kubernetes-fleet.io/allocatable-memory`.
 

articles/kubernetes-fleet/quickstart-create-fleet-and-members.md

@@ -88,7 +88,8 @@ The following output example resembles successful creation of the resource group
 You can create a Fleet resource to later group your AKS clusters as member clusters. When created via Azure CLI, by default, this resource enables member cluster grouping and update orchestration. If the Fleet hub is enabled, other preview features are enabled, such as Kubernetes object propagation to member clusters and L4 service load balancing across multiple member clusters. For more information, see the [conceptual overview of fleet types](./concepts-choosing-fleet.md), which provides a comparison of different fleet configurations.
 
 > [!IMPORTANT]
-> Once a Fleet resource has been created, it's possible to upgrade a Kubernetes Fleet resource without a hub cluster to one with a hub cluster. For Kubernetes Fleet resources with a hub cluster, once private or public has been selected it cannot be changed.
+> Once a Kubernetes Fleet resource has been created, it's possible to upgrade a Kubernetes Fleet resource without a hub cluster to one with a hub cluster. For Kubernetes Fleet resources with a hub cluster, once private or public has been selected it cannot be changed.
+
 
 ### [Kubernetes Fleet resource without hub cluster](#tab/without-hub-cluster)
 

articles/kubernetes-fleet/upgrade-hub-cluster-type.md

@@ -11,7 +11,7 @@ ms.service: kubernetes-fleet
 
 # Upgrade hub cluster type for Azure Kubernetes Fleet Manager resource
 
-In this article, you learn how to upgrade an Azure Kubernetes Fleet Manager (Kubernetes Fleet) resource without any hub cluster to a Kubernetes Fleet resource having a hub cluster. When a Kubernetes Fleet resource is created without a hub cluster, a central Azure Kubernetes Service (AKS) cluster isn't created for the Kubernetes Fleet resource. When a Kubernetes Fleet resource with hub cluster is created, a central and managed AKS cluster is created to enable scenarios such as workload orchestration and layer-4 load balancing.
+In this article, you learn how to upgrade an Azure Kubernetes Fleet Manager (Kubernetes Fleet) resource without a hub cluster to a Kubernetes Fleet resource that has a hub cluster. When a Kubernetes Fleet resource is created without a hub cluster, a central Azure Kubernetes Service (AKS) cluster isn't created for the Kubernetes Fleet resource. When a Kubernetes Fleet resource with a hub cluster is created, a central and managed AKS cluster is created to enable scenarios such as workload orchestration and layer-4 load balancing.
 
 For more information, see [Choosing an Azure Kubernetes Fleet Manager option][concepts-choose-fleet].
 
@@ -20,14 +20,14 @@ For more information, see [Choosing an Azure Kubernetes Fleet Manager option][co
 [!INCLUDE [free trial note](../../includes/quickstarts-free-trial-note.md)]
 - [Install or upgrade Azure CLI](/cli/azure/install-azure-cli) to the latest version.
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- You must have an existing Kubernetes Fleet resource without the hub cluster. The steps in this article show you how to create such a Kubernetes Fleet resource without the hub cluster, but you already have one you can substitute your existing resource.
+- You must have an existing Kubernetes Fleet resource without a hub cluster. The steps in this article show you how to create a Kubernetes Fleet resource without a hub cluster. If you already have one, you can skip the initial setup and begin at [Upgrade hub cluster type for the Kubernetes Fleet resource](#upgrade-hub-cluster-type-for-the-kubernetes-fleet-resource).
 - This article also includes steps on joining member clusters. If you plan to follow along, you need at least one AKS cluster.
 
 
 > [!IMPORTANT]
-> Kubernetes Fleet resources without a hub cluster can be upgraded to fleet resource having a hub cluster. However, a Kubernetes Fleet resource already having a hub cluster can't be downgraded to Kubernetes Fleet resource without hub cluster.
-> All configuration options and settings associated with the hub cluster based Kubernetes Fleet resource are immutable and can't be changed after creation or upgrade time.
-> Upgrading from Kubernetes Fleet without hub cluster to one with a hub cluster can only be done through the Azure CLI. Currently there's no equivalent Azure portal experience.
+> Kubernetes Fleet resources without a hub cluster can be upgraded to a Kubernetes Fleet resource with a hub cluster. However, a Kubernetes Fleet resource that already has a hub cluster can't be downgraded to a Kubernetes Fleet resource without a hub cluster.
+> All configuration options and settings associated with Kubernetes Fleet resource that has a hub cluster are immutable and can't be changed after creation or upgrade time.
+> Upgrading from a Kubernetes Fleet resource without a hub cluster to one with a hub cluster can only be done through the Azure CLI. Currently there's no equivalent Azure portal experience.
 
 ## Initial setup
 
@@ -48,16 +48,16 @@ az group create -n $RG -l $LOCATION
 az fleet create -g $RG -n $FLEET
 
 # Join member cluster to hubless fleet resource
-az fleet member create -n $FLEET_MEMBER -f $FLEET -g $RG --member-cluster-id /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RG/providers/Microsoft.ContainerService/managedClusters/$CLUSTER
+az fleet member create --name $FLEET_MEMBER --fleet-name $FLEET --resource-group $RG --member-cluster-id /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RG/providers/Microsoft.ContainerService/managedClusters/$CLUSTER
 ```
 
 ## Upgrade hub cluster type for the Kubernetes Fleet resource
 
-To upgrade hub cluster type for the Kubernetes Fleet resource, use the `az fleet create` command with the `--enable-hub` flag set. Be sure to include any other relevant configuration options, as the fleet resource will become immutable after this operation is complete.
+To upgrade the hub cluster type for the Kubernetes Fleet resource, use the `az fleet create` command with the `--enable-hub` flag set. Be sure to include any other relevant configuration options, as the fleet resource will become immutable after this operation is complete.
 
 ```azurecli-interactive
-# Upgrade the Kubernetes fleet resource without hub cluster to one with a hub cluster
-az fleet create -n $FLEET -g $RG --enable-hub 
+# Upgrade the Kubernetes fleet resource without a hub cluster to one with a hub cluster
+az fleet create --name $FLEET --resource-group $RG --enable-hub 
 
 ```
 
@@ -115,7 +115,7 @@ For each member cluster that you rejoin to the newly upgraded fleet, view the ou
 
 You need access to the Kubernetes API of the hub cluster. If you don't have access, see [Access the Kubernetes API of the Fleet resource with Azure Kubernetes Fleet Manager](./quickstart-access-fleet-kubernetes-api.md).
 
-To verify that your newly upgraded fleet resource is functioning properly and member clusters joined successfully, confirm that you're able to access the hub cluster's API server using the `kubectl get memberclusters` command.
+To verify that your newly upgraded Kubernetes Fleet resource is functioning properly and that the member clusters joined successfully, confirm that you're able to access the hub cluster's API server using the `kubectl get memberclusters` command.
 
 If successful, your output should look similar to the following example output: