Fixed typo

Author: kgremban

articles/iot-dps/virtual-network-support.md

@@ -27,7 +27,7 @@ For several reasons, customers may wish to restrict connectivity to Azure resour
 * Enabling a private connectivity experience from your on-premises network assets ensuring that your data and traffic 
 is transmitted directly to Azure backbone network.
 
-* Preventing exfiltration attacks from sensitive on-premises networks. 
+* Preventing exfiltration attacks from sensitive on-premises networks.
 
 * Following established Azure-wide connectivity patterns using [private endpoints](../private-link/private-endpoint-overview.md).
 
@@ -61,7 +61,7 @@ Note the following current limitations for DPS when using private endpoints:
 
 * Enabling one or more private endpoints typically involves [disabling public access](public-network-access.md) to your DPS instance. This means that you can no longer use the Azure portal to manage enrollments. Instead you can manage enrollments using the Azure CLI, PowerShell, or service APIs from machines inside the VNET(s)/private endpoint(s) configured on the DPS instance.
 
-* When using private endpoints, we recommend deploying DPS in one of the regions that support [Availability Zones](iot-dps-ha-dr.md). Otherwise, DPS instances with private endpoints enables may see reduced availability in the event of outages.
+* When using private endpoints, we recommend deploying DPS in one of the regions that support [Availability Zones](iot-dps-ha-dr.md). Otherwise, DPS instances with private endpoints enabled may see reduced availability in the event of outages.
 
 >[!NOTE]
 >**Data residency consideration:**