Update 2-explore-azure-virtual-networks.md

Author: staleycyn

learn-pr/wwl-azure/introduction-to-azure-virtual-networks/includes/2-explore-azure-virtual-networks.md

@@ -11,11 +11,11 @@ This video reviews the basics of IP addressing and subnetting.
 
 Azure VNets enable resources in Azure to securely communicate with each other, the internet, and on-premises networks.
 
-- **Communication with the internet.** All resources in a VNet can communicate outbound to the internet, by default. You can communicate inbound to a resource by assigning a public IP address or a public Load Balancer. You can also use public IP or public Load Balancer to manage your outbound connections.
-- **Communication between Azure resources.** There are three key mechanisms through which Azure resource can communicate: VNets, VNet service endpoints, and VNet peering. Virtual Networks can connect not only virtual machines (VMs), but other Azure Resources, such as the App Service Environment, Azure Kubernetes Service, and Azure Virtual Machine Scale Sets. You can use service endpoints to connect to other Azure resource types, such as Azure SQL databases and storage accounts. When you create a VNet, your services and VMs within your VNet can communicate directly and securely with each other in the cloud.
-- **Communication between on-premises resources.** Securely extend your data center. You can connect your on-premises computers and networks to a virtual network using any of the following options: Point-to-site virtual private network (VPN), Site-to-site VPN, Azure ExpressRoute.
+- **Communication with the internet.** Resources in a VNet can communicate outbound to the internet using a NAT gateway, public IP address, or public load balancer. 
+- **Communication between Azure resources.** There are four key mechanisms through which Azure resource can communicate: VNets, VNet service endpoints, VNet private endpoints and VNet peering. 
+- **Communication between on-premises resources.** You can connect your on-premises computers and networks to a virtual network using any of the following options: Point-to-site virtual private network (VPN), Site-to-site VPN, and Azure ExpressRoute.
 - **Filtering network traffic.** You can filter network traffic between subnets using any combination of network security groups and network virtual appliances.  
-- **Routing network traffic.** Azure routes traffic between subnets, connected virtual networks, on-premises networks, and the Internet, by default. You can implement route tables or border gateway protocol (BGP) routes to override the default routes Azure creates.
+- **Routing network traffic.** Azure routes traffic between subnets, connected virtual networks, and on-premises networks.. You can implement route tables or border gateway protocol (BGP) routes to override the default routes Azure creates.
 
 ## Design considerations for Azure Virtual Networks
 
@@ -61,4 +61,4 @@ When planning to implement virtual networks, you need to consider:
 
 
 
-Choose the best response for each question.
+Choose the best response for each question.