implementing docs feedback

Author: Shereen-Bhar

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

@@ -114,7 +114,7 @@ Use the following sections to learn more about the individual OT sensor settings
 
 ### Active Directory
 
-To modify Active Directory settings in the Azure portal, edit for the following options:
+To configure Active Directory settings from the Azure portal, define values for the following options:
 
 |Name  |Description  |
 |---------|---------|

articles/defender-for-iot/organizations/how-to-troubleshoot-sensor.md

@@ -264,7 +264,7 @@ For more information, see:
 You can configure a standalone sensor and a management console, with the sensors related to it, to connect to NTP.
 
 > [!TIP]
-> When you're ready to start managing your OT sensor settings at scale, define NTP from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
+> When you're ready to start managing your OT sensor settings at scale, define NTP settings from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
 
 To connect a standalone sensor to NTP:
 

articles/defender-for-iot/organizations/manage-users-sensor.md

@@ -27,7 +27,7 @@ We recommend configuring on-premises users on your OT sensor with Active Directo
 For example, use Active Directory when you have a large number of users that you want to assign Read Only access to, and you want to manage those permissions at the group level.
 
 > [!TIP]
-> When you're ready to start managing your OT sensor settings at scale, define Active Directory from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
+> When you're ready to start managing your OT sensor settings at scale, define Active Directory settings from the Azure portal. Once you apply settings from the Azure portal, settings on the sensor console are read-only. For more information, see [Configure OT sensor settings from the Azure portal (Public preview)](configure-sensor-settings-portal.md).
 
 **To integrate with Active Directory**:
 

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

@@ -20,17 +20,14 @@ Features released earlier than nine months ago are described in the [What's new
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | **Sensor version 22.3.x and later**: <br>- [Configure Active Directory and NTP settings in the portal](#configure-active-directory-and-ntp-settings-in-the-portal) |
+| **OT networks** | **Sensor versions 22.3.x and higher**: <br>- [Configure Active Directory and NTP settings in the Azure portal](#configure-active-directory-and-ntp-settings-in-the-azure-portal) |
 
-### Configure Active Directory and NTP settings in the portal
+### Configure Active Directory and NTP settings in the Azure portal
 
-Configure Active Directory and NTP settings for your sensors remotely from the Azure portal.
+Now you can configure Active Directory and NTP settings for your OT sensors remotely from the **Sites and sensors** page in the Azure portal. These settings are available for OT sensor versions 22.3.x and higher.
 
 For more information, see [Sensor setting reference](configure-sensor-settings-portal.md#sensor-setting-reference)
 
-> [!NOTE]
-> The NTP and Active Directory setting is supported only for OT sensors, versions 22.3.x and later.
-
 ## April 2023
 
 |Service area  |Updates  |