Update configure-storage-policy.md

Author: LHL407

articles/azure-vmware/configure-storage-policy.md

@@ -154,10 +154,10 @@ Keep the following information in mind:
    | **vSANIOLimit** | Sets limit on allowed input/output (IO). <br>- The default value is unset. <br>- Valid values are `0` to `2147483647`. <br>- Input/output operations per second (IOPS) limit for the policy. |
    | **vSANDiskStripesPerObject** | The number of hard disk drives (HDDs) across which each replica of a storage object is striped. <br>- The default value is `1`. Valid values are `1` to `12`. <br>- A value higher than `1` might result in better performance (for example, when flash read cache misses need to get serviced from HDD), but also results in a higher use of system resources. |
    | **vSANObjectSpaceReservation** | Object reservation. <br>- The default value is `0`.  <br>- Valid values are `0` to `100`. <br>- `0` = thin provision <br>- `100` = thick provision|
-   | **VMEncryption** | Sets VM encryption. <br>- The default value is `None`.  <br>- Valid values are `None`, `Pre-IO`, `Post-IO`. <br>- Pre-IO allows virtual IO (VAIO) filtering solutions to capture data before VM encryption. <br>- Post-IO allows VAIO filtering solutions to capture data after VM encryption. |
-   | **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- The default value is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, `R1FTT3` <br>- `None` = No data redundancy<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring)<br>- `R1FTT2` = 2 failures - `RAID-1` (Mirroring)<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring)<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding),<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding) <br>- No data redundancy options aren't covered under Microsoft's SLA.|
-   | **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>-  The default value is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, `NoneStretch`  <br>- `None` = No site redundancy. Recommended option for nonstretch clusters. Not recommended for stretch clusters)  <br>- `Dual` = Dual site redundancy. Recommended option for stretch clusters.  <br>- `Preferred` = No site redundancy - keep data on Preferred (stretched cluster)  <br>- `Secondary` = No site redundancy -  Keep data on Secondary Site (stretched cluster)  <br>- `NoneStretch` = No site redundancy - Not Recommended (https://kb.vmware.com/s/article/88358)|
-   | **Description** | Description of the storage policy you're creating, free form text. |
+   | **VMEncryption** | Sets VM encryption. <br>- The default value is `None`.  <br>- Valid values are `None`, `Pre-IO`, and `Post-IO`. <br>- Pre-IO allows virtual IO (VAIO) filtering solutions to capture data before VM encryption. <br>- Post-IO allows VAIO-filtering solutions to capture data after VM encryption. |
+   | **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- The default value is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, and `R1FTT3` <br>- `None` = No data redundancy<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring)<br>- `R1FTT2` = 2 failures - `RAID-1` (mirroring)<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring)<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding),<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding) <br>- The 'None' (no data redundancy) option isn't covered under Microsoft's SLA.|
+   | **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>-  The default value is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, and `NoneStretch`  <br>- `None` = No site redundancy. This option is recommended for nonstretch clusters and not recommended for stretch clusters.  <br>- `Dual` = dual site redundancy. This option is recommended for stretch clusters.  <br>- `Preferred` = no site redundancy - Keep data on Preferred (stretched cluster).  <br>- `Secondary` = No site redundancy -  Keep data on Secondary Site (stretched cluster).  <br>- `NoneStretch` = No site redundancy - not recommended. (https://kb.vmware.com/s/article/88358)|
+   | **Description** | Description of the storage policy that you're creating, free form text. |
    | **Name** | Name of the storage policy to set. For example, *RAID1 FTT-1*. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *New-AVSStoragePolicy-Exec1*.  |
@@ -175,7 +175,7 @@ Run the `Remove-AVSStoragePolicy` cmdlet to specify the default storage policy f
 
    | **Field** | **Value** |
    | --- | --- |
-   | **Name** | Name of the storage Policy. Wildcards aren't supported and are stripped. |
+   | **Name** | Name of the storage policy. Wildcards aren't supported and are stripped. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *Remove-AVSStoragePolicy-Exec1*.  |
    | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |