diff --git a/website/content/docs/concepts/client-count/faq.mdx b/website/content/docs/concepts/client-count/faq.mdx
index b51dbececa0..b6442eed186 100644
--- a/website/content/docs/concepts/client-count/faq.mdx
+++ b/website/content/docs/concepts/client-count/faq.mdx
@@ -71,7 +71,7 @@ Although client counts have been available via the usage metrics UI since Vault
 * Vault 1.6: Introduction of client counts in the usage metrics UI
 * Vault 1.8:
   - Eliminated wrapped tokens and control groups from client count, thereby reducing the non-entity token count. Previously, the creation and usage of control groups and wrapping tokens affected the client count each time the response is read (in the case of a wrapping token) and each time a control group was created (a non-entity token was created)
-  - Changed logic of counting of non-entity tokens on usage instead of at create time (therefore resulting in more accurate client counts)
+  - Changed the logic of counting of active identity entities on usage instead of at create time, resulting in more accurate client counts
 * Vault 1.9:
   - Changed the non-entity token computation logic to deduplicate non-entity tokens, reducing the overall client count. Moving forward, non-entity tokens, where there is no entity to map tokens, Vault will use the contents fo the token to generate a unique client identifier based on the namespace ID and associated  policies. The clientID will prevent duplicating the same token in the overall client count when the token is used again during the billing period.
   - Changed the tracking of non-entity tokens to complete on access instead of creation.