Skip to content

Commit b2ea1df

Browse files
authored
Line 457: is > are
1 parent 8845fcb commit b2ea1df

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -454,7 +454,7 @@ This feature is supported for the following sensor versions:
454454

455455
## Retrieve forensics data stored on the sensor
456456

457-
Use Defender for IoT data mining reports on an OT network sensor to retrieve forensic data from that sensor’s storage. The following types of forensic data is stored locally on OT sensors, for devices detected by that sensor:
457+
Use Defender for IoT data mining reports on an OT network sensor to retrieve forensic data from that sensor’s storage. The following types of forensic data are stored locally on OT sensors, for devices detected by that sensor:
458458

459459
- Device data
460460
- Alert data
@@ -496,4 +496,4 @@ For more information, see:
496496
- [Manage sensors with Defender for IoT in the Azure portal](how-to-manage-sensors-on-the-cloud.md)
497497
- [Threat intelligence research and packages](how-to-work-with-threat-intelligence-packages.md)
498498
- [Manage sensors from the management console](how-to-manage-sensors-from-the-on-premises-management-console.md)
499-
- [Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)
499+
- [Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md)

0 commit comments

Comments
 (0)