Clarify how pending and failed invitations affect license consumption (#60578)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>

Author: 3 people

content/billing/reference/github-license-users.md

@@ -37,6 +37,7 @@ category:
 * Billing managers
 * Anyone with a pending invitation to become a billing manager
 * Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+* Anyone with a failed invitation to become an organization member or an outside collaborator on a repository owned by your organization
 
 ## Organizations on {% data variables.product.prodname_ghe_cloud %}
 
@@ -53,19 +54,21 @@ category:
 If your enterprise does not use {% data variables.product.prodname_emus %}, you will also be billed for each of the following accounts:
 
 * Anyone with a pending invitation to become an organization owner or member
+  * If the invited user already consumes an enterprise license, a pending organization invitation won't use an additional license—as long as the invitation is sent to their {% data variables.product.github %} username or a verified email address on their account. 
 * Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
   * {% data reusables.organizations.org-invite-scim %}
-  * Inviting an outside collaborator to a repository using their email address temporarily uses an available seat, even if they already have access to other repositories. After they accept the invite, the seat will be freed up again. Inviting them using their username does not temporarily use a seat.
+  * If the invited user already consumes an enterprise license because they're a collaborator on an internal or private repository in the enterprise, a pending collaborator invitation using their email address for another repository in the enterprise consumes an available seat. After they accept the invite, the seat will be freed up again. Inviting them using their username does not temporarily use a seat.
 
 ### People who don't consume licenses
 
-* {% data variables.enterprise.prodname_managed_users_caps %} that are suspended
+* Suspended {% data variables.enterprise.prodname_managed_users_caps %}
 * Enterprise owners who are not a member or owner of at least one organization in the enterprise
 * The user who set up the enterprise
 * Enterprise billing managers
 * Billing managers for individual organizations
 * Anyone with a pending invitation to become a billing manager
 * Anyone who is an outside collaborator on a public repository owned by your organization, or who has a pending invitation to become one
+* Anyone with a failed invitation to become an organization member or an outside collaborator on a repository owned by your organization
 * Guest collaborators who are not organization members or repository collaborators (see [AUTOTITLE](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#guest-collaborators))
 * Users of {% data variables.visual_studio.prodname_vss_ghe %} whose accounts on {% data variables.product.prodname_dotcom %} are not linked, and who do not meet any of the other criteria for per-user pricing
 * Unaffiliated users: people who have been added to the enterprise, but are not members of any organizations in the enterprise