review updates

Author: parameshbabu

AKS-Hybrid/aks-edge-howto-multi-node-deployment.md

@@ -27,7 +27,7 @@ You can generate the parameters needed to create a scalable cluster using the fo
 New-AksEdgeConfig -DeploymentType ScalableCluster -outFile .\aksedge-config.json | Out-Null
 ```
 
-This creates a configuration file called **aksedge-config.json** which includes the configuration needed to create a scalable cluster with a Linux node. The file is created in your current working directory. See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for detailed description of the configuration parameters (such as Proxy settings).
+This creates a configuration file called **aksedge-config.json** which includes the configuration needed to create a scalable cluster with a Linux node. The file is created in your current working directory. See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for detailed description of the configuration parameters (such as proxy settings).
 
 See the following examples for more options for creating the configuration file.
 

AKS-Hybrid/aks-edge-howto-single-node-deployment.md

@@ -26,7 +26,7 @@ New-AksEdgeConfig -DeploymentType SingleMachineCluster -outFile .\aksedge-config
 
 This command creates a configuration file called **aksedge-config.json** that includes the configuration needed to create a single-machine cluster with a Linux node. The file is created in your current working directory. See the following examples for more options for creating the configuration file.
 
-See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for detailed description of the configuration parameters.
+See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for a detailed description of the configuration parameters.
 
 The key parameters for single machine deployment are:
 
@@ -91,7 +91,7 @@ New-AksEdgeDeployment -JsonConfigString ($jsonObj | ConvertTo-Json -Depth 4)
 ```
 
 > [!TIP]
-> See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for all available options, including network settings such as Proxy settings.
+> See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for all available options, including network settings such as proxy settings.
 
 ### Create a simple cluster with NodePort service
 

AKS-Hybrid/aks-edge-quickstart.md

@@ -13,7 +13,7 @@ ms.custom: template-how-to
 This quickstart describes how to set up an Azure Kubernetes Service (AKS) Edge Essentials single-machine K3S Linux-only cluster.
 
 > [!NOTE]
-> The purpose of this quickstart script is to ease the evaluation process and requires higher level credentials for one-time setup of Azure subscription. This is not intended for production use.
+> The purpose of this quickstart script is to ease the evaluation process. This script requires higher level credentials for a one-time setup of the Azure subscription. This is not intended for production use.
 
 ## Prerequisites
 
@@ -57,7 +57,7 @@ This script automates the following steps:
   - Connects the deployed cluster to Arc for connected Kubernetes.
 
 > [!TIP]
-> You can modify the `$aksedgeConfig` json content in the `AksEdgeQuickStart` script for any additional options. See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for available options.
+> You can modify the `$aksedgeConfig` json content in the `AksEdgeQuickStart` script for any additional options. For available options, see [Deployment JSON configuration](aks-edge-deployment-config-json.md).
 
 ## Step 2: Deploy AKS Edge Essentials
 

AKS-Hybrid/scale-requirements.md

@@ -21,10 +21,10 @@ This article describes the maximum and minimum supported scale count for AKS on
 | Scale item   | Minimum  | Maximum |
 |--------------|----------|---------|
 | Number of physical nodes in an Azure Stack HCI cluster  | 1  | 16 |
-| Count of control plane nodes `(Allowed values: 1, 3, and 5)`   | 1 | 5 |
+| Count of control plane nodes (Allowed values are 1, 3, and 5)  | 1 | 5 |
 | Number of nodes in default node pool created during cluster create  | 1 | 200 |
 | Number of node pools in an AKS cluster  | 1  | 16  |
-| Number of nodes in a node pool (Empty node pools not supported)  | 1 | 64 |
+| Number of nodes in a node pool (empty node pools not supported)  | 1 | 64 |
 | Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
 | Number of AKS clusters per Azure Stack HCI cluster | 0| 32 |
 
@@ -42,7 +42,7 @@ This article describes the maximum and minimum supported scale count for AKS on
 | System Role                     | VM Size                                | Memory, CPU          |
 |---------------------------------|----------------------------------------|----------------------|
 | AKS Arc control plane nodes  | Standard_A4_v2                         | 8-GB memory, 4 vcpu  |
-| AKS Arc HA Proxy VM          | Standard_A4_v2. `Fixed size.`      | 8-GB memory, 4 vcpu  |
+| AKS Arc HA Proxy VM          | Standard_A4_v2. (This size is fixed and can't be changed) | 8-GB memory, 4 vcpu  |
 | AKS Arc Linux worker node    | Standard_K8S3_v1                       | 6-GB memory, 4 vcpu  |
 | AKS Arc Windows worker node  | Standard_K8S3_v1                       | 6-GB memory, 4 vcpu  |