updates after double checking

Author: Shereen-Bhar

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

@@ -311,7 +311,9 @@ Sensor backup files are automatically named through the following format: `<sens
 
 ### Restore sensors
 
-You can restore a sensor from a backup file using the sensor console or the CLI. For more information, see [CLI command reference from OT network sensors](cli-ot-sensor.md).
+You can restore a sensor from a backup file using the sensor console or the CLI.
+
+For more information, see [CLI command reference from OT network sensors](cli-ot-sensor.md).
 
 **To restore from the sensor console:**
 

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

@@ -170,7 +170,7 @@ This procedure descries how to recover privileged access to a sensor, for the *c
 
 Use the OT sensor's CLI access to define the number of maximum failed sign-ins before an OT sensor will prevent the user from signing in again from the same IP address.
 
-For more information, see [Defender for IoT CLI users and access](references-work-with-defender-for-iot-cli-commands.md) and [CLI command reference from OT network sensors](cli-ot-sensor.md).
+For more information, see [Defender for IoT CLI users and access](references-work-with-defender-for-iot-cli-commands.md).
 
 **Prerequisites**: This procedure is available for the *cyberx* user only.
 

articles/defender-for-iot/organizations/ot-deploy/post-install-validation-ot-software.md

@@ -11,8 +11,6 @@ After you've installed OT software on your [OT sensors](install-software-ot-sens
 
 System health validations are supported via the sensor or on-premises management console UI or CLI, and are available for both the *support* and *cyberx* users.
 
-For more information, see [CLI command reference from OT network sensors](../cli-ot-sensor.md)
-
 ## General tests
 
 After installing OT monitoring software, make sure to run the following tests:

articles/defender-for-iot/organizations/resources-manage-proprietary-protocols.md

@@ -37,8 +37,6 @@ After you've developed and tested a dissector plugin for proprietary protocols,
 
 1. Sign in to your sensor machine via CLI as the *Administrator*, *Cyberx*, or *Support* user.
 
-    For more information, see [CLI command reference from OT network sensors](cli-ot-sensor.md).
-
 1. Go the `/var/cyberx/properties/horizon.properties` file and verify that the `ui.enabled` property is set to `true` (`horizon.properties:ui.enabled=true`)
 
 1. Sign in to the sensor console as the *Administrator*, *Cyberx*, or *Support*.

articles/defender-for-iot/organizations/update-ot-software.md

@@ -202,8 +202,6 @@ The sensor update process won't succeed if you don't update the on-premises mana
 
 This procedure describes how to update OT sensor software via the CLI, directly on the OT sensor.
 
-For more information, see [CLI command reference from OT network sensors](cli-ot-sensor.md).
-
 **To update sensor software directly from the sensor via CLI**:
 
 1. Use SFTP or SCP to copy the update file to the sensor machine.

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

@@ -546,7 +546,7 @@ For more information, see [Manage your IoT devices with the device inventory for
 
 Starting in this version, CLI users are automatically signed out of their session after 300 inactive seconds. To sign out manually, use the new `logout` CLI command.
 
-For more information, see [Work with Defender for IoT CLI commands](references-work-with-defender-for-iot-cli-commands.md) and [CLI command reference from OT network sensors](cli-ot-sensor.md).
+For more information, see [Work with Defender for IoT CLI commands](references-work-with-defender-for-iot-cli-commands.md).
 
 ## February 2022