Minor update.

Author: MaryMichael-MS

articles/migrate/troubleshoot-assessment-faq.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot assessments FAQ in Azure Migrate
-description: FAQs for Troubleshooring assessments in Azure Migrate.
+description: FAQs for Troubleshooting assessments in Azure Migrate.
 author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
@@ -31,7 +31,7 @@ For **Performance-based** assessment, the assessment report export says 'Percent
 - If the VMs are powered on for the duration for which you're creating the assessment.
 - If only memory counters are missing and you're trying to assess Hyper-V VMs, check if you have dynamic memory enabled on these VMs. Because of a known issue, currently the Azure Migrate appliance can't collect memory utilization for such VMs.
 - If all of the performance counters are missing, ensure the port access requirements for assessment are met. Learn more about the port access requirements for [VMware](./migrate-support-matrix-vmware.md#port-access-requirements), [Hyper-V](./migrate-support-matrix-hyper-v.md#port-access), and [physical](./migrate-support-matrix-physical.md#port-access) assessments.
-If any of the performance counters are missing, Azure Migrate: Discovery and assessment fall back to the allocated cores/memory on-premises and recommends a VM size accordingly.
+If any of the performance counters are missing, Azure Migrate: Discovery and assessment fall back to the allocated cores/memory on-premises and recommend a VM size accordingly.
 
 ## Why is performance data missing for some or all servers in my Azure VM or Azure VMware Solution assessment report?
 
@@ -80,7 +80,7 @@ By design, in Hyper-V if maximum memory provisioned is less than what is require
 
 An Azure VM assessment currently considers the operating system license cost only for Windows servers. License costs for Linux servers aren't currently considered.
 
-## How does performance-based sizing work in an Azure VM assessment?
+## How performance-based sizing works in an Azure VM assessment?
 
 An Azure VM assessment continuously collects performance data of on-premises servers and uses it to recommend the VM SKU and disk SKU in Azure. [Learn more](concepts-assessment-calculation.md#calculate-sizing-performance-based) about how performance-based data is collected.
 

articles/migrate/troubleshoot-assessment-supported-scenarios.md

@@ -28,7 +28,7 @@ For servers in a VMware environment, use the VMware Hybrid Cloud Extension (HCX)
 
 ### Cause
 
-In the case of VMware and Hyper-V VMs, an Azure VM assessment marks Linux VMs as **conditionally ready** because of a known gap. 
+In the case of VMware and Hyper-V VMs, an Azure VM assessment marks Linux VM as **conditionally ready** because of a known gap. 
 
 - The gap prevents it from detecting the minor version of the Linux OS installed on the on-premises VMs.
 - For example, for RHEL 6.10, currently an Azure VM assessment detects only RHEL 6 as the OS version. This behavior occurs because the vCenter Server and the Hyper-V host don't provide the kernel version for Linux VM operating systems.

articles/migrate/troubleshoot-assessment.md

@@ -487,7 +487,7 @@ Unable to determine ISAPI filters present for all of the site configuration.
 
 #### Recommended Action
 
-Automatic configuration of custom ISAPI filters isn't supported. Fix all configuration errors and confirm that all site content locations are accessible to the administrators group.
+Automatic configuration of custom ISAPI filters isn't supported. Fix all configuration errors and confirm that all site content locations are accessible to the administrator's group.
 
 ### Error: Location tag check