PR feedback

Author: robswain

articles/private-5g-core/commission-cluster.md

@@ -159,7 +159,7 @@ If you're running other VMs on your Azure Stack Edge, we recommend that you stop
 
 1. For the **Node size**, select **Standard_F16s_HPN**.
 1. Ensure the **Arc enabled Kubernetes** checkbox is selected.
-1. Select the **Change** link and enter the Microsoft Entra application Object Id (OID) for the custom location which you obtained from [Retrieve the Object ID (OID)](complete-private-mobile-network-prerequisites.md#retrieve-the-object-id-oid).
+1. Select the **Change** link and enter the Microsoft Entra application Object ID (OID) for the custom location which you obtained from [Retrieve the Object ID (OID)](complete-private-mobile-network-prerequisites.md#retrieve-the-object-id-oid).
 
    :::image type="content" source="media/commission-cluster/commission-cluster-configure-kubernetes.png" alt-text="Screenshot of Configure Arc enabled Kubernetes pane, showing where to enter the custom location OID.":::
 

articles/private-5g-core/complete-private-mobile-network-prerequisites.md

@@ -42,7 +42,7 @@ Azure Private 5G Core is deployed as an Azure Kubernetes Service (AKS) cluster.
 
 For an HA deployment, you will need to deploy a gateway router (strictly, a Layer 3 capable device – either a router or an L3 switch (router/switch hybrid)) between the ASE cluster and:
 
-- the RAN equipment in the access network
+- the RAN equipment in the access network.
 - the data network(s).
 
 The gateway router must support Bidirectional Forwarding Detection (BFD) and Mellanox-compatible SFPs (small form factor pluggable modules).
@@ -69,10 +69,7 @@ See [Supported network topologies](/azure/databox-online/azure-stack-edge-gpu-cl
 
 A two node ASE cluster requires a cluster witness, so that if one of the ASE nodes fails, the cluster witness accounts for the third vote, and the cluster stays online. The cluster witness runs in the Azure cloud.
 
-To configure an Azure cloud witness, see [https://learn.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness](/windows-server/failover-clustering/deploy-cloud-witness). Note the following:
-
--	The Replication field must be set to locally redundant storage (LRS)
--	Firewalls between the ASE cluster and the Azure storage account must allow outbound traffic to https://*.core.windows.net/* on port 443 (HTTPS).
+To configure an Azure cloud witness, see [https://learn.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness](/windows-server/failover-clustering/deploy-cloud-witness). The Replication field must be set to locally redundant storage (LRS). Firewalls between the ASE cluster and the Azure storage account must allow outbound traffic to https://*.core.windows.net/* on port 443 (HTTPS).
 
 ## Allocate subnets and IP addresses
 

articles/private-5g-core/configure-routers-high-availability.md

@@ -16,13 +16,11 @@ In a Highly Available Azure Private 5G Core deployment, the Azure Kubernetes Ser
 
 This requires you to deploy a gateway router between the ASE cluster and:
 
-- the RAN equipment in the access network
+- the RAN equipment in the access network.
 - the data networks.
 
 The routers should rapidly detect the failure of an ASE device through a BFD session going down and immediately redirect all traffic to the other ASE. With the recommended settings, BFD should be able to detect failure in about one second, ensuring that traffic should be restored in less than 2.5 seconds. User plane state is replicated across the two ASEs to ensure the backup can take over immediately.
 
-:::image type="content" source="media/ha-summary.png" alt-text="Diagram showing the routing configuration in a highly available deployment.":::
-
 This how-to guide describes the configuration required on your router or routers to support an HA deployment. The gateway router for the access network and the gateway router for the data networks may be the same device or separate devices.
 
 ## Prerequisites

articles/private-5g-core/media/ha-summary.png

@@ -152,7 +152,7 @@ You need to document the IPv4 subnets that will be used for the deployment and a
 
 You can optionally deploy Azure Private 5G Core as a Highly Available (HA) service on a pair of Azure Stack Edge (ASE) devices. This requires a gateway router (strictly, a Layer 3 capable device – either a router or an L3 switch (router/switch hybrid)) between the ASE cluster and:
 
-- the RAN equipment in the access network
+- the RAN equipment in the access network.
 - the data network(s).
 
 For more information, see [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).