From e8b83a4b35a24d5cecac876e9b310ae9f827cce0 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis <axil@gitlab.com> Date: Mon, 6 Nov 2023 07:02:52 +0000 Subject: [PATCH] Redefine High Availability word list usage High Availability should not be avoided to be used, but it should rather be used in the context of the reference architectures. --- doc/development/documentation/styleguide/word_list.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md index 06ac500f3ce0c..96005e0ccd76b 100644 --- a/doc/development/documentation/styleguide/word_list.md +++ b/doc/development/documentation/styleguide/word_list.md @@ -792,7 +792,9 @@ Do not use **handy**. If the user doesn't find the feature or process to be hand ## high availability, HA -Do not use **high availability** or **HA**. Instead, direct readers to the GitLab [reference architectures](../../../administration/reference_architectures/index.md) for information about configuring GitLab for handling greater amounts of users. +Do not use **high availability** or **HA**, except in the GitLab [reference architectures](../../../administration/reference_architectures/index.md#high-availability-ha). Instead, direct readers to the reference architectures for more information about configuring GitLab for handling greater amounts of users. + +Do not use phrases like **high availability setup** to mean a multiple node environment. Instead, use **multi-node setup** or similar. ## higher -- GitLab