Apply suggestions from code review

Co-authored-by: robswain <[email protected]>

Author: b-branco

articles/private-5g-core/private-mobile-network-design-requirements.md

@@ -50,7 +50,7 @@ You will need to document the IPv4 subnets that will be used for the deployment
 
 Your design must reflect the enterprise’s rules on what networks and assets should be reachable by the RAN and UEs on the private 5G network. For example, they might be permitted to access local Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), the internet, or Azure, but not a factory operations local area network (LAN). You may need to arrange for remote access to the network so that you can troubleshoot issues without requiring a site visit. You also need to consider how the enterprise site will be connected to upstream networks such as Azure, for management and/or for access to other resources and applications outside of the enterprise site.
 
-Confirm the IP subnets and addresses that will be allowed to communicate with each other with the enterprise team. Then, create a routing plan and/or access control list (ACL) configuration that implements this plan on the local IP infrastructure. You may also use virtual local area networks (VLANs) to partition elements at layer 2 (although the Azure Private 5G Core does not tag VLAN traffic itself). As the system integrator, you may also agree with the enterprise to set up an access mechanism, such as a virtual private network (VPN), that allows your support personnel to remotely connect to the management interface of each element in the solution. In any case you'll need an IP link between Azure Private 5G Core and Azure for management and telemetry.
+You will need to agree with the enterprise team which IP subnets and addresses that will be allowed to communicate with each other. Then, create a routing plan and/or access control list (ACL) configuration that implements this agreement on the local IP infrastructure. You may also use virtual local area networks (VLANs) to partition elements at layer 2 (note that the Azure Private 5G Core does not tag VLAN traffic itself). You may also agree with the enterprise to set up an access mechanism, such as a virtual private network (VPN), that allows your support personnel to remotely connect to the management interface of each element in the solution. You will also need an IP link between Azure Private 5G Core and Azure for management and telemetry.
 
 ### RAN compliance
 
@@ -80,7 +80,7 @@ You should SIMs in factors compatible with the UEs and programmed with the PLMN
 
 Being able to build enterprise networks using automation and other programmatic techniques saves time, reduces errors, and produces better customer outcomes. Such techniques also provide a recovery path in the event of a site failure that requires rebuilding the network.
 
-Consider adopting a programmatic, *infrastructure as code* approach to your deployments. Use templates or the Azure REST API to build your deployment using parameters as inputs with values that you have collected during the design phase of the project. Save provisioning information such as SIM data, switch/router configuration, and network policies in machine-readable format so that, in the event of a failure, you can reapply the configuration in the same way as you originally did. You may also wish to deploy a spare Azure Stack Edge server to minimize recovery time if the first unit fails. For more information on deploying a network using templates, refer to [Quickstart: Deploy a private mobile network and site - ARM template](deploy-private-mobile-network-with-site-arm-template.md).
+You should adopting a programmatic, *infrastructure as code* approach to your deployments. You can use templates or the Azure REST API to build your deployment using parameters as inputs with values that you have collected during the design phase of the project. You should save provisioning information such as SIM data, switch/router configuration, and network policies in machine-readable format so that, in the event of a failure, you can reapply the configuration in the same way as you originally did. You may also want to deploy a spare Azure Stack Edge server to minimize recovery time if the first unit fails. For more information on deploying a network using templates, refer to [Quickstart: Deploy a private mobile network and site - ARM template](deploy-private-mobile-network-with-site-arm-template.md).
 
 You must also consider how you'll integrate other Azure products and services with the private enterprise network. These products include [Azure Active Directory](/azure/active-directory/fundamentals/active-directory-whatis) and [role-based access control (RBAC)](/azure/role-based-access-control/overview), where you must consider how tenants, subscriptions and resource permissions will align with the business model that exists between you and the enterprise, as well as your own approach to customer system management. For example, you might use [Azure Blueprints](/azure/governance/blueprints/overview) to set up the subscriptions and resource group model that works best for your organization.