diff --git a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
index 2fb13c50339d..d9161a46c8c8 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -23,9 +23,11 @@ topics:
 {% data reusables.enterprise-accounts.dormant-user-activity %}
 
 {% ifversion ghec %}
-When assessing user dormancy, we only consider organizations, repositories, or sign-on events that are associated with the enterprise. For example, a user who has recently commented on an issue in a public repository outside of the enterprise may be considered dormant, while a user who has commented on an issue in a public repository within the enterprise will not be considered dormant. 
+When assessing user dormancy, we only consider organizations, repositories, or sign-on events that are associated with the enterprise. For example, a user who has recently commented on an issue in a public repository outside of the enterprise may be considered dormant, while a user who has commented on an issue in a public repository within the enterprise will not be considered dormant.
 
 Only sign-on events through an SSO domain associated with your enterprise are considered user activity associated with the enterprise.
+
+The report includes both enterprise members and outside collaborators.
 {% endif %}
 
 {% ifversion ghes or ghae %}