language edits

Author: jobingeorge-microsoft

articles/azure-vmware/architecture-private-clouds copy.md

@@ -27,13 +27,13 @@ Host remediation involves replacing the faulty node with a new healthy node in t
 AVS undertakes periodic maintenance of the private cloud and this includes security patches, minor & major updates to VMware software stack.
 
 The following actions are always recommended for ensuring host maintenance operations are carried out successfully:
-1.	**vSAN storage utilization:** To maintain Service Level Agreement (SLA), ensure that your vSphere cluster's storage space utilization remains below 75%. If the utilization exceeds 75%, upgrades may take than expected or fail entirely. If your storage utilization exceeds 70%, consider adding a node to expand the cluster and prevent potential downtime during upgrades.
+1.	**vSAN storage utilization:** To maintain Service Level Agreement (SLA), ensure that your vSphere cluster's storage space utilization remains below 75%. If the utilization exceeds 75%, upgrades may take longer than expected or fail entirely. If your storage utilization exceeds 75%, consider adding a node to expand the cluster and prevent potential downtime during upgrades.
 2.	**Distributed Resource Scheduler (DRS) rules:** DRS VM-VM anti-affinity rules must be configured in a way to have at least (N+1) hosts in the cluster, where N is the number of VMs part of DRS rule.
 3.	**Failures To Tolerate (FTT) violation:** To prevent data loss, change VMs configured with a vSAN storage policy for Failures to Tolerate (FTT) of 0 to a vSAN storage policy compliant with [Microsoft SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) (FTT=1 for up to 5 hosts in a cluster and FTT=2 for 6 or more hosts in a cluster) and ensure host maintenance operations can carried out seamlessly.
 4.	**Remove VM CD-ROM mounts:** VMs mounted with “Emulate mode” CD-ROMs will block host maintenance. Ensure CD-ROMs are mounted in “Passthrough mode”.
-5.	**Serial/parallel port or external device:** If you are using an image file (ISO, FLP, etc), ensure that it is accessible from all ESXi hosts in the cluster. Store the files on a datastore that are shared between all ESXi Servers that will participate in the vMotion of the virtual machine. Refer to [this Broadcom KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) for more information.
-6.	**Orphaned VMs:** In the case of an orphaned virtual machine, the VM needs to be either re-registered if possible (if it has not been deleted) or removed from inventory. Refer to [this Broadcom KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information.
-7.	**SCSI shared controller:** When using SCSI bus sharing use with bus type as “Physical” for VMs. VMs connected to Virtual SCSCI controllers will be powered-off. Refer to [this Broadcom KB article](https://knowledge.broadcom.com/external/article?legacyId=2147661) for more information.
+5.	**Serial/parallel port or external device:** If you are using an image file (ISO, FLP, etc), ensure that it is accessible from all ESXi hosts in the cluster. Store the files on a datastore that are shared between all ESXi Servers that will participate in the vMotion of the virtual machine. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/324829/vmotion-fails-with-the-compatibility-err.html) for more information.
+6.	**Orphaned VMs:** In the case of an orphaned virtual machine, the VM needs to be either re-registered if possible (if it has not been deleted) or removed from inventory. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article/312831/virtual-machines-appear-as-invalid-or-or.html) for more information.
+7.	**SCSI shared controller:** When using SCSI bus sharing use with bus type as “Physical” for VMs. VMs connected to Virtual SCSCI controllers will be powered-off. Refer to [Broadcom KB article](https://knowledge.broadcom.com/external/article?legacyId=2147661) for more information.
 8.	**Third-party VMs & applications:** For third-party VMs & applications:
     1. Ensure that third-party solutions deployed on AVS are compliant and do not interfere with maintenance operations.   
     2. Ensure that the VM isn’t installed with a VM-Host “Must run” DRS rule. Additionally, verify that these applications are compatible with upcoming versions of the VMware stack.