Apply suggestions from code review

Co-authored-by: swtiwari0709 <[email protected]>

Author: robswain

articles/private-5g-core/configure-internal-forwarding.md

@@ -12,9 +12,10 @@ ms.custom: template-how-to
 
 # Configure UE to UE internal forwarding for Azure Private 5G Core - Azure portal
 
-By default, traffic flowing between user equipment (UEs) attached to the same data network stays within that network. This is called *internal forwarding*. Internal forwarding minimizes latency and maximizes security and privacy. Alternatively, you can disable internal forwarding to force internal traffic to use an external gateway.
+AP5GC enables traffic flowing between user equipment (UEs) attached to the same data network to stay within that network. This is called *internal forwarding between UEs*. Internal forwarding between UEs minimizes latency and maximizes security and privacy for UE-UE traffic. You can modify your existing SIM policies to enable or disable this behaviour.
 
-If you are using the [Default service and allow-all SIM policy](default-service-sim-policy.md), internal forwarding will be enabled. If you are using a more restrictive policy, you may need to enable internal forwarding.
+If you are using the [Default service and allow-all SIM policy](default-service-sim-policy.md), internal forwarding will be enabled. If you are using a more restrictive policy, you may need to enable internal forwarding. 
+If you are using the [Default service and allow-all SIM policy](default-service-sim-policy.md, and would like to disable internal forwarding, either because you use an external gateway or because you do not want UEs to communicate with each other, you can create a service to do so and then apply it to your allow-all SIM policy
 
 ## Prerequisites