Kubernetes fleet - address comments

Author: shashankbarsin

articles/kubernetes-fleet/architectural-overview.md

@@ -20,21 +20,21 @@ Azure Kubernetes Fleet Manager is meant to solve at-scale and multi-cluster prob
 
 Fleet supports joining the following types of existing AKS clusters as member clusters:
 
-1. AKS clusters across same or different resource groups within same subscription
-1. AKS clusters across different subscriptions of the same Azure AD tenant
-1. AKS clusters from different regions but within the same tenant
+* AKS clusters across same or different resource groups within same subscription
+* AKS clusters across different subscriptions of the same Azure AD tenant
+* AKS clusters from different regions but within the same tenant
 
 During preview, you can join up to 20 AKS clusters as member clusters to the same fleet resource.
 
-Once a cluster is joined to a fleet, a MemeberCluster custom resource is created on the fleet.
+Once a cluster is joined to a fleet resource, a MemeberCluster custom resource is created on the fleet.
 
 The member clusters can be viewed by running the following command:
 
 ```bash
 kubectl get crd memberclusters.fleet.azure.com -o yaml
 ```
 
-The complete specification of the MemberCluster fleet can be viewed by running the following command:
+The complete specification of the `MemberCluster` custom resource can be viewed by running the following command:
 
 ```bash
 kubectl get crd memberclusters -o yaml
@@ -76,7 +76,7 @@ Fleet can be used to set up layer 4 multi-cluster load balancing across workload
 
 For multi-cluster load balancing, Fleet requires target clusters to be using [Azure CNI networking](../aks/configure-azure-cni.md). Azure CNI networking enables pod IPs to be directly addressable on the Azure virtual network so that they can be routed to from the Azure Load Balancer.
 
-The user needs to create `ServiceExport` object on a member cluster to express the intent that the fleet cluster and other member clusters of the same fleet need to be made aware of this service. The ServiceExport itself can be propagated from the fleet cluster to the member cluster using Kubernetes resource propagation feature described above or it can be directly created on the member cluster too. Once this `ServiceExport` resource is created, it results in ServiceImport being created on the fleet and all other member clusters to build the awareness of this service. 
+The ServiceExport itself can be propagated from the fleet cluster to a member cluster using the Kubernetes resource propagation feature describe above, or it can be created directly on the member cluster. Once this ServiceExport resource is created, it results in a ServiceImport being created on the fleet cluster and all other member clusters to build the awareness of the service
 
 The user can then create a `MultiClusterService` custom resource to indicate that they want to set up Layer 4 multi-cluster load balancing. This `MultiClusterService` results in the member cluster mapped Azure Load Balancer being configured to load balance incoming traffic across endpoints of this service on multiple member clusters.
 

articles/kubernetes-fleet/faq.md

@@ -16,11 +16,11 @@ ms.topic: conceptual
 
 Azure Kubernetes Service (AKS) simplifies deploying a managed Kubernetes cluster in Azure by offloading the operational overhead to Azure. As a hosted Kubernetes service, Azure handles critical tasks, like health monitoring and maintenance. Since the Kubernetes control plane is managed by Azure, you only manage and maintain the agent nodes. You run your actual workloads on the AKS clusters.
 
-Azure Kubernetes Fleet Manager (Fleet) will help you address at-scale and multi-cluster scenarios for Azure Kubernetes Service clusters. Fleet only provides a group representation for your AKS clusters and helps users with orchestrating Kubernetes resource propagation and multi-cluster load balancing. User workloads can't be run on the Fleet's Kubernetes cluster itself. 
+Azure Kubernetes Fleet Manager (Fleet) will help you address at-scale and multi-cluster scenarios for Azure Kubernetes Service clusters. Azure Kubernetes Fleet Manager only provides a group representation for your AKS clusters and helps users with orchestrating Kubernetes resource propagation and multi-cluster load balancing. User workloads can't be run on the fleet cluster itself. 
 
-## Creation of AKS clusters from fleet
+## Creation of AKS clusters from fleet resource
 
-The current preview of Azure Kubernetes Fleet Manager resource supports joining only existing AKS clusters as member. Creation and lifecycle management of new AKS clusters from fleet is in the [roadmap](https://aka.ms/fleet/roadmap).
+The current preview of Azure Kubernetes Fleet Manager resource supports joining only existing AKS clusters as member. Creation and lifecycle management of new AKS clusters from fleet cluster is in the [roadmap](https://aka.ms/fleet/roadmap).
 
 ## Number of clusters
 
@@ -36,7 +36,7 @@ Fleet supports joining the following types of AKS clusters as member clusters:
 
 ## Relationship to Azure-Arc enabled Kubernetes
 
-The current preview of Azure Kubernetes Fleet Manager resource supports joining only AKS clusters as member clusters. Support for joining member clusters to the Fleet resource is in the [roadmap](https://aka.ms/fleet/roadmap).
+The current preview of Azure Kubernetes Fleet Manager resource supports joining only AKS clusters as member clusters. Support for joining member clusters to the fleet resource is in the [roadmap](https://aka.ms/fleet/roadmap).
 
 ## Regional or global