correction to Public address item

Author: tarTech23

articles/defender-for-iot/organizations/configure-sensor-settings-portal.md

@@ -186,8 +186,7 @@ Select **Add VLAN** to add more VLANs as needed.
 
 ### Public addresses
 
-Add public addresses that might have been used for internal use and shouldn't be included as suspicious IP addresses or tracking the data<!-- Theo is this correct? OR-->.
-Excluded public IP addresses that might have been used for internal use and shouldn't be included as suspicious IP addresses or tracking the data.
+Add the public addresses of internel devices into this configuration to ensure that the sensor includes them in the inventory and doesn't treat them as internal communication.
 
 1. In the **Settings** tab, type the **IP address** and **Mask** address.
 

articles/defender-for-iot/organizations/whats-new.md

@@ -59,7 +59,7 @@ We now support the OCPI protocol. See [the updated protocol list](concept-suppor
 
 ### New sensor setting type Public addresses
 
-We're adding the **Public addresses** type to the sensor settings, that allows you to exclude public IP addresses that might have been used for internal use and shouldn't be tracked. For more information, see [add sensor settings](configure-sensor-settings-portal.md#add-sensor-settings).
+We're adding the **Public addresses** type to the sensor settings, that allows you list the public addresses of internal devices and ensure that the sensor doesn't treat them as internal communication. For more information, see [add sensor settings](configure-sensor-settings-portal.md#add-sensor-settings).
 
 ### Improved OT sensor onboarding