From bb8c8db8f80d3519a7b03f28ce931edef8479ac6 Mon Sep 17 00:00:00 2001
From: Marcel Amirault <mamirault@gitlab.com>
Date: Tue, 2 Apr 2024 08:03:56 +0000
Subject: [PATCH] Enforce proper grammar for set up
It should be to set up, no to setup, so this fixes
and adds a rule for that grammar issue
---
doc/.vale/gitlab/Substitutions.yml | 2 +
.../reference_architectures/10k_users.md | 70 +++++++++---------
.../reference_architectures/25k_users.md | 74 +++++++++----------
.../reference_architectures/2k_users.md | 42 +++++------
.../reference_architectures/3k_users.md | 66 ++++++++---------
.../reference_architectures/50k_users.md | 70 +++++++++---------
.../reference_architectures/5k_users.md | 66 ++++++++---------
doc/administration/sidekiq/index.md | 2 +-
doc/api/google_cloud_integration.md | 4 +-
doc/api/groups.md | 4 +-
doc/api/settings.md | 2 +-
.../blueprints/capacity_planning/index.md | 2 +-
.../ci_insights.md | 2 +-
.../gitlab_agent_deployments/index.md | 2 +-
.../backend.md | 2 +-
.../blueprints/remote_development/index.md | 2 +-
...et_detection_gem_in_the_same_repository.md | 2 +-
.../blueprints/tailwindcss/index.md | 2 +-
doc/ci/runners/runner_fleet_dashboard.md | 2 +-
doc/development/ai_features/index.md | 4 +-
doc/development/code_suggestions/index.md | 4 +-
doc/development/distributed_tracing.md | 2 +-
doc/development/gotchas.md | 2 +-
doc/development/integrations/index.md | 2 +-
doc/install/docker_troubleshooting.md | 2 +-
doc/integration/clickhouse.md | 4 +-
doc/integration/google_cloud_iam.md | 4 +-
doc/topics/offline/quick_start_guide.md | 4 +-
doc/tutorials/build_application.md | 2 +-
doc/tutorials/scrum_events/index.md | 2 +-
doc/user/gitlab_duo_chat.md | 2 +-
.../integrations/google_artifact_registry.md | 2 +-
32 files changed, 228 insertions(+), 226 deletions(-)
diff --git a/doc/.vale/gitlab/Substitutions.yml b/doc/.vale/gitlab/Substitutions.yml
index 4950e495e728c..4319539aa53fb 100644
--- a/doc/.vale/gitlab/Substitutions.yml
+++ b/doc/.vale/gitlab/Substitutions.yml
@@ -19,6 +19,7 @@ swap:
at least the Owner role: the Owner role
can login: can log in
can log-in: can log in
+ can setup: can set up
can signin: can sign in
can sign-in: can sign in
codequality: code quality
@@ -61,6 +62,7 @@ swap:
the administrator access level: administrator access
to login: to log in
to log-in: to log in
+ to setup: to set up
to signin: to sign in
to sign-in: to sign in
x509: X.509
diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md
index e6a8cba035084..0b6c4370c0b6a 100644
--- a/doc/administration/reference_architectures/10k_users.md
+++ b/doc/administration/reference_architectures/10k_users.md
@@ -177,7 +177,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 10,000 users:
@@ -354,8 +354,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -423,8 +423,8 @@ backend praefect
Refer to your preferred Load Balancer's documentation for further guidance.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -503,8 +503,8 @@ run: node-exporter: (pid 30093) 76833s; run: log: (pid 29663) 76855s
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -673,8 +673,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -703,8 +703,8 @@ If the 'State' column for any node doesn't say "running", check the
before proceeding.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -801,8 +801,8 @@ The following IPs will be used as an example:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1018,8 +1018,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1163,8 +1163,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1277,8 +1277,8 @@ in the second step, do not supply the `EXTERNAL_URL` value.
1. Follow the [post configuration](#praefect-postgresql-post-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1342,8 +1342,8 @@ This is how this would work with a Linux package PostgreSQL setup:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1747,8 +1747,8 @@ To configure Praefect with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1904,8 +1904,8 @@ To configure the Sidekiq nodes, on each one:
1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2108,8 +2108,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2176,8 +2176,8 @@ To configure the Monitoring node:
1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2209,8 +2209,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2231,8 +2231,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2436,7 +2436,7 @@ When setting up a Cloud Native Hybrid environment, it's worth noting that severa
For this setup specifically, the [GitLab Rails](https://docs.gitlab.com/charts/installation/secrets.html#gitlab-rails-secret) and [GitLab Shell](https://docs.gitlab.com/charts/installation/secrets.html#gitlab-rails-secret) secrets should be synced.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md
index e2b0b35e03ff9..0902b1a4a72d0 100644
--- a/doc/administration/reference_architectures/25k_users.md
+++ b/doc/administration/reference_architectures/25k_users.md
@@ -177,7 +177,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 25,000 users:
@@ -356,8 +356,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -421,14 +421,14 @@ backend praefect
Refer to your preferred Load Balancer's documentation for further guidance.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -507,8 +507,8 @@ run: node-exporter: (pid 30093) 76833s; run: log: (pid 29663) 76855s
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -677,8 +677,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -707,8 +707,8 @@ If the 'State' column for any node doesn't say "running", check the
before proceeding.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -805,8 +805,8 @@ The following IPs will be used as an example:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1020,8 +1020,8 @@ a node and change its status from primary to replica (and vice versa).
Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.html) are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1169,8 +1169,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1283,8 +1283,8 @@ in the second step, do not supply the `EXTERNAL_URL` value.
1. Follow the [post configuration](#praefect-postgresql-post-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1346,8 +1346,8 @@ This is how this would work with a Linux package PostgreSQL setup:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1751,8 +1751,8 @@ To configure Praefect with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1908,8 +1908,8 @@ To configure the Sidekiq nodes, on each one:
1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2114,8 +2114,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2182,8 +2182,8 @@ To configure the Monitoring node:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2215,8 +2215,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2237,8 +2237,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2435,7 +2435,7 @@ specifically to accommodate several additional deployments. However, if your dep
pool as given, you can increase the node pool accordingly.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md
index bdaf4bb7a7ee5..8a6970de7adb6 100644
--- a/doc/administration/reference_architectures/2k_users.md
+++ b/doc/administration/reference_architectures/2k_users.md
@@ -120,7 +120,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 2,000 users:
@@ -254,8 +254,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -339,8 +339,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -407,8 +407,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -606,8 +606,8 @@ To configure Gitaly with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -741,8 +741,8 @@ To configure the Sidekiq server, on the server node you want to use for Sidekiq:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -921,8 +921,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1018,8 +1018,8 @@ running [Prometheus](../monitoring/prometheus/index.md):
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1051,8 +1051,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1077,8 +1077,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1232,7 +1232,7 @@ specifically to accommodate several additional deployments. However, if your dep
pool as given, you can increase the node pool accordingly.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md
index eff1462710b1f..1bc2a28cd929b 100644
--- a/doc/administration/reference_architectures/3k_users.md
+++ b/doc/administration/reference_architectures/3k_users.md
@@ -172,7 +172,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 3,000 users:
@@ -344,8 +344,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -413,8 +413,8 @@ backend praefect
Refer to your preferred Load Balancer's documentation for further guidance.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -628,8 +628,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -778,8 +778,8 @@ run: sentinel: (pid 30098) 76832s; run: log: (pid 29704) 76850s
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -948,8 +948,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -978,8 +978,8 @@ If the 'State' column for any node doesn't say "running", check the
before proceeding.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1093,8 +1093,8 @@ The following IPs will be used as an example:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1206,8 +1206,8 @@ in the second step, do not supply the `EXTERNAL_URL` value.
1. Follow the [post configuration](#praefect-postgresql-post-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1269,8 +1269,8 @@ This is how this would work with a Linux package PostgreSQL setup:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1678,8 +1678,8 @@ To configure Praefect with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1843,8 +1843,8 @@ To configure the Sidekiq nodes, on each one:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2065,8 +2065,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2140,8 +2140,8 @@ running [Prometheus](../monitoring/prometheus/index.md):
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2173,8 +2173,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2195,8 +2195,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2413,7 +2413,7 @@ specifically to accommodate several additional deployments. However, if your dep
pool as given, you can increase the node pool accordingly.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md
index d80bf01e3a745..3064e0aee7814 100644
--- a/doc/administration/reference_architectures/50k_users.md
+++ b/doc/administration/reference_architectures/50k_users.md
@@ -176,7 +176,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 50,000 users:
@@ -362,8 +362,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -431,8 +431,8 @@ backend praefect
Refer to your preferred Load Balancer's documentation for further guidance.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -511,8 +511,8 @@ run: node-exporter: (pid 30093) 76833s; run: log: (pid 29663) 76855s
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -682,8 +682,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -712,8 +712,8 @@ If the 'State' column for any node doesn't say "running", check the
before proceeding.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -810,8 +810,8 @@ The following IPs will be used as an example:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1031,8 +1031,8 @@ a node and change its status from primary to replica (and vice versa).
Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.html) are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1176,8 +1176,8 @@ a node and change its status from primary to replica (and vice versa).
Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.html) are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1290,8 +1290,8 @@ in the second step, do not supply the `EXTERNAL_URL` value.
1. Follow the [post configuration](#praefect-postgresql-post-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1355,8 +1355,8 @@ This is how this would work with a Linux package PostgreSQL setup:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1760,8 +1760,8 @@ To configure Praefect with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1918,8 +1918,8 @@ To configure the Sidekiq nodes, on each one:
1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2128,8 +2128,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2196,8 +2196,8 @@ To configure the Monitoring node:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2229,8 +2229,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2251,8 +2251,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2449,7 +2449,7 @@ specifically to accommodate several additional deployments. However, if your dep
pool as given, you can increase the node pool accordingly.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md
index b9d4bf619cae3..06efcf3aa8a29 100644
--- a/doc/administration/reference_architectures/5k_users.md
+++ b/doc/administration/reference_architectures/5k_users.md
@@ -172,7 +172,7 @@ The results of this testing are [available publicly on the GPT wiki](https://git
The load balancers used for testing were HAProxy for Linux package environments or equivalent Cloud Provider services via NGINX Ingress for Cloud Native Hybrids. Note that these selections do not represent a specific requirement or recommendation as most [reputable load balancers are expected to work](#configure-the-external-load-balancer).
-## Setup components
+## Set up components
To set up GitLab and its components to accommodate up to 5,000 users:
@@ -344,8 +344,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
for details on managing SSL certificates and configuring NGINX.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -413,8 +413,8 @@ backend praefect
Refer to your preferred Load Balancer's documentation for further guidance.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -628,8 +628,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/redis.
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -777,8 +777,8 @@ run: sentinel: (pid 30098) 76832s; run: log: (pid 29704) 76850s
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -947,8 +947,8 @@ Advanced [configuration options](https://docs.gitlab.com/omnibus/settings/databa
are supported and can be added if needed.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -977,8 +977,8 @@ If the 'State' column for any node doesn't say "running", check the
before proceeding.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1092,8 +1092,8 @@ The following IPs are used as an example:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1206,8 +1206,8 @@ in the second step, do not supply the `EXTERNAL_URL` value.
1. Follow the [post configuration](#praefect-postgresql-post-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1269,8 +1269,8 @@ This is how this would work with a Linux package PostgreSQL setup:
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1674,8 +1674,8 @@ To configure Praefect with TLS:
1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -1839,8 +1839,8 @@ more nodes can be added as required. You can also tune your Sidekiq nodes to
run [multiple Sidekiq processes](../sidekiq/extra_sidekiq_processes.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2064,8 +2064,8 @@ the [HTTPS documentation](https://docs.gitlab.com/omnibus/settings/ssl/index.htm
1. [Configure fast lookup of authorized SSH keys in the database](../operations/fast_ssh_key_lookup.md).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2139,8 +2139,8 @@ running [Prometheus](../monitoring/prometheus/index.md):
```
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2172,8 +2172,8 @@ There are plans to [enable the use of a single bucket](https://gitlab.com/gitlab
in the future.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2194,8 +2194,8 @@ cluster alongside your instance, read how to
[choose the optimal cluster configuration](../../integration/advanced_search/elasticsearch.md#guidance-on-choosing-optimal-cluster-configuration).
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
@@ -2388,7 +2388,7 @@ specifically to accommodate several additional deployments. However, if your dep
pool as given, you can increase the node pool accordingly.
<div align="right">
- <a type="button" class="btn btn-default" href="#setup-components">
- Back to setup components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
+ <a type="button" class="btn btn-default" href="#set-up-components">
+ Back to set up components <i class="fa fa-angle-double-up" aria-hidden="true"></i>
</a>
</div>
diff --git a/doc/administration/sidekiq/index.md b/doc/administration/sidekiq/index.md
index 73a6cf5cecf53..977d061bc9f18 100644
--- a/doc/administration/sidekiq/index.md
+++ b/doc/administration/sidekiq/index.md
@@ -123,7 +123,7 @@ Updates to example must be made at:
########################################
## Must be the same in every sentinel node.
- redis['master_name'] = 'gitlab-redis' # Required if you have setup redis cluster
+ redis['master_name'] = 'gitlab-redis' # Required if you have set up redis cluster
## The same password for Redis authentication you set up for the master node.
redis['master_password'] = '<redis_master_password>'
diff --git a/doc/api/google_cloud_integration.md b/doc/api/google_cloud_integration.md
index cd247dc90f32f..513d26cfc667c 100644
--- a/doc/api/google_cloud_integration.md
+++ b/doc/api/google_cloud_integration.md
@@ -51,9 +51,9 @@ curl --request GET \
--url "https://gitlab.com/api/v4/projects/<your_project_id>/google_cloud/setup/wlif.sh"
```
-### Script to setup a Google Cloud integration
+### Script to set up a Google Cloud integration
- > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144787) in GitLab 16.10.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144787) in GitLab 16.10.
Users with at least the Maintainer role for the project can use the following endpoint to
query a shell script to set up a Google Cloud integration:
diff --git a/doc/api/groups.md b/doc/api/groups.md
index 256995254d30d..1454946eb2fed 100644
--- a/doc/api/groups.md
+++ b/doc/api/groups.md
@@ -863,7 +863,7 @@ Parameters:
| `parent_id` | integer | no | The parent group ID for creating nested group. |
| `project_creation_level` | string | no | Determine if developers can create projects in the group. Can be `noone` (No one), `maintainer` (users with the Maintainer role), or `developer` (users with the Developer or Maintainer role). |
| `request_access_enabled` | boolean | no | Allow users to request member access. |
-| `require_two_factor_authentication` | boolean | no | Require all users in this group to setup Two-factor authentication. |
+| `require_two_factor_authentication` | boolean | no | Require all users in this group to set up two-factor authentication. |
| `share_with_group_lock` | boolean | no | Prevent sharing a project with another group within this group. |
| `subgroup_creation_level` | string | no | Allowed to [create subgroups](../user/group/subgroups/index.md#create-a-subgroup). Can be `owner` (Owners), or `maintainer` (users with the Maintainer role). |
| `two_factor_grace_period` | integer | no | Time before Two-factor authentication is enforced (in hours). |
@@ -1036,7 +1036,7 @@ PUT /groups/:id
| `prevent_sharing_groups_outside_hierarchy` | boolean | no | See [Prevent group sharing outside the group hierarchy](../user/group/access_and_permissions.md#prevent-group-sharing-outside-the-group-hierarchy). This attribute is only available on top-level groups. [Introduced in GitLab 14.1](https://gitlab.com/gitlab-org/gitlab/-/issues/333721) |
| `project_creation_level` | string | no | Determine if developers can create projects in the group. Can be `noone` (No one), `maintainer` (users with the Maintainer role), or `developer` (users with the Developer or Maintainer role). |
| `request_access_enabled` | boolean | no | Allow users to request member access. |
-| `require_two_factor_authentication` | boolean | no | Require all users in this group to setup Two-factor authentication. |
+| `require_two_factor_authentication` | boolean | no | Require all users in this group to set up two-factor authentication. |
| `shared_runners_setting` | string | no | See [Options for `shared_runners_setting`](#options-for-shared_runners_setting). Enable or disable shared runners for a group's subgroups and projects. |
| `share_with_group_lock` | boolean | no | Prevent sharing a project with another group within this group. |
| `subgroup_creation_level` | string | no | Allowed to [create subgroups](../user/group/subgroups/index.md#create-a-subgroup). Can be `owner` (Owners), or `maintainer` (users with the Maintainer role). |
diff --git a/doc/api/settings.md b/doc/api/settings.md
index 21abfa415ab4d..d325b16750e99 100644
--- a/doc/api/settings.md
+++ b/doc/api/settings.md
@@ -576,7 +576,7 @@ listed in the descriptions of the relevant settings.
| `repository_size_limit` | integer | no | Size limit per repository (MB). Premium and Ultimate only. |
| `repository_storages_weighted` | hash of strings to integers | no | (GitLab 13.1 and later) Hash of names of taken from `gitlab.yml` to [weights](../administration/repository_storage_paths.md#configure-where-new-repositories-are-stored). New projects are created in one of these stores, chosen by a weighted random selection. |
| `require_admin_approval_after_user_signup` | boolean | no | When enabled, any user that signs up for an account using the registration form is placed under a **Pending approval** state and has to be explicitly [approved](../administration/moderate_users.md) by an administrator. |
-| `require_two_factor_authentication` | boolean | no | (**If enabled, requires:** `two_factor_grace_period`) Require all users to set up Two-factor authentication. |
+| `require_two_factor_authentication` | boolean | no | (**If enabled, requires:** `two_factor_grace_period`) Require all users to set up two-factor authentication. |
| `restricted_visibility_levels` | array of strings | no | Selected levels cannot be used by non-Administrator users for groups, projects or snippets. Can take `private`, `internal` and `public` as a parameter. Default is `null` which means there is no restriction.[Changed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131203) in GitLab 16.4: cannot select levels that are set as `default_project_visibility` and `default_group_visibility`. |
| `rsa_key_restriction` | integer | no | The minimum allowed bit length of an uploaded RSA key. Default is `0` (no restriction). `-1` disables RSA keys. |
| `session_expire_delay` | integer | no | Session duration in minutes. GitLab restart is required to apply changes. |
diff --git a/doc/architecture/blueprints/capacity_planning/index.md b/doc/architecture/blueprints/capacity_planning/index.md
index e497868390499..54daabc9e0d0d 100644
--- a/doc/architecture/blueprints/capacity_planning/index.md
+++ b/doc/architecture/blueprints/capacity_planning/index.md
@@ -179,7 +179,7 @@ For additional visibility, we may want to consider enabling getting Slack update
### Tamland as a Service (not chosen)
-An alternative design, we don't consider an option at this point, is to setup Tamland as a Service and run it fully **outside** of tenant environments.
+An alternative design, we don't consider an option at this point, is to set up Tamland as a Service and run it fully **outside** of tenant environments.
diff --git a/doc/architecture/blueprints/ci_builds_runner_fleet_metrics/ci_insights.md b/doc/architecture/blueprints/ci_builds_runner_fleet_metrics/ci_insights.md
index 72d82558eb76b..256f8a1eee37e 100644
--- a/doc/architecture/blueprints/ci_builds_runner_fleet_metrics/ci_insights.md
+++ b/doc/architecture/blueprints/ci_builds_runner_fleet_metrics/ci_insights.md
@@ -92,7 +92,7 @@ Make sure that we can get information on how often this page is viewed. If we do
### Routing
-We are planning to have new routes for the page and some redicts to setup. To read more about the routing proposal, see the [related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/437556)
+We are planning to have new routes for the page and some redicts to set up. To read more about the routing proposal, see the [related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/437556)
### Pipelines duration graph
diff --git a/doc/architecture/blueprints/gitlab_agent_deployments/index.md b/doc/architecture/blueprints/gitlab_agent_deployments/index.md
index 5fd5006c637af..484616b6d5cfa 100644
--- a/doc/architecture/blueprints/gitlab_agent_deployments/index.md
+++ b/doc/architecture/blueprints/gitlab_agent_deployments/index.md
@@ -186,7 +186,7 @@ The microservice project setup can be improved by [Multi-Project Deployment Pipe
- Deployment Project can behave as the shared deployment engine for any upstream application projects and environments.
- Environments can be created within the application projects. It gives more visibility of environments for developers.
- Deployment Project can be managed under Operator group. More segregation of duties.
-- Users don't need to setup [RBAC to restrict CI/CD jobs](../../../user/clusters/agent/ci_cd_workflow.md#restrict-project-and-group-access-by-using-impersonation).
+- Users don't need to set up [RBAC to restrict CI/CD jobs](../../../user/clusters/agent/ci_cd_workflow.md#restrict-project-and-group-access-by-using-impersonation).
- This is especitially helpful for [dynamic environments](../../../ci/environments/index.md#create-a-dynamic-environment), such as Review Apps.
```mermaid
diff --git a/doc/architecture/blueprints/google_artifact_registry_integration/backend.md b/doc/architecture/blueprints/google_artifact_registry_integration/backend.md
index 0e2c528a8b0d5..f5618e7afc4ab 100644
--- a/doc/architecture/blueprints/google_artifact_registry_integration/backend.md
+++ b/doc/architecture/blueprints/google_artifact_registry_integration/backend.md
@@ -38,7 +38,7 @@ The client will then need to expose three functions: `#repository`, `#docker_ima
Before calling the official client, this class will need to check the user permissions. The given `User` should have `read_gcp_artifact_registry_repository` on the `Project` related with the `Integrations::GoogleCloudPlatform::ArtifactRegistry`.
-Lastly, to setup the official client, we will need to properly set:
+Lastly, to set up the official client, we will need to properly set:
- the [timeout](https://github.com/googleapis/google-cloud-ruby/blob/a64ed1de61a6f1b5752e7c8e01d6a79365e6de67/google-cloud-artifact_registry-v1/lib/google/cloud/artifact_registry/v1/artifact_registry/operations.rb#L646).
- the [retry_policy](https://github.com/googleapis/google-cloud-ruby/blob/a64ed1de61a6f1b5752e7c8e01d6a79365e6de67/google-cloud-artifact_registry-v1/lib/google/cloud/artifact_registry/v1/artifact_registry/operations.rb#L652).
diff --git a/doc/architecture/blueprints/remote_development/index.md b/doc/architecture/blueprints/remote_development/index.md
index 41ed274667875..5c23e0b7b11c7 100644
--- a/doc/architecture/blueprints/remote_development/index.md
+++ b/doc/architecture/blueprints/remote_development/index.md
@@ -593,7 +593,7 @@ flowchart TB
#### Auth annotations on the Ingress resource
-Use auth annotations on the Ingress resource to allow Ingress controllers(for example, `ingress-nginx`) to delegate authentication and authorization to a separate process. The challenge is that these annotations are not standardized (that is, not part of the [Ingress specification](https://kubernetes.io/docs/concepts/services-networking/ingress/)) and may not be supported across different Ingress controllers. We would need to document the process to setup our Auth provider for each of the Ingress controllers. However, if they do become a part of the new [Gateway API](https://gateway-api.sigs.k8s.io/concepts/security-model/), we will reconsider this decision.
+Use auth annotations on the Ingress resource to allow Ingress controllers(for example, `ingress-nginx`) to delegate authentication and authorization to a separate process. The challenge is that these annotations are not standardized (that is, not part of the [Ingress specification](https://kubernetes.io/docs/concepts/services-networking/ingress/)) and may not be supported across different Ingress controllers. We would need to document the process to set up our Auth provider for each of the Ingress controllers. However, if they do become a part of the new [Gateway API](https://gateway-api.sigs.k8s.io/concepts/security-model/), we will reconsider this decision.
For `ingress-nginx`, the auth annotations would be:
diff --git a/doc/architecture/blueprints/secret_detection/decisions/002_store_the_secret_detection_gem_in_the_same_repository.md b/doc/architecture/blueprints/secret_detection/decisions/002_store_the_secret_detection_gem_in_the_same_repository.md
index f743dd2bfac2f..14f8d9015b4a9 100644
--- a/doc/architecture/blueprints/secret_detection/decisions/002_store_the_secret_detection_gem_in_the_same_repository.md
+++ b/doc/architecture/blueprints/secret_detection/decisions/002_store_the_secret_detection_gem_in_the_same_repository.md
@@ -18,7 +18,7 @@ We evaluated two possible approaches:
1. Store the library [in the same repository](../../../../development/gems.md#in-the-same-repo) as the monolith.
1. Store the library [in an external repository](../../../../development/gems.md#in-the-external-repo).
-Each approach came with some advantages and disadvantages, mostly around distribution, consistency, maintainability, and the overhead of having to setup review and release workflows and similar processes. See below for more information.
+Each approach came with some advantages and disadvantages, mostly around distribution, consistency, maintainability, and the overhead of having to set up review and release workflows and similar processes. See below for more information.
### Within the same repository as the monolith
diff --git a/doc/architecture/blueprints/tailwindcss/index.md b/doc/architecture/blueprints/tailwindcss/index.md
index 6d58e0dae8e8e..726785138bbc3 100644
--- a/doc/architecture/blueprints/tailwindcss/index.md
+++ b/doc/architecture/blueprints/tailwindcss/index.md
@@ -64,7 +64,7 @@ Here are a few reasons that led us to choosing Tailwind CSS over similar tools:
- Tailwind CSS is well maintained and keeps evolving without getting bloated.
- It integrates well in all of our tech stacks
- Ruby on Rails projects can leverage the [`tailwindcss-rails` Gem](https://tailwindcss.com/docs/guides/ruby-on-rails).
- - Nuxt apps can setup the [`tailwindcss` module](https://nuxt.com/modules/tailwindcss).
+ - Nuxt apps can set up the [`tailwindcss` module](https://nuxt.com/modules/tailwindcss).
- More generic frontend stacks can use the [`tailwindcss` Node module](https://tailwindcss.com/docs/installation).
### Goals
diff --git a/doc/ci/runners/runner_fleet_dashboard.md b/doc/ci/runners/runner_fleet_dashboard.md
index e9a3495ffe264..ab0826088c392 100644
--- a/doc/ci/runners/runner_fleet_dashboard.md
+++ b/doc/ci/runners/runner_fleet_dashboard.md
@@ -84,7 +84,7 @@ To help us improve the Runner Fleet Dashboard, you can provide feedback in
[issue 421737](https://gitlab.com/gitlab-org/gitlab/-/issues/421737).
In particular:
-- How easy or difficult it was to setup GitLab to make the dashboard work.
+- How easy or difficult it was to set up GitLab to make the dashboard work.
- How useful you found the dashboard.
- What other information you would like to see on that dashboard.
- Any other related thoughts and ideas.
diff --git a/doc/development/ai_features/index.md b/doc/development/ai_features/index.md
index ce4705cc36359..c5978963e5931 100644
--- a/doc/development/ai_features/index.md
+++ b/doc/development/ai_features/index.md
@@ -164,11 +164,11 @@ GITLAB_SIMULATE_SAAS=1 RAILS_ENV=development bundle exec rake 'gitlab:duo:setup[
### Bypass AI Gateway
NOTE:
-You need to setup AI Gateway since GitLab 16.8.
+You need to set up AI Gateway since GitLab 16.8.
It's a recommended way to test AI features. Sending requests directly to LLMs could lead to unnoticed bugs.
Use this workaround with caution.
-To setup direct requests to LLMs you have to:
+To set up direct requests to LLMs you have to:
1. Disable the feature flag.
diff --git a/doc/development/code_suggestions/index.md b/doc/development/code_suggestions/index.md
index 5b477545b935b..ce22f4031f330 100644
--- a/doc/development/code_suggestions/index.md
+++ b/doc/development/code_suggestions/index.md
@@ -23,7 +23,7 @@ This should enable everyone to see locally any change in an IDE being sent to th
1. In VS Code, go to the Extensions page and find "GitLab Workflow" in the list.
1. Open the extension settings by clicking a small cog icon and select "Extension Settings" option.
1. Check a "GitLab: Debug" checkbox.
- 1. If you'd like to test code suggestions are working from inside the VS Code Extension, then follow the [steps to setup a personal access token](https://gitlab.com/gitlab-org/gitlab-vscode-extension/#setup) with your GDK inside the new window of VS Code that pops up when you run the "Run and Debug" command.
+ 1. If you'd like to test code suggestions are working from inside the VS Code Extension, then follow the [steps to set up a personal access token](https://gitlab.com/gitlab-org/gitlab-vscode-extension/#setup) with your GDK inside the new window of VS Code that pops up when you run the "Run and Debug" command.
- Once you complete the steps below, to test you are hitting your local `/code_suggestions/completions` endpoint and not production, follow these steps:
1. Inside the new window, in the built in terminal select the "Output" tab then "GitLab Language Server" from the drop down menu on the right.
1. Open a new file inside of this VS Code window and begin typing to see code suggestions in action.
@@ -75,7 +75,7 @@ with the deployed staging AI Gateway. To do this:
### Setup instructions to use GDK with the Code Suggestions Add-on
On February 15, 2023 we will require the code suggestions add-on subscription to be able to use code suggestions.
-To setup your GDK for local development using the add-on, please follow these steps:
+To set up your GDK for local development using the add-on, please follow these steps:
1. Drop a note in the `#s_fulfillment` or `s_fulfillment_engineering` internal Slack channel to request an activation code with the Code Suggestions add-on.
1. Someone will reach out to you with a code.
diff --git a/doc/development/distributed_tracing.md b/doc/development/distributed_tracing.md
index 60da0cd146f6f..2f3cce29d73ba 100644
--- a/doc/development/distributed_tracing.md
+++ b/doc/development/distributed_tracing.md
@@ -189,7 +189,7 @@ $ docker run \
#### Using the Jaeger process
-Without Docker, the all-in-one process is still easy to setup.
+Without Docker, the all-in-one process is still easy to set up.
1. Download the [latest Jaeger release](https://github.com/jaegertracing/jaeger/releases) for your
platform.
diff --git a/doc/development/gotchas.md b/doc/development/gotchas.md
index 0f872bfff01fb..8d8519fc4e1fc 100644
--- a/doc/development/gotchas.md
+++ b/doc/development/gotchas.md
@@ -164,7 +164,7 @@ end
```
Since Active Record is not calling the `.new` method on model classes to instantiate the objects,
-you should use `expect_next_found_instance_of` or `allow_next_found_instance_of` mock helpers to setup mock on objects returned by Active Record query & finder methods._
+you should use `expect_next_found_instance_of` or `allow_next_found_instance_of` mock helpers to set up mock on objects returned by Active Record query & finder methods._
It is also possible to set mocks and expectations for multiple instances of the same Active Record model by using the `expect_next_found_(number)_instances_of` and `allow_next_found_(number)_instances_of` helpers, like so;
diff --git a/doc/development/integrations/index.md b/doc/development/integrations/index.md
index 191c8ce6f11dd..b234b2dcabbe4 100644
--- a/doc/development/integrations/index.md
+++ b/doc/development/integrations/index.md
@@ -248,7 +248,7 @@ This method should return an array of hashes for each field, where the keys can
### Define sections
All integrations should define `Integration#sections` which split the form into smaller sections,
-making it easier for users to setup the integration.
+making it easier for users to set up the integration.
The most commonly used sections are pre-defined and already include some UI:
diff --git a/doc/install/docker_troubleshooting.md b/doc/install/docker_troubleshooting.md
index dfd4525d96623..6ddaa677fa57a 100644
--- a/doc/install/docker_troubleshooting.md
+++ b/doc/install/docker_troubleshooting.md
@@ -65,7 +65,7 @@ Our recommendation is to switch to using the native Docker install for your
platform, instead of using Docker Toolbox.
If you cannot use the native Docker install (Windows 10 Home Edition, or Windows 7/8),
-then an alternative solution is to setup NFS mounts instead of VirtualBox shares for
+then an alternative solution is to set up NFS mounts instead of VirtualBox shares for
Docker Toolbox's boot2docker.
## Linux ACL issues
diff --git a/doc/integration/clickhouse.md b/doc/integration/clickhouse.md
index cc2b706a27611..c2c2590d51387 100644
--- a/doc/integration/clickhouse.md
+++ b/doc/integration/clickhouse.md
@@ -11,11 +11,11 @@ DETAILS:
This feature is an [Experiment](../policy/experiment-beta-support.md).
-Instructions about how to setup integration between GitLab and ClickHouse database.
+Instructions about how to set up integration between GitLab and ClickHouse database.
## Setup
-To setup ClickHouse as the GitLab data storage:
+To set up ClickHouse as the GitLab data storage:
1. [Run ClickHouse Cluster and configure database](#run-and-configure-clickhouse).
1. [Configure GitLab connection to Clickhouse](#configure-the-gitlab-connection-to-clickhouse).
diff --git a/doc/integration/google_cloud_iam.md b/doc/integration/google_cloud_iam.md
index be1f681a95922..979daa5614bb3 100644
--- a/doc/integration/google_cloud_iam.md
+++ b/doc/integration/google_cloud_iam.md
@@ -30,10 +30,10 @@ grant GitLab workloads access to Google Cloud resources through OpenID Connect
## Create and configure a workload identity federation
-To setup the workload identity federation you can either:
+To set up the workload identity federation you can either:
- Use the GitLab UI for a guided setup.
-- Use the Google Cloud CLI to setup the workload identity federation manually.
+- Use the Google Cloud CLI to set up the workload identity federation manually.
### With the GitLab UI
diff --git a/doc/topics/offline/quick_start_guide.md b/doc/topics/offline/quick_start_guide.md
index 5d00d6ffb0b6e..4a7aa6faf274a 100644
--- a/doc/topics/offline/quick_start_guide.md
+++ b/doc/topics/offline/quick_start_guide.md
@@ -62,7 +62,7 @@ sudo dpkg -i <package_name>.deb
URL for the `EXTERNAL_URL` installation step. Once installed, we can manually
configure the SSL ourselves.
-It is strongly recommended to setup a domain for IP resolution rather than bind
+It is strongly recommended to set up a domain for IP resolution rather than bind
to the server's IP address. This better ensures a stable target for our certs' CN
and makes long-term resolution simpler.
@@ -333,7 +333,7 @@ echo "All objects saved to $PKG_METADATA_DIR"
### Automatic synchronization
Your GitLab instance is synchronized [regularly](https://gitlab.com/gitlab-org/gitlab/-/blob/63a187d47f6da353ba4514650bbbbeb99c356325/config/initializers/1_settings.rb#L840-842) with the contents of the `package_metadata` directory.
-To automatically update your local copy with the upstream changes, a cron job can be added to periodically download new exports. For example, the following crontabs can be added to setup a cron job that runs every 30 minutes.
+To automatically update your local copy with the upstream changes, a cron job can be added to periodically download new exports. For example, the following crontabs can be added to set up a cron job that runs every 30 minutes.
For License Scanning:
diff --git a/doc/tutorials/build_application.md b/doc/tutorials/build_application.md
index 7e5f5e7288be1..810c53ead24c3 100644
--- a/doc/tutorials/build_application.md
+++ b/doc/tutorials/build_application.md
@@ -22,7 +22,7 @@ Use CI/CD pipelines to automatically build, test, and deploy your code.
| [Find CI/CD examples and templates](../ci/examples/index.md#cicd-examples) | Use these examples and templates to set up CI/CD for your use case. | |
| <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> [Understand CI/CD rules](https://www.youtube.com/watch?v=QjQc-zeL16Q) (8m 56s) | Learn more about how to use CI/CD rules. | |
| [Use Auto DevOps to deploy an application](../topics/autodevops/cloud_deployments/auto_devops_with_gke.md) | Deploy an application to Google Kubernetes Engine (GKE). | |
-| [Using Buildah in a rootless container with GitLab Runner Operator on OpenShift](../ci/docker/buildah_rootless_tutorial.md) | Learn how to setup GitLab Runner Operator on OpenShift to build Docker images with Buildah in a rootless container | |
+| [Using Buildah in a rootless container with GitLab Runner Operator on OpenShift](../ci/docker/buildah_rootless_tutorial.md) | Learn how to set up GitLab Runner Operator on OpenShift to build Docker images with Buildah in a rootless container | |
## Configure GitLab Runner
diff --git a/doc/tutorials/scrum_events/index.md b/doc/tutorials/scrum_events/index.md
index 8038df51eaed5..1f917746d69d8 100644
--- a/doc/tutorials/scrum_events/index.md
+++ b/doc/tutorials/scrum_events/index.md
@@ -241,7 +241,7 @@ journey:
flowchart TD
Epic["Epic: When using the application, I need to create an <br> account, so that I can use the application features"] --> Issue1["Issue: When creating my account, I need to specify my email address,<br> so that I can receive future updates from the application"]
Epic --> Issue2["Issue: When creating my account, I need to <br>specify a password, so that my account remains secure"]
- Epic --> Issue3["Issue: When creating my account and entering the required info, I need to <br>finalize creating my account, so that I can login"]
+ Epic --> Issue3["Issue: When creating my account and entering the required info, I need to <br>finalize creating my account, so that I can log in"]
```
You've taken the feature of an unmodified account sign-up for an application and broke it down into
diff --git a/doc/user/gitlab_duo_chat.md b/doc/user/gitlab_duo_chat.md
index b997139e162ab..e419b6e541fba 100644
--- a/doc/user/gitlab_duo_chat.md
+++ b/doc/user/gitlab_duo_chat.md
@@ -41,7 +41,7 @@ GitLab Duo Chat is a Beta feature. We're continuously extending the capabilities
## Watch a demo
<div class="video-fallback">
- <a href="https://youtu.be/l6vsd1HMaYA?si=etXpFbj1cBvWyj3_">View how to setup and use GitLab Duo Chat</a>.
+ <a href="https://youtu.be/l6vsd1HMaYA?si=etXpFbj1cBvWyj3_">View how to set up and use GitLab Duo Chat</a>.
</div>
<figure class="video-container">
<iframe src="https://www.youtube-nocookie.com/embed/l6vsd1HMaYA?si=etXpFbj1cBvWyj3_" frameborder="0" allowfullscreen> </iframe>
diff --git a/doc/user/project/integrations/google_artifact_registry.md b/doc/user/project/integrations/google_artifact_registry.md
index 609c57e5221b4..488270ff8a52b 100644
--- a/doc/user/project/integrations/google_artifact_registry.md
+++ b/doc/user/project/integrations/google_artifact_registry.md
@@ -46,7 +46,7 @@ To connect a Google Artifact Registry repository to a GitLab project:
- **Google Cloud project ID**: The [Google Cloud project ID](https://cloud.google.com/resource-manager/docs/creating-managing-projects#identifying_projects) where the Artifact Registry repository is located.
- **Repository name**: The name of the Artifact Registry repository.
- **Repository location**: The [Google Cloud location](https://cloud.google.com/about/locations) of the Artifact Registry repository.
-1. Follow the onscreen instructions to setup the Google Cloud Identity and Access Management (IAM) policies. For more information about the types of policies, see [IAM policies](#iam-policies).
+1. Follow the onscreen instructions to set up the Google Cloud Identity and Access Management (IAM) policies. For more information about the types of policies, see [IAM policies](#iam-policies).
1. Select **Save changes**.
You should now see a **Google Artifact Registry** entry in the sidebar under **Deploy**.
--
GitLab