Copy edits

Author: b-branco

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

@@ -16,7 +16,7 @@ This article will help you design and prepare for implementing a private 4G or 5
 
 ## Azure Private MEC and Azure Private 5G Core
 
-[Azure private multi-access edge compute (MEC)](../private-multi-access-edge-compute-mec/overview.md) is a solution that combines Microsoft compute, networking, and application services onto a deployment at the enterprise premises (edge). These deployments are managed centrally from the cloud. Azure Private 5G Core is an Azure service, within Azure private MEC, that provides 4G and 5G core network functions at the enterprise edge. At the enterprise edge site, devices attach across a cellular radio access network (RAN) and are connected via the Azure Private 5G Core service to upstream networks, applications, and resources. Optionally, devices may exploit the local compute capability provided by Azure private MEC to process data streams at very low latency, all under the control of the enterprise.
+[Azure private multi-access edge compute (MEC)](../private-multi-access-edge-compute-mec/overview.md) is a solution that combines Microsoft compute, networking, and application services onto a deployment at the enterprise premises (edge). These deployments are managed centrally from the cloud. Azure Private 5G Core is an Azure service within Azure private MEC that provides 4G and 5G core network functions at the enterprise edge. At the enterprise edge site, devices attach across a cellular radio access network (RAN) and are connected via the Azure Private 5G Core service to upstream networks, applications, and resources. Optionally, devices may exploit the local compute capability provided by Azure private MEC to process data streams at very low latency, all under the control of the enterprise.
 
 :::image type="content" source="media/private-5g-elements.png" alt-text="Diagram displaying the components of a private network solution. UEs, RANs and sites are at the edge, while Azure region management is in the cloud.":::
 
@@ -44,7 +44,7 @@ You may have existing IP networks at the enterprise site that the private cellul
 - Using network address and port translation (NAPT), either on the packet core itself, or on an upstream network device such as a border router.
 - Optimizing the network for performance by choosing a maximum transmission unit (MTU) that minimizes fragmentation.
 
-Document the IP subnets (IPv4) that will be used for the deployment with the enterprise, agreeing the IP addresses to use for each element in the solution, as well as the addresses that will be allocated to UEs when they attach. Plan to deploy (or configure existing) routers and firewalls at the enterprise site to permit traffic. You should also agree how and where in the network any NAPT or MTU changes are required and plan the associated router/firewall configuration. For additional information, see [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).
+Document the IP subnets (IPv4) that will be used for the deployment with the enterprise, agreeing the IP addresses to use for each element in the solution, as well as the addresses that will be allocated to UEs when they attach. Plan to deploy (or configure existing) routers and firewalls at the enterprise site to permit traffic. You should also agree how and where in the network any NAPT or MTU changes are required and plan the associated router/firewall configuration. For more information, see [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).
 
 ### Network access
 
@@ -68,21 +68,21 @@ Your RAN will transmit an identifier, known as a *PLMN ID*, to all UEs, on the f
 
 The UEs must be able to communicate with the RAN, from any location at the site. This means that the signals must propagate effectively in the environment, including accounting for obstructions and equipment, to support UEs moving around the site, for example between indoor and outdoor areas.
 
-Perform a site survey with your RAN partner and the enterprise to make sure that the coverage is adequate. Make sure that you understand the RAN units’ capabilities in different environments (for example, outdoors) and any limits, for example, on the number of attached UEs that a single unit can support. If your UEs are going to move around the site, you should also confirm that the RAN supports X2 (4G) or Xn (5G) handover, which allows for the UE to transition seamlessly between the coverage provided by two RAN units. However, note that UEs cannot use these handover techniques to roam between a private enterprise network and the public cellular network offered by a telco operator.
+Perform a site survey with your RAN partner and the enterprise to make sure that the coverage is adequate. Make sure that you understand the RAN units’ capabilities in different environments and any limits, for example, on the number of attached UEs that a single unit can support. If your UEs are going to move around the site, you should also confirm that the RAN supports X2 (4G) or Xn (5G) handover, which allows for the UE to transition seamlessly between the coverage provided by two RAN units. Note that UEs cannot use these handover techniques to roam between a private enterprise network and the public cellular network offered by a telco operator.
 
 ### SIMs
 
 Every UE must present an identity encoded in a SIM to the network. SIMs are available in different physical form factors as well as in software-only format (eSIM). The data encoded on the SIM must match the configuration of the RAN and of the provisioned identity data in the Azure Private 5G Core.
 
-Obtain SIMs in factors compatible with the UEs and programmed with the PLMN ID and keys that you want to use for the deployment. Physical SIMs are widely available on the open market at relatively low cost. If you prefer to use eSIMs, you'll need to deploy the necessary eSIM configuration and provisioning infrastructure so that UEs can configure themselves before they attach to the cellular network. Use the provisioning data you receive from your SIM partner to provision matching entries in Azure Private 5G Core. Because SIM data must be kept secure, the cryptographic keys used to provision SIMs are not readable in Azure Private 5G Core once set, so consider how you might store them in case you ever need to re-provision the data in Azure Private 5G Core.
+Obtain SIMs in factors compatible with the UEs and programmed with the PLMN ID and keys that you want to use for the deployment. Physical SIMs are widely available on the open market at relatively low cost. If you prefer to use eSIMs, you'll need to deploy the necessary eSIM configuration and provisioning infrastructure so that UEs can configure themselves before they attach to the cellular network. Use the provisioning data you receive from your SIM partner to provision matching entries in Azure Private 5G Core. Because SIM data must be kept secure, the cryptographic keys used to provision SIMs are not readable in Azure Private 5G Core once set, so consider how you might store them in case you ever need to reprovision the data in Azure Private 5G Core.
 
 ### Automation and integration
 
 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 re-apply 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 additional 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).
+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 must also consider how you'll integrate other Azure products and services with the private enterprise network. Notable among these are [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. You might use, for example, [Azure Blueprints](/azure/governance/blueprints/overview) to set up the subscriptions and resource group model that works best for your organization.
+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. You might use, for example, [Azure Blueprints](/azure/governance/blueprints/overview) to set up the subscriptions and resource group model that works best for your organization.
 
 ## Next steps