Merge pull request #153721 from shortpatti/patch-4

Update faq.yml

Author: Court72

articles/azure-vmware/faq.yml

@@ -181,7 +181,7 @@ sections:
         answer: Thick provisioning is reserved or pre-allocated storage space.  Thick provisioning protects systems by allowing them to function even if the vSAN datastore is full because the space is already reserved. For example, suppose you create a 10GB virtual disk with thick provisioning. In that case, the full amount of virtual disk storage capacity is pre-allocated on the physical storage where the virtual disk is created and consumes all the space allocated to it in the datastore.  It won’t allow other VMs to share the space from the datastore. A thin-provisioned virtual disk consumes the space that it needs initially and grows to the data space demand used in the datastore.
 
       - question: Can I create a new VM in Azure VMware Solution with thin provisioning even if the default vSAN policy is thick provisioning?
-        answer: Yes. Only the default cluster (first three nodes) is set up with thick provisioning for reliability reasons. Outside of the default (thick_provision), you can create VMs with FTT1 thin provisioning. 
+        answer: Yes. Outside of the default (thick_provision), you can create VMs with FTT1 thin provisioning. 
 
       - question: If we migrate a VM created with thin provisioning on the on-premises side to Azure VMware Solution, will the VM remain thin?
         answer: No. However, if the VM is migrated as thick, you can change policies on the individual VMs and individual vmdks through a combination of UI and PowerCLI.