Skip to content

Commit 38e7efc

Browse files
committed
heading
1 parent 0313330 commit 38e7efc

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

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

374374
1. For a locally-managed sensor, version 22.1.3 or higher, continue with [Upload a diagnostics log for support](how-to-manage-sensors-on-the-cloud.md#upload-a-diagnostics-log-for-support-public-preview).
375375

376-
### Clearing sensor data to factory default
376+
## Clearing sensor data to factory default
377377

378378
In cases where the sensor needs to be relocated or erased, the sensor can be reset to factory default data.
379379

@@ -388,11 +388,11 @@ Clearing data deletes all detected or learned data on the sensor. After clearing
388388

389389
1. Select **Support** > **Clear data**.
390390

391-
1. In the confirmation dialog box, select **Yes** to confirm that you do want to clear all data from the sensor and reset to factory default.
391+
1. In the confirmation dialog box, select **Yes** to confirm that you do want to clear all data from the sensor and reset to factory default. For example:
392392

393393
:::image type="content" source="media/how-to-manage-individual-sensors/clear-system-data.png" alt-text="Screenshot of clearing system data on the support page in the sensor console.":::
394394

395-
All allowlists, policies, and configuration settings are cleared, and the sensor is restarted.
395+
A confirmation message appears that the action was successful. All allowlists, policies, and configuration settings are cleared, and the sensor is restarted.
396396

397397
## Next steps
398398

0 commit comments

Comments
 (0)