Update 2 files

- /doc/user/project/settings/project_access_tokens.md
- /doc/user/group/settings/group_access_tokens.md

doc/user/group/settings/group_access_tokens.md

@@ -168,7 +168,7 @@ These bot users are similar to
 [bot users for projects](../../project/settings/project_access_tokens.md#bot-users-for-projects), except they are added
 to groups instead of projects. Bot users for groups:
 
-- Do not count as licensed seats.
+- Is not a billable user, so it does not count toward the license limit.
 - Can have a maximum role of Owner for a group. For more information, see
   [Create a group access token](../../../api/group_access_tokens.md#create-a-group-access-token).
 - Have a username set to `group_{group_id}_bot_{random_string}`. For example, `group_123_bot_4ffca233d8298ea1`.

doc/user/project/settings/project_access_tokens.md

@@ -110,7 +110,7 @@ Even when creation is disabled, you can still use and revoke existing project ac
 
 Bot users for projects are [GitLab-created service accounts](../../../subscriptions/self_managed/index.md#billable-users).
 Each time you create a project access token, a bot user is created and added to the project.
-These bot users do not count as licensed seats.
+This user is not a billable user, so it does not count toward the license limit.
 
 The bot users for projects have [permissions](../../permissions.md#project-members-permissions) that correspond with the
 selected role and [scope](#scopes-for-a-project-access-token) of the project access token.