Fix 'GitLab' brand name

content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx

@@ -77,7 +77,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
    | Expire access tokens (checkbox) | (no longer required)                   |
    | Scopes (all checkboxes) | api                                            |
 
-   -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often.
+   -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often.
 
 1. Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx

@@ -150,7 +150,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 ```
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
 ```
 bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443

content/terraform-enterprise/v202206-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202207-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202207-2/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202208-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202208-2/docs/enterprise/vcs/gitlab-eece.mdx

@@ -86,7 +86,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
--> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202208-2/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202208-3/docs/enterprise/vcs/gitlab-eece.mdx

@@ -86,7 +86,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
--> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202208-3/docs/enterprise/vcs/troubleshooting.mdx

@@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202209-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202209-2/docs/enterprise/vcs/gitlab-eece.mdx

@@ -87,7 +87,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
--> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202209-2/docs/enterprise/vcs/troubleshooting.mdx

@@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202210-1/docs/enterprise/vcs/gitlab-eece.mdx

@@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
-    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202210-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202211-1/docs/enterprise/vcs/gitlab-eece.mdx

@@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
-    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202211-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202212-1/docs/enterprise/vcs/gitlab-eece.mdx

@@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
-    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202212-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -124,7 +124,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202212-2/docs/enterprise/vcs/gitlab-eece.mdx

@@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
-    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202212-2/docs/enterprise/vcs/troubleshooting.mdx

@@ -124,7 +124,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)

content/terraform-enterprise/v202301-1/docs/enterprise/vcs/gitlab-eece.mdx

@@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from
     | Expire access tokens (checkbox) | (no longer required)                           |
     | Scopes (all checkboxes)         | api                                            |
 
-    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often.
+    -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often.
 
 4.  Click the "Save application" button, which creates the application and takes you to its page.
 

content/terraform-enterprise/v202301-1/docs/enterprise/vcs/troubleshooting.mdx

@@ -126,7 +126,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca-
 
     openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443
 
-For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
+For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below:
 
     bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443
     CONNECTED(00000003)