edit pass

Author: Ja-Dunn

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.yml

@@ -398,7 +398,7 @@ sections:
       - question: |
           Is there a virtual machine scale set template example that integrates with Azure Monitor Logs?
         answer: |
-          For a virtual machine scale set template example that integrates with Azure Monitor logs, see the second example in [Deploy an Azure Service Fabric cluster and enable monitoring by using Azure Monitor Logs](https://github.com/krnese/AzureDeploy/tree/master/OMS/MSOMS/ServiceFabric).
+          For a virtual machine scale set template example that integrates with Azure Monitor Logs, see the second example in [Deploy an Azure Service Fabric cluster and enable monitoring by using Azure Monitor Logs](https://github.com/krnese/AzureDeploy/tree/master/OMS/MSOMS/ServiceFabric).
 
       - question: |
           How do I add an extension to all VMs in my virtual machine scale set?
@@ -760,7 +760,7 @@ sections:
           The main difference is that `deallocate` doesn't delete the virtual hard disks (VHDs). There are storage costs associated with running `stop deallocate`. You might use one or the other for one of the following reasons:
 
           - You want to stop paying compute costs, but you want to keep the disk state of the VMs.
-          - You want to start a set of VMs more quickly than you could scale out a virtual machine scale set.
+          - You want to start a set of VMs more quickly than you can scale out a virtual machine scale set.
             - Related to this scenario, you might have created your own autoscale engine and want a faster end-to-end scale.
           - You have a virtual machine scale set that is unevenly distributed across fault domains or update domains. This might be because you selectively deleted VMs, or because VMs were deleted after overprovisioning. Running `stop deallocate` followed by `start` on the virtual machine scale set evenly distributes the VMs across fault domains or update domains.