From 70a6efc96891e693b8e07a23bf54d90ee530fae8 Mon Sep 17 00:00:00 2001
From: Lysanne Pinto <lpinto@gitlab.com>
Date: Sun, 28 Jul 2024 19:06:49 +0000
Subject: [PATCH] Fix capitalization inconsistencies with zero-downtime
---
doc/administration/packages/container_registry.md | 2 +-
doc/administration/reference_architectures/index.md | 6 +++---
doc/user/application_security/vulnerability_report/index.md | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md
index 42be6bb6d0c88..551c31716cffc 100644
--- a/doc/administration/packages/container_registry.md
+++ b/doc/administration/packages/container_registry.md
@@ -1286,7 +1286,7 @@ itself on the system so that the `gitlab-ctl` command can bring the registry ser
Also, there's no way to save progress or results during the mark phase of the process. Only once
blobs start being deleted is anything permanent done.
-### Continuous Zero-Downtime Garbage Collection
+### Continuous zero-downtime garbage collection
DETAILS:
diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md
index d0dc48108d7b7..8520f1924663a 100644
--- a/doc/administration/reference_architectures/index.md
+++ b/doc/administration/reference_architectures/index.md
@@ -113,9 +113,9 @@ In general then, we'd only recommend you employ HA in the following scenarios:
If you still need to have HA for a lower number of users, this can be achieved with an adjusted [3K architecture](3k_users.md#supported-modifications-for-lower-user-counts-ha).
-#### Zero-Downtime Upgrades
+#### Zero-downtime upgrades
-[Zero-Downtime Upgrades](../../update/zero_downtime.md) are available for standard Reference Architecture environments with HA (Cloud Native Hybrid is [not supported](https://gitlab.com/groups/gitlab-org/cloud-native/-/epics/52)). This allows for an environment to stay up during an upgrade, but the process is more complex as a result and has some limitations as detailed in the documentation.
+[Zero-downtime upgrades](../../update/zero_downtime.md) are available for standard Reference Architecture environments with HA (Cloud Native Hybrid is [not supported](https://gitlab.com/groups/gitlab-org/cloud-native/-/epics/52)). This allows for an environment to stay up during an upgrade, but the process is more complex as a result and has some limitations as detailed in the documentation.
When going through this process it's worth noting that there may still be brief moments of downtime when the HA mechanisms take effect.
@@ -170,7 +170,7 @@ graph TD
L2A("Equivalent to <a href=3k_users.md#testing-methodology>3,000 users</a> or more?")
L2B("Equivalent to <a href=2k_users.md#testing-methodology>2,000 users</a> or less?")
- L3A("<a href=#do-you-need-high-availability-ha>Do you need HA?</a><br>(or Zero-Downtime Upgrades)")
+ L3A("<a href=#do-you-need-high-availability-ha>Do you need HA?</a><br>(or zero-downtime upgrades)")
L3B[Do you have experience with<br/>and want additional resilience<br/>with select components in Kubernetes?]
L4A><b>Recommendation</b><br><br>60 RPS / 3K users architecture with HA<br>and supported reductions]
diff --git a/doc/user/application_security/vulnerability_report/index.md b/doc/user/application_security/vulnerability_report/index.md
index 0b90ff69b452a..3436eea6bbf25 100644
--- a/doc/user/application_security/vulnerability_report/index.md
+++ b/doc/user/application_security/vulnerability_report/index.md
@@ -165,7 +165,7 @@ To filter the list of vulnerabilities:
## Grouping vulnerabilities
-> - Project-level grouping of vulnerabilities[introduced](https://gitlab.com/groups/gitlab-org/-/epics/10164) in GitLab 16.4 [with a flag](../../../administration/feature_flags.md) named `vulnerability_report_grouping`. Disabled by default.
+> - Project-level grouping of vulnerabilities [introduced](https://gitlab.com/groups/gitlab-org/-/epics/10164) in GitLab 16.4 [with a flag](../../../administration/feature_flags.md) named `vulnerability_report_grouping`. Disabled by default.
> - Project-level grouping of vulnerabilities [enabled on self-managed and GitLab Dedicated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134073) in GitLab 16.5.
> - Project-level grouping of vulnerabilities [generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/422509) in GitLab 16.6. Feature flag `vulnerability_report_grouping` removed.
> - Group-level grouping of vulnerabilities [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137778) in GitLab 16.7 with a flag named [`group_level_vulnerability_report_grouping`](https://gitlab.com/gitlab-org/gitlab/-/issues/432778). Disabled by default.
--
GitLab