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 214df67d27..f857694b50 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
@@ -65,7 +65,7 @@ topics:
 {% tip %}
 
 **Tip**
-For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant; however, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear on a dormant user report.
+For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant. However, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear in the Dormant User report.
 
 In the case of web sign-on events, only sign-on events through via an SSO domain associated with your enterprise are considered user activity associated with the enterprise.