Update AP5GC 2211 router and RAN limitation

Author: richardwhiuk

articles/private-5g-core/azure-private-5g-core-release-notes-2211.md

@@ -56,9 +56,8 @@ The following table provides a summary of known issues in this release.
 
   |No.  |Feature  | Issue |
   |-----|-----|-----|
-  | 1 | Packet forwarding | If Azure Private 5G Core is deployed into a network where the gNodeB is on the same subnet as the Packet Core's N3 interface address (that is, there is no gateway router between them) then all downstream traffic is broken.   | 
-  | 2 | Local dashboards | In deployments with multiple Data Networks, **UPF Downstream CPU Utilization** is incorrectly reported on the local dashboards when running calls using single Data Network.  | 
-  | 3 | Local dashboards  | In some scenarios, the local dashboards don't show session rejection under the **Device and Session Statistics** panel if Session Establishment requests are rejected due to invalid PDU type (e.g. IPv6 when only IPv4 supported).   | 
+  | 1 | Local dashboards | In deployments with multiple Data Networks, **UPF Downstream CPU Utilization** is incorrectly reported on the local dashboards when running calls using single Data Network.  | 
+  | 2 | Local dashboards  | In some scenarios, the local dashboards don't show session rejection under the **Device and Session Statistics** panel if Session Establishment requests are rejected due to invalid PDU type (e.g. IPv6 when only IPv4 supported).   | 
 
 
 ## Known issues from previous releases
@@ -69,9 +68,7 @@ The following table provides a summary of known issues carried over from the pre
   |-----|-----|-----|
   | 1 | Policy configuration  | Azure Private 5G Core may ignore non-default QoS and Policy configuration when handling 4G subscribers.  | 
   | 2 | Packet forwarding  | Azure Private 5G Core may not forward buffered packets if NAT is enabled.   | 
-
-
-
+  | 3 | Packet forwarding | If Azure Private 5G Core is placed on the same subset as the RAN node (gNodeB / eNodeB) without an intervening/available router, there are two limitations. <br> - Only one RAN node can be used.  It is not possible to connect multiple RAN nodes without an intervening router. <br> - The IP address of the RAN node must be supplied in the gateway field, for both N2/S1-MME and N3/S1-U when configuring the ASE Virtual Networks on AKS Hybrid.  | 
 
 
 ## Next steps