Apply suggestions from code review

Co-authored-by: Anastasia Harris <[email protected]>

Author: johndowns

articles/reliability/reliability-virtual-network.md

@@ -16,22 +16,22 @@ This article describes reliability support in Azure Virtual Network, covering in
 
 [!INCLUDE [Shared responsibility description](includes/reliability-shared-responsibility-include.md)]
 
-A virtual network is a logical representation of your network in the cloud. It allows you to define your own private IP address space and segment the network into subnets. Virtual networks serve as a trust boundary to host your compute resources such as Azure Virtual Machines and load balancers. A virtual network allows direct private IP communication between the resources hosted in it. You can link a virtual network to an on-premises network through a VPN Gateway or ExpressRoute, to enable hybrid cloud scenarios and to securely extend your datacenter into Azure.
+A virtual network is a logical representation of your network in the cloud. With a virtual network, you can define your own private IP address space and segment the network into subnets. Virtual networks serve as a trust boundary to host your compute resources such as Azure Virtual Machines and load balancers. A virtual network allows direct private IP communication between the resources that are hosted in it.  To enable hybrid cloud scenarios and securely extend your datacenter into Azure, you can link a virtual network to an on-premises network through a VPN Gateway or ExpressRoute, 
 
 ## Production deployment recommendations
 
-As you build your virtual network in Azure, it's important to keep in mind the following universal design principles that help to improve the reliability of your solution:
+As you build your virtual network in Azure, it's important to improve the reliability of your solution, by keeping in mind the following universal design principles:
 
-* Ensure address spaces don't overlap. Make sure your virtual network address space (CIDR block) doesn't overlap with your organization's other network ranges.
-* Your subnets shouldn't cover the entire address space of the virtual network. Plan ahead and reserve some address space for the future.
-* Use a few large virtual networks instead of multiple small ones to reduce management overhead.
-* Secure your virtual networks by assigning Network Security Groups (NSGs) to the subnets beneath them.
+- Ensure address spaces don't overlap. Make sure your virtual network address space (CIDR block) doesn't overlap with your organization's other network ranges.
+- Your subnets shouldn't cover the entire address space of the virtual network. Plan ahead and reserve some address space for the future.
+- To reduce management overhead, use a few large virtual networks instead of multiple small ones.
+- Secure your virtual networks by assigning Network Security Groups (NSGs) to the subnets beneath them.
 
-To learn more about how to design your Azure virtual network with reliablity principles in mind, as well as other important best practices, see [Architecture best practices for Azure Virtual Network](/azure/well-architected/service-guides/virtual-network).
+To learn more about how to design your Azure virtual network with reliability principles in mind, as well as other important best practices, see [Architecture best practices for Azure Virtual Network](/azure/well-architected/service-guides/virtual-network).
 
 ## Reliability architecture overview
 
-A virtual network is one of several core networking components in Azure. When you create virtual networks, you typically create a set of resources that collectively define your networking configuration, including:
+A virtual network is one of several core networking components in Azure. When you create a virtual network, you create a set of resources that collectively define your networking configuration. These resources include:
 
 - Network security groups (NSGs) and application security groups (ASGs), which restrict communication between parts of your network.
 - User-defined routes, which control how traffic flows.
@@ -40,22 +40,22 @@ A virtual network is one of several core networking components in Azure. When yo
 - Network interface cards (NICs), which provide network connectivity to Azure virtual machines.
 - Private endpoints, which provide private connectivity to Azure services and to resources outside of your own virtual network.
 
-You might also deploy *appliances*, including ExpressRoute gateways, VPN gateways, and firewalls. Appliances provide services to support your networking needs, such as connecting to on-premises environments or providing sophisticated controls on traffic flow.
+You might also deploy *appliances*, such as ExpressRoute gateways, VPN gateways, and firewalls. Appliances provide services to support your networking requirements, such as connecting to on-premises environments or providing sophisticated controls on traffic flow.
 
 Finally, you deploy your own components, like virtual machines that run applications or databases, as well as other Azure services that provide virtual network integration.
 
 > [!IMPORTANT]
 > This guide focuses on Azure virtual networks, which are just one component in your network architecture.
 >
-> From a reliability perspective, it's important that you consider each component in your solution individually as well as how they behave together. Many core Azure networking services provide high resiliency by default, but you might need to consider how other network appliances, virtual machines, and other components can support your reliability needs. Review the reliability guides for each Azure service you use to understand how that service supports reliability.
+> From a reliability perspective, it's important that you consider each component in your solution individually as well as how they behave together. Many core Azure networking services provide high resiliency by default, but you might need to consider how other network appliances, virtual machines, and other components can support your reliability needs. Review the [reliability guides for each Azure service](./overview-reliability-guidance.md) you use to understand how that service supports reliability.
 
 To learn more about networking in Azure, see [Networking architecture design](/azure/architecture/networking/).
 
 ## Transient faults
 
 [!INCLUDE [Transient fault description](includes/reliability-transient-fault-description-include.md)]
 
-Virtual networks themselves aren't typically affected by transient faults themselves. However, transient faults might affect resources deployed within a virtual network. Review the reliability guide for each resource you use to understand their transient fault handling behaviors.
+Virtual networks themselves aren't usually affected by transient faults. However, transient faults might affect resources deployed within a virtual network. Review the [reliability guide for each resource](./overview-reliability-guidance.md) you use to understand their transient fault handling behaviors.
 
 ## Availability zone support
 
@@ -71,7 +71,7 @@ Zone-redundant virtual networks can be deployed in [any region that supports ava
 
 ### Cost
 
-Zone redundancy for Azure Virtual Networks doesn't incur a charge.
+There is no extra cost for zone redundancy for Azure Virtual Networks.
 
 ### Configure availability zone support
 
@@ -81,17 +81,17 @@ Zone redundancy is configured automatically when a virtual network is deployed i
 
 Azure virtual networks are designed to be resilient to zone failures. When a zone becomes unavailable, Azure Virtual Network automatically reroutes virtual network requests to the remaining zones. This process is seamless and doesn't require any action from you.
 
-However, any resources within the virtual network need to be considered individually, because each resource might have a different set of behaviors during the loss of an availability zone. Consult the reliability guide for each resource you use to understand their availability zone support and behavior when a zone is unavailable.
+However, any resources within the virtual network need to be considered individually, because each resource might have a different set of behaviors during the loss of an availability zone. Consult the [reliability guide for each resource(./overview-reliability-guidance.md) you use to understand their availability zone support and behavior when a zone is unavailable.
 
 ### Failback
 
 When the zone recovers, Microsoft initiates a failback process to ensure that virtual networks continue to work in the recovered zone. The failback process is automatic and doesn't require any action from you.
 
-However, you should verify the failback behaviors of any resources you deploy within the virtual network.
+However, you should verify the failback behaviors of any resources you deploy within the virtual network. For more information, consult the [reliability guide for each resource(./overview-reliability-guidance.md).
 
 ### Testing for zone failures
 
-The Azure Virtual Network platform manages traffic routing, failover, and failback for virtual networks across availability zones. You don't need to initiate anything. Because this feature is fully managed, you don't need to validate availability zone failure processes.
+The Azure Virtual Network platform manages traffic routing, failover, and failback for virtual networks across availability zones.  Because this feature is fully managed, you don't need to validate availability zone failure processes.
 
 ## Multi-region support
 
@@ -103,7 +103,7 @@ You can create virtual networks in multiple regions, and you can optionally *pee
 
 By creating virtual networks and other resources in multiple regions, you can be resilient to regional outages. However, you need to consider many factors, including:
 
-- **Traffic routing:** If you host internet-facing services in the virtual network, you need to decide how to route incoming traffic among your regions and components. Services like Azure Traffic Manager and Azure Front Door enable you to route internet traffic based on rules you specify.
+- **Traffic routing:** If you host internet-facing services in the virtual network, you need to decide how to route incoming traffic among your regions and components. With services such as Azure Traffic Manager and Azure Front Door, you can route internet traffic based on rules you specify.
 
 - **Failover:** If an Azure region is unavailable, you typically need to *fail over* by processing traffic in healthy regions. Azure Traffic Manager and Azure Front Door provide failover capabilities for internet applications.      
 
@@ -117,7 +117,7 @@ For an example of a multi-region networking architecture for web applications, s
 
 ## Service-level agreement
 
-There isn't a defined SLA for Azure Virtual Network due to the nature of the service.
+Due to the nature of the service provided. there isn't a defined SLA for Azure Virtual Network.
 
 ## Related content