Fix seat usage alert threshold description
What does this MR do?
Clarify/fix "Seat usage alerts" threshold in the documentation
Related issues
(I did not open an issue for this small change)
Here we can find how the logic is defined https://gitlab.com/gitlab-org/gitlab/-/blob/54fdc621dfb084be7dcab2d005738a9d6cbeb9cb/ee/app/services/gitlab_subscriptions/reconciliations/calculate_seat_count_data_service.rb (introduced in !83492 (diffs))
For example, on an instance with 50 seats:
- The current wording "10% of seats have been used" can be interpreted as "I will be alerted when I reach 5 seats used", while the user will be alerted when 45 seats are used (so 10% left)
- The new wording "10% of seats in the subscription are remaining" should be clearer
Note that there may be an even clearer way to express it and I'm fine to use a clearer wording.
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on:- The documentation page's metadata.
- The associated Technical Writer.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by homer