Update virtual-networks-faq.md

Fixed wrong word choice (main -> name).
Added article "from" 4 to 30 for more professional flow.
Changed 2 instances of "IPV6" to "IPv6" to match rest of article.

Author: AMcVicker

articles/virtual-network/virtual-networks-faq.md

@@ -209,7 +209,7 @@ If you change your DNS server list, you need to perform a DHCP lease renewal on
 Azure-provided DNS is a multitenant DNS service from Microsoft. Azure registers all of your VMs and cloud service role instances in this service. This service provides name resolution:
 
 * By host name for VMs and role instances in the same cloud service.
-* By fully qualified domain main (FQDN) for VMs and role instances in the same virtual network.
+* By fully qualified domain name (FQDN) for VMs and role instances in the same virtual network.
 
 To learn more about DNS, see [Name resolution for resources in Azure virtual networks](virtual-networks-name-resolution-for-vms-and-role-instances.md).
 
@@ -345,7 +345,7 @@ No. You must set the [FlowTimeoutInMinutes](/powershell/module/az.network/set-az
 
 ```Powershell
 $Allvnet = Get-AzVirtualNetwork
-$time = 4 #The value should be 4 to 30 minutes (inclusive) to enable tracking, or null to disable tracking. 
+$time = 4 #The value should be from 4 to 30 minutes (inclusive) to enable tracking, or null to disable tracking. 
 ForEach ($vnet in $Allvnet)
 {
     $vnet.FlowTimeoutInMinutes = $time
@@ -506,7 +506,7 @@ Certain services (such as Azure SQL and Azure Cosmos DB) allow exceptions to the
 Turning on the service endpoints on the network side can lead to a connectivity drop, because the source IP changes from a public IPv4 address to a private address. Setting up virtual network ACLs on the Azure service side before turning on service endpoints on the network side can help avoid a connectivity drop.
 
 >[!NOTE]
-> If you enable Service Endpoint on certain services like "Microsoft.AzureActiveDirectory" you can see IPV6 address connections on Sign-In Logs. Microsoft use an internal IPV6 private range for this type of connection.
+> If you enable Service Endpoint on certain services like "Microsoft.AzureActiveDirectory" you can see IPv6 address connections on Sign-In Logs. Microsoft use an internal IPv6 private range for this type of connection.
 
 ### Do all Azure services reside in the Azure virtual network that the customer provides? How does a virtual network service endpoint work with Azure services?