Updated the author name

Author: BanoFarha

articles/azure-arc/system-center-virtual-machine-manager/set-up-and-manage-self-service-access-scvmm.md

@@ -18,7 +18,7 @@ Once your SCVMM resources are enabled in Azure, as a final step, provide your te
 ## Prerequisites
 
 - Your SCVMM instance must be connected to Azure Arc.
-- Your SCVMM resources such as virtual machines, clouds, VM networks and VM templates must be Azure enabled.
+- Your SCVMM resources such as virtual machines, clouds, VM networks, and VM templates must be Azure enabled.
 - You must have **User Access Administrator** or **Owner** role at the scope (resource group/subscription) to assign roles to other users.
 
 ## Provide access to use Arc-enabled SCVMM resources

articles/azure-arc/vmware-vsphere/azure-arc-agent.md

@@ -51,7 +51,7 @@ Installing the Connected Machine agent for Window applies the following system-w
     | %ProgramFiles%\AzureConnectedMachineAgent | azcmagent CLI and instance metadata service executables.|
     | %ProgramFiles%\AzureConnectedMachineAgent\ExtensionService\GC | Extension service executables.|
     | %ProgramFiles%\AzureConnectedMachineAgent\GCArcService\GC | Guest configuration (policy) service executables.|
-    | %ProgramData%\AzureConnectedMachineAgent | Configuration, log and identity token files for azcmagent CLI and instance metadata service.|
+    | %ProgramData%\AzureConnectedMachineAgent | Configuration, log, and identity token files for azcmagent CLI and instance metadata service.|
     | %ProgramData%\GuestConfig | Extension package downloads, guest configuration (policy) definition downloads, and logs for the extension and guest configuration services.|
     | %SYSTEMDRIVE%\packages | Extension package executables. |
 
@@ -198,7 +198,7 @@ Metadata information about a connected machine is collected after the Connected
 * Cluster resource ID (for Azure Stack HCI nodes)
 * Hardware manufacturer
 * Hardware model
-* CPU family, socket, physical core and logical core counts
+* CPU family, socket, physical core, and logical core counts
 * Total physical memory
 * Serial number
 * SMBIOS asset tag

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -95,7 +95,7 @@ You need a Windows or Linux machine that can access both your vCenter Server ins
 
 11. Provide a name for your vCenter Server instance in Azure. For example: **contoso-nyc-vcenter**.
 
-12. You may choose to **Enable Kubernetes Service on VMware [Preview]**. If you choose to do so, please ensure you update the namespace of your custom location to "default" in the onboarding script: $customLocationNamespace = ("default".ToLower() -replace '[^a-z0-9-]', ''). For more details about this update, refer to the [known issues from AKS on VMware (preview)](/azure/aks/hybrid/aks-vmware-known-issues)
+12. You can choose to **Enable Kubernetes Service on VMware [Preview]**. If you choose to do so, please ensure you update the namespace of your custom location to "default" in the onboarding script: $customLocationNamespace = ("default".ToLower() -replace '[^a-z0-9-]', ''). For more details about this update, refer to the [known issues from AKS on VMware (preview)](/azure/aks/hybrid/aks-vmware-known-issues)
 
 13. Select **Next: Download and run script**.
 

articles/azure-arc/vmware-vsphere/quick-start-create-a-vm.md

@@ -59,7 +59,7 @@ Once your administrator has connected a VMware vCenter to Azure, represented VMw
 
 10. (Optional) Add tags to the VM resource if necessary.
 
-11. Select **Create** after reviewing all the properties.  It should take a few minutes to create the VM.
+11. Select **Create** after reviewing all the properties. It should take a few minutes to create the VM.
 
 ## Next steps