Update retention-logic-mdvm.md

Author: denisebmsft

defender-vulnerability-management/retention-logic-mdvm.md

@@ -1,6 +1,6 @@
 ---
 title: Understand retention logic in Microsoft Defender Vulnerability Management
-description: Get an overview of retention logic for inactive devices or uninstalled software in Microsoft Defender Vunerability Management.
+description: Get an overview of retention logic for inactive devices or uninstalled software in Microsoft Defender Vulnerability Management.
 author: denisebmsft
 ms.author: deniseb
 manager: deniseb
@@ -31,7 +31,7 @@ In the Microsoft Defender portal, a device can be listed as inactive for any of
 - The device was offboarded from Defender for Endpoint at least seven days ago
 - The device has network connectivity issues, such as impaired communications, blocked URLs, or blocked ports, and sends some (but not all) events
 
-If a device stops reporting to Defender for Endpoint, Defender Vulnerability Management continues to display the latest vulnerability snapshot for 30 days. After that, the device is marked as inactive, and its vulnerabilities are no longer shown in the [Microsoft Defender portal](https://security.microsoft.com).
+If a device stops reporting to Defender for Endpoint, Defender Vulnerability Management continues to display the latest vulnerability snapshot for 30 days. After that, the device is marked as inactive, and its vulnerabilities are no longer shown in the [Microsoft Defender portal](https://security.microsoft.com). Data for inactive devices is retained for 180 days (see [Microsoft Defender for Endpoint data storage and privacy](../defender-endpoint/data-storage-privacy.md)).
 
 To prevent confusion in your vulnerability data, you can exclude a device manually in the device inventory, as shown in the following screenshot: