removing 'updatable'

Author: Shereen-Bhar

articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md

@@ -49,7 +49,7 @@ To edit a site's details, select the site's name on the **Sites and sensors** pa
 
 - **Tags**: (Optional) Enter values for the **Key** and **Value** fields for each new tag you want to add to your site. Select **+ Add** to add a new tag.
 
-- **Owner**: For sites with OT sensors only. Enter one or more email addresses for the user you want to designate as the owner of the devices at this site. The site owner is inherited by all devices at the site, and is shown on the IoT device entity pages and in incident details in Microsoft Sentinel. 
+- **Owner**: For sites with OT sensors only. Enter one or more email addresses for the user you want to designate as the owner of the devices at this site. The site owner is inherited by all devices at the site, and is shown on the IoT device entity pages and in incident details in Microsoft Sentinel.
 
     In Microsoft Sentinel, use the **AD4IoT-SendEmailtoIoTOwner** and **AD4IoT-CVEAutoWorkflow** playbooks to automatically notify device owners about important alerts or incidents. For more information, see [Investigate and detect threats for IoT devices](../../sentinel/iot-advanced-threat-monitoring.md).
 
@@ -59,7 +59,7 @@ When you're done, select **Save** to save your changes.
 
 Sensors that you've on-boarded to Defender for IoT are listed on the Defender for IoT **Sites and sensors** page. Select a specific sensor name to drill down to more details for that sensor.
 
-Use the options on the **Sites and sensor** page and a sensor details page to do any of the following tasks. If you're on the **Sites and sensors** page, select multiple sensors to apply your actions in bulk using toolbar options. For individual sensors, use the **Sites and sensors** toolbar options, the **...** options menu at the right of a sensor row, or the options on a sensor details page. 
+Use the options on the **Sites and sensor** page and a sensor details page to do any of the following tasks. If you're on the **Sites and sensors** page, select multiple sensors to apply your actions in bulk using toolbar options. For individual sensors, use the **Sites and sensors** toolbar options, the **...** options menu at the right of a sensor row, or the options on a sensor details page.
 
 |Task |Description  |
 |---------|---------|
@@ -87,7 +87,7 @@ You may need to reactivate an OT sensor because you want to:
 
 - **Associate the sensor to a new site**:  Re-register the sensor with new site definitions and use the new activation file to activate.
 
-- **Change your plan commitment**: If you make changes to your plan, for example if you change your price plan from a trial to a monthly commitment, you'll need to reactivate your sensors to reflect the new changes.
+- **Change your plan commitment**: If you make changes to your plan, such as changing your price plan from a trial to a monthly commitment, you'll need to reactivate your sensors to reflect the new changes.
 
 In such cases, do the following steps:
 
@@ -106,7 +106,6 @@ Make sure that you've started with the relevant updates steps for this update. F
 >
 > For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
 
-
 ## Understand sensor health (Public preview)
 
 This procedure describes how to view sensor health data from the Azure portal. Sensor health includes data such as whether traffic is stable, the sensor is overloaded, notifications about sensor software versions, and more.
@@ -127,7 +126,6 @@ This procedure describes how to view sensor health data from the Azure portal. S
 
         For more information, see our [Sensor health message reference](sensor-health-messages.md).
 
-    - **Updatable** means that the sensor has an older version, and there are software updates available to install
     - **Unsupported** means that the sensor has a software version install that is no longer supported.
 
 1. To check on specific sensor issues, filter the grid by sensor health, and select one or more issues to verify. For example:

articles/defender-for-iot/organizations/sensor-health-messages.md

@@ -13,19 +13,17 @@ For more information, see [Understand sensor health (Public preview)](how-to-man
 
 ## Critical messages
 
-
 |Title  |Message  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Disconnected**     |   This sensor is not communicating with Azure     |      Sensor is disconnected   |   Try signing into the sensor to check for errors or networking failures. <br><br>We also recommend reviewing the sensor networking configuration and verifying the sensor’s ability to communicate with Azure.      |
-|**Sanity failed**     |    This sensor failed an internal consistency check     |      Sensor fails sanity   |       The sensor is in a degraded state. <br><br>Check the sensor for hardware failures and try restarting the sensor.  If the issue isn't resolved, open a support ticket.  |
+|**Disconnected**     |   This sensor isn't communicating with Azure     |      Sensor is disconnected   |   Try signing into the sensor to check for errors or networking failures. <br><br> We also recommend reviewing the sensor networking configuration and verifying the sensor’s ability to communicate with Azure.      |
+|**Sanity failed**     |    This sensor failed an internal consistency check     |      Sensor fails sanity   |       The sensor is in a degraded state. <br><br> Check the sensor for hardware failures and try restarting the sensor.  If the issue isn't resolved, open a support ticket.  |
 |**No traffic detected**     |   No traffic detected on the monitored network interfaces      |   No traffic detected      |  Check that the monitoring ports are connected to SPAN/monitor ports on the adjacent switch and that traffic is active on the link. At least one link with network traffic should be connected to the monitor ports.       |
 
-
 ## Warning messages
 
 |Title  |Message  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Package upload failed** |There was an error uploading the file to the sensor |Upload error |Verify the sensor’s ability to communicate with download.microsoft.com and retry. <br><br>If the problem persists,  open a support ticket.|
+|**Package upload failed** |There was an error uploading the file to the sensor |Upload error |Verify the sensor’s ability to communicate with download.microsoft.com and retry. <br><br> If the problem persists,  open a support ticket.|
 |**Sensor update failed** | There was an error installing the update.| Installation error |Open a support ticket. |
 | **Unstable traffic to Azure**|Sensor’s connection to Azure is unstable |Unstable traffic to Azure | We recommend that you check the sensor WAN connection, the BW limit settings, and validate network equipment that might be on the route between the sensor and the cloud.|
 | **Outdated**|Outdated software may result in a non-optimal experience |Sensor version is outdated |Upgrade your sensor software to the latest version to use the most recently available Defender for IoT features.|
@@ -34,9 +32,8 @@ For more information, see [Understand sensor health (Public preview)](how-to-man
 
 |Title  |Message  |Description  |Recommendation  |
 |---------|---------|---------|---------|
-|**Pending activation** |Waiting for sensor to connect for the first time |Pending activation | Upload the activation file to the sensor. If this does not resolve the problem, verify the sensor’s ability to communicate with Azure.|
-|**Pending reactivation** |Waiting for reactivation with new license |Pending reactivation |Upload the new activation file to the sensor. If this does not resolve the problem, verify the sensor’s ability to communicate with Azure. |
-|**Updatable** |A new version is available |Update available | Upgrade your sensor software to the latest version to use the most recently available Defender for IoT features.|
+|**Pending activation** |Waiting for sensor to connect for the first time |Pending activation | Upload the activation file to the sensor. If this doesn't resolve the problem, verify the sensor’s ability to communicate with Azure.|
+|**Pending reactivation** |Waiting for reactivation with new license |Pending reactivation |Upload the new activation file to the sensor. If this doesn't resolve the problem, verify the sensor’s ability to communicate with Azure. |
 
 ## Next steps