Acrolinx updates

Author: PaulCarterMicrosoft

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

@@ -35,11 +35,11 @@ The following table shows the support status for different Packet Core releases
 
 ### TCP Maximum Segment Size (MSS) Clamping
 
-TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core will now automatically set this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core now automatically sets this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
 
 ### Improved Packet Core Scaling 
 
-The maximum supported limits for a range of parameters in an Azure Private 5G Core deployment have increased.  These limits have been confirmed through testing, but other factors may affect what is achievable in a given scenario. 
+In this release, the maximum supported limits for a range of parameters in an Azure Private 5G Core deployment increase. Testing confirms these limits, but other factors could affect what is achievable in a given scenario. 
 The following table lists the new maximum supported limits.
 
 | Element                | Maximum supported |
@@ -49,9 +49,9 @@ The following table lists the new maximum supported limits.
 | RAN nodes (eNB/gNB)    | 200 per packet core |
 | Active UEs             | 10,000 per deployment (all sites) |
 | SIMs                   | 20,000 per ASE |
-| SIM provisioning       | 10,000 per JSON file via Azure portal, 4MB per REST API call  |
+| SIM provisioning       | 10,000 per JSON file via Azure portal, 4 MB per REST API call  |
 
-See [Service Limits](azure-stack-edge-virtual-machine-sizing#service-limits) for more information.
+For more information, see [Service Limits](azure-stack-edge-virtual-machine-sizing#service-limits).
 
 ## Issues fixed in the AP5GC 2403 release
 

articles/private-5g-core/whats-new.md

@@ -33,11 +33,11 @@ The 2403 release for the Azure Private 5G Core packet core is now available. For
 
 ### TCP Maximum Segment Size (MSS) Clamping
 
-TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core will now automatically set this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core now automatically sets this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
 
 ### Improved Packet Core Scaling 
 
-The maximum supported limits for a range of parameters in an Azure Private 5G Core deployment have increased.  These limits have been confirmed through testing, but other factors may affect what is achievable in a given scenario. 
+In this release, the maximum supported limits for a range of parameters in an Azure Private 5G Core deployment increase. Testing confirms these limits, but other factors could affect what is achievable in a given scenario. 
 The following table lists the new maximum supported limits.
 
 | Element                | Maximum supported |
@@ -47,9 +47,9 @@ The following table lists the new maximum supported limits.
 | RAN nodes (eNB/gNB)    | 200 per packet core |
 | Active UEs             | 10,000 per deployment (all sites) |
 | SIMs                   | 20,000 per ASE |
-| SIM provisioning       | 10,000 per JSON file via Azure portal, 4MB per REST API call  |
+| SIM provisioning       | 10,000 per JSON file via Azure portal, 4 MB per REST API call  |
 
-See [Service Limits](azure-stack-edge-virtual-machine-sizing#service-limits) for more information.
+For more information, see [Service Limits](azure-stack-edge-virtual-machine-sizing#service-limits).
 
 ## March 2024