Commit 4633f6a6 authored by Craig Norris's avatar Craig Norris

Merge branch 'cc-add-to-recommended-wordlist' into 'master'

Added air gap to the documentation word list

See merge request gitlab-org/gitlab!83905
parents 11bfe91d b6c9d7c4
...@@ -11,6 +11,7 @@ link: https://about.gitlab.com/handbook/communication/#top-misused-terms ...@@ -11,6 +11,7 @@ link: https://about.gitlab.com/handbook/communication/#top-misused-terms
level: warning level: warning
ignorecase: true ignorecase: true
swap: swap:
air(?:-| )?gapped: offline environment
click: select click: select
code base: codebase code base: codebase
config: configuration config: configuration
......
...@@ -97,6 +97,12 @@ The token generated when you create an agent for Kubernetes. Use **agent access ...@@ -97,6 +97,12 @@ The token generated when you create an agent for Kubernetes. Use **agent access
- secret token - secret token
- authentication token - authentication token
## air gap, air-gapped
Use **offline environment** to describe installations that have physical barriers or security policies that prevent or limit internet access. Do not use **air gap**, **air gapped**, or **air-gapped**. For example:
- The firewall policies in an offline environment prevent the computer from accessing the internet.
## allow, enable ## allow, enable
Try to avoid **allow** and **enable**, unless you are talking about security-related features. Try to avoid **allow** and **enable**, unless you are talking about security-related features.
...@@ -1023,7 +1029,7 @@ Do not use **yet** when talking about the product or its features. The documenta ...@@ -1023,7 +1029,7 @@ Do not use **yet** when talking about the product or its features. The documenta
Sometimes you might need to use **yet** when writing a task. If you use Sometimes you might need to use **yet** when writing a task. If you use
**yet**, ensure the surrounding phrases are written **yet**, ensure the surrounding phrases are written
in present tense, active voice. in present tense, active voice.
[View guidance about how to write about future features](index.md#promising-features-in-future-versions). [View guidance about how to write about future features](index.md#promising-features-in-future-versions).
([Vale](../testing.md#vale) rule: [`CurrentStatus.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/CurrentStatus.yml)) ([Vale](../testing.md#vale) rule: [`CurrentStatus.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale/gitlab/CurrentStatus.yml))
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment