Skip to content

Make terminology in sync between handdbook and docs pages

Peter Lu requested to merge master-patch-2046 into master

What does this MR do and why?

When reviewing issue GitLab should push breaking changes that have m... (gitlab-com/Product#5739 - closed), I found the terminology are slightly different between https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology and https://about.gitlab.com/handbook/product/gitlab-the-product/#definitions, so this MR brings them in sync.

Both pages also have comments:

If updating these definitions, be sure to update them in the product docs as well: https://docs.gitlab.com/ee/development/deprecation_guidelines/index.html#terminology

If updating these definitions, be sure to update them in the handbook as well: https://about.gitlab.com/handbook/product/gitlab-the-product/#definitions

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports