edit pass

Ja-Dunn · Ja-Dunn · commit 9c4056a21b09 · 2022-01-12T13:29:25.000-08:00
diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.yml b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.yml
@@ -21,19 +21,19 @@ sections:
       - question: |
           How many VMs can I have in a scale set?
         answer: |
-          A scale set can have 0 to 1,000 VMs based on platform images, or 0 to 600 VMs based on custom images.
+          A scale set can have 0 to 1,000 virtual machines (VMs) based on platform images, or 0 to 600 VMs based on custom images.
 
       - question: |
           Are data disks supported within scale sets?
         answer: |
-          Yes. A scale set can define an attached data disks configuration that applies to all VMs in the set. For more information, see [Azure scale sets and attached data disks](virtual-machine-scale-sets-attached-disks.md). Other options for storing data include:
+          Yes. A scale set can define the configuration of an attached data disk that applies to all VMs in the set. For more information, see [Azure scale sets and attached data disks](virtual-machine-scale-sets-attached-disks.md). Other options for storing data include:
 
-          * Azure files (SMB shared drives)
+          * Azure Files (SMB shared drives)
           * Azure shared disks
-          * OS drive
+          * Operating system drive
           * Temp drive (local, not backed by Azure Storage)
-          * Azure data service (for example, Azure tables, Azure blobs)
-          * External data service (for example, remote database)
+          * Azure data service (for example, Azure Table Storage or Azure Blob Storage)
+          * External data service (for example, a remote database)
 
       - question: |
           Which Azure regions support scale sets?
@@ -43,12 +43,12 @@ sections:
       - question: |
           How do I create a scale set by using a custom image?
         answer: |
-          Create and capture a VM image, then use that as the source for your scale set. For a tutorial on how to create and use a custom VM image, you can use the [Azure CLI](tutorial-use-custom-image-cli.md) or [Azure PowerShell](tutorial-use-custom-image-powershell.md)
+          Create and capture a VM image, and then use that as the source for your scale set. For a tutorial on how to create and use a custom VM image, you can use the [Azure CLI](tutorial-use-custom-image-cli.md) or [Azure PowerShell](tutorial-use-custom-image-powershell.md).
 
       - question: |
           If I reduce my scale set capacity from 20 to 15, which VMs are removed?
         answer: |
-          By default, virtual machines are removed from the scale set evenly across availability zones (if the scale set is deployed in zonal configuration) and fault domains to maximize availability. VMs with the highest IDs are removed first.
+          By default, virtual machines are removed from the scale set evenly across availability zones (if the scale set is deployed in zonal configuration) and fault domains, to maximize availability. VMs with the highest IDs are removed first.
 
           You can change the order of virtual machine removal by specifying a [scale-in policy](virtual-machine-scale-sets-scale-in-policy.md) for the scale set.
 
@@ -65,30 +65,30 @@ sections:
       - question: |
           Do scale sets work with Azure availability sets?
         answer: |
-          A regional (non-zonal) scale set uses *placement groups*, which act as an implicit availability set with five fault domains and five update domains. Scale sets of more than 100 VMs span multiple placement groups. For more information about placement groups, see [Working with large virtual machine scale sets](virtual-machine-scale-sets-placement-groups.md). An availability set of VMs can exist in the same virtual network as a scale set of VMs. A common configuration is to put control node VMs (which often require unique configuration) in an availability set and put data nodes in the scale set.
+          A regional (non-zonal) scale set uses *placement groups*, which act as an implicit availability set with five fault domains and five update domains. Scale sets of more than 100 VMs span multiple placement groups. For more information about placement groups, see [Working with large virtual machine scale sets](virtual-machine-scale-sets-placement-groups.md). An availability set of VMs can exist in the same virtual network as a scale set of VMs. A common configuration is to put control node VMs (which often require unique configuration) in an availability set, and put data nodes in the scale set.
 
       - question: |
           Do scale sets work with Azure availability zones?
         answer: |
-          Yes! For more information, see the [scale set zone doc](./virtual-machine-scale-sets-use-availability-zones.md).
+          Yes. For more information, see the [scale set zone doc](./virtual-machine-scale-sets-use-availability-zones.md).
 
 
   - name: Autoscale
     questions:
       - question: |
-          What are best practices for Azure Autoscale?
+          What are best practices for Azure autoscale?
         answer: |
-          For best practices for Autoscale, see [Best practices for autoscaling virtual machines](../azure-monitor/autoscale/autoscale-best-practices.md).
+          See [Best practices for autoscaling virtual machines](../azure-monitor/autoscale/autoscale-best-practices.md).
 
       - question: |
           Where do I find metric names for autoscaling that uses host-based metrics?
         answer: |
-          For metric names for autoscaling that uses host-based metrics, see [Supported metrics with Azure Monitor](../azure-monitor/essentials/metrics-supported.md).
+          See [Supported metrics with Azure Monitor](../azure-monitor/essentials/metrics-supported.md).
 
       - question: |
           Are there any examples of autoscaling based on an Azure Service Bus topic and queue length?
         answer: |
-          Yes. For examples of autoscaling based on an Azure Service Bus topic and queue length, see [Azure Monitor autoscaling common metrics](../azure-monitor/autoscale/autoscale-common-metrics.md).
+          Yes. For these examples, see [Azure Monitor autoscaling common metrics](../azure-monitor/autoscale/autoscale-common-metrics.md).
 
           For a Service Bus queue, use the following JSON:
 
@@ -112,7 +112,7 @@ sections:
       - question: |
           Should I autoscale by using host-based metrics or a diagnostics extension?
         answer: |
-          You can create an autoscale setting on a VM to use host-level metrics or guest OS-based metrics.
+          You can create an autoscale setting on a VM to use host-level metrics, or metrics based on a guest operating system.
 
           For a list of supported metrics, see [Azure Monitor autoscaling common metrics](../azure-monitor/autoscale/autoscale-common-metrics.md).
 
@@ -125,24 +125,24 @@ sections:
       - question: |
           How do I set alert rules on a virtual machine scale set?
         answer: |
-          You can create alerts on metrics for virtual machine scale sets via PowerShell or Azure CLI. For more information, see [Azure Monitor PowerShell quickstart samples](../azure-monitor/powershell-samples.md#create-metric-alerts) and [Azure Monitor cross-platform CLI quickstart samples](../azure-monitor/cli-samples.md#work-with-alerts).
+          You can create alerts on metrics for virtual machine scale sets via PowerShell or the Azure CLI. For more information, see [Azure Monitor PowerShell quickstart samples](../azure-monitor/powershell-samples.md#create-metric-alerts) and [Azure Monitor cross-platform CLI quickstart samples](../azure-monitor/cli-samples.md#work-with-alerts).
 
-          The TargetResourceId of the virtual machine scale set looks like this:
+          The `TargetResourceId` of the virtual machine scale set looks like this:
 
-          /subscriptions/yoursubscriptionid/resourceGroups/yourresourcegroup/providers/Microsoft.Compute/virtualMachineScaleSets/yourvmssname
+          */subscriptions/yoursubscriptionid/resourceGroups/yourresourcegroup/providers/Microsoft.Compute/virtualMachineScaleSets/yourvmssname*
 
-          You can choose any VM performance counter as the metric to set an alert for. For more information, see [Guest OS metrics for Resource Manager-based Windows VMs](../azure-monitor/autoscale/autoscale-common-metrics.md#guest-os-metrics-for-resource-manager-based-windows-vms) and [Guest OS metrics for Linux VMs](../azure-monitor/autoscale/autoscale-common-metrics.md#guest-os-metrics-linux-vms) in the [Azure Monitor autoscaling common metrics](../azure-monitor/autoscale/autoscale-common-metrics.md) article.
+          You can choose any VM performance counter as the metric to set an alert for. For more information, see [Guest operating system metrics for Resource Manager-based Windows VMs](../azure-monitor/autoscale/autoscale-common-metrics.md#guest-os-metrics-for-resource-manager-based-windows-vms) and [Guest operating system metrics for Linux VMs](../azure-monitor/autoscale/autoscale-common-metrics.md#guest-os-metrics-linux-vms) in the [Azure Monitor autoscaling common metrics](../azure-monitor/autoscale/autoscale-common-metrics.md) article.
 
       - question: |
           How do I set up autoscale on a virtual machine scale set by using PowerShell?
         answer: |
-          To set up autoscale on a virtual machine scale set by using PowerShell, see [automatically scale a virtual machine scale set](tutorial-autoscale-powershell.md). You can also configure autoscale with the [Azure CLI](tutorial-autoscale-cli.md) and [Azure templates](tutorial-autoscale-template.md)
+          See [automatically scale a virtual machine scale set](tutorial-autoscale-powershell.md). You can also configure autoscale with the [Azure CLI](tutorial-autoscale-cli.md) and [Azure templates](tutorial-autoscale-template.md).
 
 
       - question: |
           If I have stopped (deallocated) a VM, is that VM started as part of an autoscale operation?
         answer: |
-          No. If autoscale rules require additional VM instances as part of a scale set, a new VM instance is created. VM instances that are stopped (deallocated) are not started as part of an autoscale event. However, those stopped (deallocated) VMs may be deleted as part of an autoscale event that scales in the number of instances, the same way that any VM instance may be deleted based on the order of VM instance ID.
+          No. If autoscale rules require additional VM instances as part of a scale set, a new VM instance is created. VM instances that are stopped (deallocated) aren't started as part of an autoscale event. However, those stopped (deallocated) VMs can be deleted as part of an autoscale event that scales in the number of instances, in the same way that any VM instance can be deleted based on the order of VM instance IDs.
 
 
 
@@ -177,22 +177,22 @@ sections:
 
 
       - question: |
-          How do I use self-signed certificates provisioned for Azure Service Fabric Clusters?
+          How do I use self-signed certificates provisioned for Azure Service Fabric clusters?
         answer: |
-          For the latest example use the following Azure CLI statement within Azure shell, read Service Fabrics CLI module Example documentation, which will be printed to stdout:
+          For the latest example, in an Azure shell, use the following Azure CLI statement, which will be printed to stdout:
 
           ```azurecli
           az sf cluster create -h
           ```
 
-          Self-signed certificates can not be used for distributed trust provided by a Certificate Authority, and should not be used for any Service Fabric Cluster intended to host enterprise production solutions; for additional Service Fabric Security guidance, review [Azure Service Fabric Security Best Practices](../security/fundamentals/service-fabric-best-practices.md) and [Service Fabric cluster security scenarios](../service-fabric/service-fabric-cluster-security.md).
+          Self-signed certificates can't be used for distributed trust provided by a certificate authority, and shouldn't be used for any Service Fabric cluster intended to host enterprise production solutions. For additional security guidance, review [Azure Service Fabric security best practices](../security/fundamentals/service-fabric-best-practices.md) and [Service Fabric cluster security scenarios](../service-fabric/service-fabric-cluster-security.md).
 
       - question: |
-          Can I specify an SSH key pair to use for SSH authentication with a Linux virtual machine scale set from a Resource Manager template?
+          For SSH authentication with a Linux virtual machine scale set from a Resource Manager template, can I specify an SSH key pair to use?
         answer: |
-          Yes. The REST API for **osProfile** is similar to the standard VM REST API.
+          Yes. The REST API for `osProfile` is similar to the standard VM REST API.
 
-          Include **osProfile** in your template:
+          Include `osProfile` in your template:
 
           ```json
           "osProfile": {
