Update retention-logic-mdvm.md

Author: denisebmsft

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

@@ -19,13 +19,13 @@ ms.date: 04/28/2025
 
 # Understand retention logic in Microsoft Defender Vulnerability Management
 
-[Defender Vulnerability Management](defender-vulnerability-management.md) continuously prioritizes vulnerabilities across devices and provides security recommendations to mitigate risk in the Microsoft Defender portal. Defender Vulnerability Management recommendations uses different retention periods to determine when to stop flagging vulnerabilities based on event reporting activity. This article describes how retention works for two common scenarios: inactive devices and uninstalled software.
+[Defender Vulnerability Management](defender-vulnerability-management.md) continuously prioritizes vulnerabilities across devices and provides security recommendations to mitigate risk in the Microsoft Defender portal. Defender Vulnerability Management recommendations use different retention periods to determine when to stop flagging vulnerabilities based on event reporting activity. This article describes how retention works for two common scenarios: inactive devices and uninstalled software.
 
 ## Inactive devices
 
 In the Microsoft Defender portal, a device can be listed as inactive for any of the following reasons:
 
-- The device has stopped sending sensor data for seven days or more
+- The device stopped sending sensor data at least seven days ago
 - 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