Replace "the the" with "the"

.gitlab/issue_templates/Feature proposal - detailed.md

@@ -91,7 +91,7 @@ See the test engineering planning process and reach out to your counterpart Soft
 <!--
 Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
 
-Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md
+Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md
 -->
 
 ### What is the type of buyer?

doc/topics/autodevops/upgrading_auto_deploy_dependencies.md

@@ -258,7 +258,7 @@ change. If that happens, the deployment job fails with a message similar to:
 ```plaintext
 *************************************************************************************
                                    [WARNING]
-Detected a major version difference between the the chart that is currently deploying (auto-deploy-app-v0.7.0), and the previously deployed chart (auto-deploy-app-v1.0.0).
+Detected a major version difference between the chart that is currently deploying (auto-deploy-app-v0.7.0), and the previously deployed chart (auto-deploy-app-v1.0.0).
 A new major version might not be backward compatible with the current release (production). The deployment could fail or be stuck in an unrecoverable status.
 ...
 ```

qa/README.md

@@ -124,7 +124,7 @@ GITLAB_USERNAME=jsmith GITLAB_PASSWORD=password bundle exec bin/qa Test::Instanc
 ```
 
 Some QA tests require logging in as an admin user. By default, the QA
-tests will use the the same `root` user seeded by the GDK.
+tests will use the same `root` user seeded by the GDK.
 
 If you need to authenticate with different admin credentials, you can
 provide the `GITLAB_ADMIN_USERNAME` and `GITLAB_ADMIN_PASSWORD`

workhorse/doc/architecture/channel.md

@@ -145,7 +145,7 @@ also upgraded.
 
 Workhorse now has two websocket connections, albeit with
 differing subprotocols. It decodes incoming frames from the
-browser, re-encodes them to the the channel's subprotocol, and
+browser, re-encodes them to the channel's subprotocol, and
 sends them to the channel. Similarly, it decodes incoming
 frames from the channel, re-encodes them to the browser's
 subprotocol, and sends them to the browser.