diff --git a/docs/Using Fleet/Automations.md b/docs/Using Fleet/Automations.md
index c34d884d14..e3bc82cc35 100644
--- a/docs/Using Fleet/Automations.md	
+++ b/docs/Using Fleet/Automations.md	
@@ -15,7 +15,7 @@ percentage of hosts have not checked in to Fleet for a configured number of days
 
 Vulnerability automations are triggered if Fleet detects a new vulnerability (CVE) on at least one host. 
 
-> Note that a CVE is treated as "new" by Fleet if it was published to the national vulnerability database (NVD) within the preceding 30 days by default. This setting can be changed through the [`recent_vulnerability_max_age` configuration option](https://fleetdm.com/docs/deploying/configuration#recent-vulnerability-max-age).
+> Note that Fleet treats a CVE as "new" if it was published within the preceding 30 days by default. This setting can be changed through the [`recent_vulnerability_max_age` configuration option](https://fleetdm.com/docs/deploying/configuration#recent-vulnerability-max-age).
 
 Fleet can be configured either to send a webhook request or to create a ticket in Jira or Zendesk. Fleet checks whether to trigger vulnerability automations once per hour by default. This period can be changed through the [`vulnerabilities_periodicity` configuration option](https://fleetdm.com/docs/deploying/configuration#periodicity).