Skip to content

Proposes guidance and rule for "quite"

Amy Qualls requested to merge aqualls-avoid-quite into master

What does this MR do?

I shared https://bsky.app/profile/nameshiv.bsky.social/post/3kzereafewt2y in #lang_en yesterday, and now both the British English and American English speakers in that channel are staring at each other in horror, muttering "what is WRONG with you?"

So, as it turns out, "quite" in US English generally means "very." Everywhere else, it means "somewhat."

(We probably shouldn't be using this word in our docs, then.)

Findings from vale --no-wrap --filter='.Name=="gitlab_base.Quite"' doc/**/*.md:

55 findings, 47 in `doc/development`

User docs (8):

 doc/administration/gitaly/troubleshooting.md
 116:41  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/ci/docker/using_kaniko.md
 22:70  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/ci/migration/bamboo.md
 96:76  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/ci/pipelines/pipeline_architectures.md
 41:72  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/security/hardening_general_concepts.md
 45:73  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/tutorials/reviews/index.md
 280:30  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/user/application_security/api_fuzzing/performance.md
 50:174  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/user/application_security/api_security_testing/performance.md
 50:174  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

Development docs (47):

 doc/development/cicd/index.md
 187:75  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/contributing/verify/index.md
 244:15  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/dangerbot.md
 115:21  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/batching_best_practices.md
 207:54  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/clickhouse/index.md
 11:59  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/efficient_in_operator_queries.md
 640:29  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/pagination_guidelines.md
 157:128  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/polymorphic_associations.md
 31:47  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 64:39  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/database/understanding_explain_plans.md
 31:51   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 53:28   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 228:11  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 238:64  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 339:48  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 399:26  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 456:9   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 517:70  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/fe_guide/accessibility/automated_testing.md
 132:146  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/fe_guide/getting_started.md
 46:55  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/fe_guide/migrating_from_vuex.md
 96:185   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 100:118  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 218:169  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/fe_guide/vue.md
 457:35  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/geo.md
 11:39  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/github_importer.md
 231:25  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/i18n/externalization.md
 237:115  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 237:164  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/import_project.md
 126:12  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/merge_request_concepts/performance.md
 294:54  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/namespaces.md
 250:40  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/packages/cleanup_policies.md
 61:4  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/performance.md
 157:5   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 638:45  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/permissions/predefined_roles.md
 125:25  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 126:1   warning  Avoid using 'Quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/scalability.md
 137:59  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 207:31  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/sql.md
 86:59   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 99:29   warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 427:36  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/testing_guide/contract/provider_tests.md
 13:20  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/testing_guide/frontend_testing.md
 180:52    warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 830:58    warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite
 1522:156  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/uploads/working_with_uploads.md
 41:53  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/windows.md
 24:9  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

 doc/development/workhorse/index.md
 25:59  warning  Avoid using 'quite', as it has different meanings in British and American English.  gitlab_base.Quite

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

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 like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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 Amy Qualls

Merge request reports