From 185438e8b672af917bb0d514225497b5efe994bc Mon Sep 17 00:00:00 2001 From: Phillip Wells <pwells@gitlab.com> Date: Tue, 23 Apr 2024 23:18:12 +0000 Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: Phillip Wells <pwells@gitlab.com> --- .../documentation/styleguide/word_list.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md index 6d056e05351b1..40c81e4091977 100644 --- a/doc/development/documentation/styleguide/word_list.md +++ b/doc/development/documentation/styleguide/word_list.md @@ -2040,6 +2040,21 @@ Use sentence case for **Value stream forecasting**. On first mention on a page, Thereafter, use **Value stream forecasting** by itself. +## version, v + +To describe versions of GitLab, use **GitLab `<version number>`**. For example: + +- You must have GitLab 16.0 or later. + +To describe other software, use the same style as the documentation for that software. +For example: + +- In Kubernetes 1.4, you can... + +Pay attention to spacing by the letter **v**. In semantic versioning, no space exists after the **v**. For example: + +- v1.2.3 + ## via Do not use Latin abbreviations. Use **with**, **through**, or **by using** instead. ([Vale](../testing/vale.md) rule: [`LatinTerms.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/LatinTerms.yml)) -- GitLab