tweak wording

Author: robswain

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

@@ -120,13 +120,13 @@ IP packets from UEs are tunneled through from the RAN, which adds overhead from
 
 RANs typically come pre-configured with an MTU of 1500. The packet core’s default UE MTU is 1440 bytes to allow for encapsulation overhead. These values maximize RAN interoperability, but risk that certain UEs will not observe the default MTU and will generate larger packets that require IPv4 fragmentation and that may be dropped by the network. If you are affected by this issue, it is strongly recommended to configure the RAN to use an MTU of 1560 or higher, which allows a sufficient overhead for the encapsulation and avoids fragmentation with a UE using a standard MTU of 1500.
 
-You can also change the MTU signaled by the packet core. We recommend setting the MTU to a value within the range supported by your UEs and 60 bytes below the MTU signaled by the RAN. Note that:
+You can also change the UE MTU signaled by the packet core. We recommend setting the MTU to a value within the range supported by your UEs and 60 bytes below the MTU signaled by the RAN. Note that:
 
 - The data network (N6) is automatically updated to match the UE MTU.
 - The access network (N3) is automatically updated to match the UE MTU plus 60.
 - You can configure a value between 1280 and 1930 bytes.
 
-To change the packet core MTU, see [Modify a packet core instance](modify-packet-core.md).
+To change the UE MTU signaled by the packet core, see [Modify a packet core instance](modify-packet-core.md).
 
 ### Signal coverage