From c77560164e8f6c77c9715ee46798dc0fd5c064c7 Mon Sep 17 00:00:00 2001
From: Ashraf Khamis <akhamis@gitlab.com>
Date: Thu, 25 May 2023 14:21:13 +0200
Subject: [PATCH 1/3] Standardize step to test settings

---
 doc/integration/datadog.md                            | 2 +-
 doc/integration/jenkins.md                            | 2 +-
 doc/integration/jira/configure.md                     | 4 ++--
 doc/user/project/integrations/asana.md                | 3 ++-
 doc/user/project/integrations/bamboo.md               | 3 +--
 doc/user/project/integrations/bugzilla.md             | 3 ++-
 doc/user/project/integrations/clickup.md              | 3 ++-
 doc/user/project/integrations/custom_issue_tracker.md | 2 +-
 doc/user/project/integrations/ewm.md                  | 3 ++-
 doc/user/project/integrations/github.md               | 2 +-
 doc/user/project/integrations/hangouts_chat.md        | 2 +-
 doc/user/project/integrations/irker.md                | 5 +++--
 doc/user/project/integrations/pivotal_tracker.md      | 3 ++-
 doc/user/project/integrations/redmine.md              | 3 ++-
 doc/user/project/integrations/slack.md                | 4 ++--
 doc/user/project/integrations/unify_circuit.md        | 3 ++-
 doc/user/project/integrations/webex_teams.md          | 3 ++-
 doc/user/project/integrations/youtrack.md             | 3 ++-
 doc/user/project/integrations/zentao.md               | 2 +-
 doc/user/project/wiki/index.md                        | 2 +-
 20 files changed, 33 insertions(+), 24 deletions(-)

diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md
index edae3d0f9bdce5..04d03034b25fa2 100644
--- a/doc/integration/datadog.md
+++ b/doc/integration/datadog.md
@@ -45,7 +45,7 @@ project, group, or instance level:
 <!-- vale gitlab.Spelling = YES -->
 1. Optional. To define any custom tags for all spans at which the integration is being configured,
    enter one tag per line in **Tags**. Each line must be in the format `key:value`. ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79665) in GitLab 14.8.)
-1. Optional. Select **Test settings** to test your integration.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 When the integration sends data, you can view it in the [CI Visibility](https://app.datadoghq.com/ci)
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md
index 3db02ed1221e8b..d7a6a891159178 100644
--- a/doc/integration/jenkins.md
+++ b/doc/integration/jenkins.md
@@ -134,7 +134,7 @@ than the [webhook integration](#configure-a-webhook).
    project.
 1. If your Jenkins server requires
    authentication, enter the **Username** and **Password**.
-1. To test the connection to Jenkins, select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 ### Configure a webhook
diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md
index 81bfddb01dafca..32e47055ce3425 100644
--- a/doc/integration/jira/configure.md
+++ b/doc/integration/jira/configure.md
@@ -63,7 +63,7 @@ To configure your project settings in GitLab:
    can view all issues from the Jira project you've specified.
 
    - To [create Jira issues for vulnerabilities](../../user/application_security/vulnerabilities/index.md#create-a-jira-issue-for-a-vulnerability), select the **Enable Jira issue creation from vulnerabilities** checkbox.
-1. Optional. Select **Test settings** to verify the connection.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 Your GitLab project can now interact with all Jira projects in your instance, and the project
@@ -96,7 +96,7 @@ To migrate from Jira Server to Jira Cloud in GitLab and maintain your Jira integ
 1. In **Email or username**, enter the email or username registered on your Jira profile.
 1. [Create a Jira Cloud API token](#create-a-jira-cloud-api-token), and copy the token value.
 1. In **API token or password**, paste the API token value.
-1. Optional. Select **Test settings** to verify the connection.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 To update existing Jira issue references in GitLab to use the new Jira site URL, you must [invalidate the Markdown cache](../../administration/invalidate_markdown_cache.md#invalidate-the-cache).
diff --git a/doc/user/project/integrations/asana.md b/doc/user/project/integrations/asana.md
index b1a4d2a2f789f1..d371d0cf68563b 100644
--- a/doc/user/project/integrations/asana.md
+++ b/doc/user/project/integrations/asana.md
@@ -39,6 +39,7 @@ Complete these steps in GitLab:
 1. Paste the token you generated in Asana.
 1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 <!-- ## Troubleshooting -->
diff --git a/doc/user/project/integrations/bamboo.md b/doc/user/project/integrations/bamboo.md
index 23990036f4ee93..63a8e065bbf97d 100644
--- a/doc/user/project/integrations/bamboo.md
+++ b/doc/user/project/integrations/bamboo.md
@@ -47,8 +47,7 @@ integration in GitLab.
 1. If necessary, enter a username and password for a Bamboo user that has
    access to trigger the build plan. Leave these fields blank if you do not require
    authentication.
-1. Optional. To test the configuration and trigger a build in Bamboo,
-   select **Test Settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 ### Identify the Bamboo build plan build key
diff --git a/doc/user/project/integrations/bugzilla.md b/doc/user/project/integrations/bugzilla.md
index f2af4dc6e4deff..2514c421199404 100644
--- a/doc/user/project/integrations/bugzilla.md
+++ b/doc/user/project/integrations/bugzilla.md
@@ -31,7 +31,8 @@ To enable the Bugzilla integration in a project:
      For example, for a project named "My Cool App":
      `https://bugzilla.example.org/enter_bug.cgi#h=dupes%7CMy+Cool+App`.
 
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 After you configure and enable Bugzilla, a link appears on the GitLab
 project pages. This link takes you to the appropriate Bugzilla project.
diff --git a/doc/user/project/integrations/clickup.md b/doc/user/project/integrations/clickup.md
index 255f0c3f56b57a..c2db7c7fb444b3 100644
--- a/doc/user/project/integrations/clickup.md
+++ b/doc/user/project/integrations/clickup.md
@@ -21,7 +21,8 @@ To enable the ClickUp integration in a project:
    - **Issue URL**: The URL to the ClickUp project issue to link to this GitLab project.
      The URL must contain `:id`. GitLab replaces this ID with the issue number.
 
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 After you have configured and enabled ClickUp, you see the ClickUp link on the GitLab project pages,
 which takes you to your ClickUp project.
diff --git a/doc/user/project/integrations/custom_issue_tracker.md b/doc/user/project/integrations/custom_issue_tracker.md
index b529d728e3be0c..660c18186fd2c5 100644
--- a/doc/user/project/integrations/custom_issue_tracker.md
+++ b/doc/user/project/integrations/custom_issue_tracker.md
@@ -36,7 +36,7 @@ To enable a custom issue tracker in a project:
      **This URL is not used and an [issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/327503) to remove it.**
      Enter any URL.
 
-1. Optional. Select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 ## Reference issues in a custom issue tracker
diff --git a/doc/user/project/integrations/ewm.md b/doc/user/project/integrations/ewm.md
index 39dd548e7ca310..9a00eed61642a4 100644
--- a/doc/user/project/integrations/ewm.md
+++ b/doc/user/project/integrations/ewm.md
@@ -35,7 +35,8 @@ To enable the EWM integration, in a project:
      Append the following fragment to your project area URL: `#action=com.ibm.team.workitem.newWorkItem`.
      For example, `https://example.com/ccm/web/projects/JKE%20Banking#action=com.ibm.team.workitem.newWorkItem`.
 
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 ## Reference EWM work items in commit messages
 
diff --git a/doc/user/project/integrations/github.md b/doc/user/project/integrations/github.md
index 3e75106a9bc8e5..5b0d55cca29c97 100644
--- a/doc/user/project/integrations/github.md
+++ b/doc/user/project/integrations/github.md
@@ -36,7 +36,7 @@ Complete these steps in GitLab:
 1. In **Token**, paste the token you generated on GitHub.
 1. In **Repository URL**, enter the path to your project on GitHub, such as `https://github.com/username/repository`.
 1. Optional. To disable [static status check names](#static-or-dynamic-status-check-names), clear the **Enable static status check names** checkbox.
-1. Optional. Select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 After configuring the integration, see [Pipelines for external pull requests](../../../ci/ci_cd_for_external_repos/index.md#pipelines-for-external-pull-requests)
diff --git a/doc/user/project/integrations/hangouts_chat.md b/doc/user/project/integrations/hangouts_chat.md
index 1cfe1a026928dd..f5fc03fb9edf65 100644
--- a/doc/user/project/integrations/hangouts_chat.md
+++ b/doc/user/project/integrations/hangouts_chat.md
@@ -61,7 +61,7 @@ To enable the integration in GitLab:
 1. Scroll down to the end of the page where you find a **Webhook** field.
 1. Enter the webhook URL you copied from Google Chat.
 1. Select the events you want to be notified about in your Google Chat space.
-1. Optional. Select **Test settings** to verify the connection.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 To test the integration, make a change based on the events you selected and
diff --git a/doc/user/project/integrations/irker.md b/doc/user/project/integrations/irker.md
index df11ed3e57c758..7a982d3cc3efff 100644
--- a/doc/user/project/integrations/irker.md
+++ b/doc/user/project/integrations/irker.md
@@ -50,8 +50,9 @@ network. For more details, read
    It's prepended to every channel or user provided under **Recipients**, which is not a full URI.
 1. Under **Recipients**, enter the users or channels to receive updates, separated by spaces
    (for example, `#channel1 user1`). For more details, see [Enter irker recipients](#enter-irker-recipients).
-1. Optional. Under **Colorize messages**, select the checkbox. irker will highlight your messages.
-1. Select **Save changes** or optionally select **Test Settings**.
+1. Optional. Select the **Colorize messages** checkbox to highlight messages.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 ## Enter irker recipients
 
diff --git a/doc/user/project/integrations/pivotal_tracker.md b/doc/user/project/integrations/pivotal_tracker.md
index e1d48037ba8c59..c31e9a59702958 100644
--- a/doc/user/project/integrations/pivotal_tracker.md
+++ b/doc/user/project/integrations/pivotal_tracker.md
@@ -44,4 +44,5 @@ Complete these steps in GitLab:
 1. Paste the token you generated in Pivotal Tracker.
 1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
diff --git a/doc/user/project/integrations/redmine.md b/doc/user/project/integrations/redmine.md
index df8a6681e2bcbd..89512dfbfbf708 100644
--- a/doc/user/project/integrations/redmine.md
+++ b/doc/user/project/integrations/redmine.md
@@ -24,7 +24,8 @@ To enable the Redmine integration in a project:
      **This URL is not used and removal is planned in a future release.**
      For more information, see [issue 327503](https://gitlab.com/gitlab-org/gitlab/-/issues/327503).
 
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 After you have configured and enabled Redmine, you see the Redmine link on the GitLab project pages,
 which takes you to your Redmine project.
diff --git a/doc/user/project/integrations/slack.md b/doc/user/project/integrations/slack.md
index 5b769b84663f0c..a3161a30a44e4d 100644
--- a/doc/user/project/integrations/slack.md
+++ b/doc/user/project/integrations/slack.md
@@ -56,8 +56,8 @@ to control GitLab from Slack. Slash commands are configured separately.
 1. Leave the **Labels to be notified** field blank to get all notifications, or
    add labels that the issue or merge request must have to trigger a
    notification.
-1. Select **Test settings** to verify your information, and then select
-   **Save changes**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 Your Slack team now starts receiving GitLab event notifications as configured.
 
diff --git a/doc/user/project/integrations/unify_circuit.md b/doc/user/project/integrations/unify_circuit.md
index d20b19a3aaabe4..76f57a187c6016 100644
--- a/doc/user/project/integrations/unify_circuit.md
+++ b/doc/user/project/integrations/unify_circuit.md
@@ -23,6 +23,7 @@ In GitLab:
 1. Paste the **Webhook URL** that you copied from the Unify Circuit configuration step.
 1. Select the **Notify only broken pipelines** checkbox to notify only on failures.
 1. In the **Branches for which notifications are to be sent** dropdown list, select which types of branches to send notifications for.
-1. Select `Save changes` or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 Your Unify Circuit conversation now starts receiving GitLab event notifications.
diff --git a/doc/user/project/integrations/webex_teams.md b/doc/user/project/integrations/webex_teams.md
index c755c7a5c17783..b974e822d13c82 100644
--- a/doc/user/project/integrations/webex_teams.md
+++ b/doc/user/project/integrations/webex_teams.md
@@ -33,6 +33,7 @@ notifications:
 1. Ensure that the **Active** toggle is enabled.
 1. Select the checkboxes corresponding to the GitLab events you want to receive in Webex Teams.
 1. Paste the **Webhook** URL for the Webex Teams space.
-1. Configure the remaining options and then select **Test settings and save changes**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 The Webex Teams space begins to receive all applicable GitLab events.
diff --git a/doc/user/project/integrations/youtrack.md b/doc/user/project/integrations/youtrack.md
index ee5ca8eca7864e..cf97361a3f08ab 100644
--- a/doc/user/project/integrations/youtrack.md
+++ b/doc/user/project/integrations/youtrack.md
@@ -22,7 +22,8 @@ To enable the YouTrack integration in a project:
    - **Project URL**: The URL to the project in YouTrack.
    - **Issue URL**: The URL to view an issue in the YouTrack project.
      The URL must contain `:id`. GitLab replaces `:id` with the issue number.
-1. Select **Save changes** or optionally select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
+1. Select **Save changes**.
 
 After you configure and enable YouTrack, a link appears on the GitLab
 project pages. This link takes you to the appropriate YouTrack project.
diff --git a/doc/user/project/integrations/zentao.md b/doc/user/project/integrations/zentao.md
index 19f6a3e315ca7a..8652cc88993013 100644
--- a/doc/user/project/integrations/zentao.md
+++ b/doc/user/project/integrations/zentao.md
@@ -52,7 +52,7 @@ Complete these steps in GitLab:
 
    ![ZenTao settings page](img/zentao_product_id.png)
 
-1. To verify the ZenTao connection is working, select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 <!--- end_remove -->
diff --git a/doc/user/project/wiki/index.md b/doc/user/project/wiki/index.md
index eb13814f2ad174..4d88fd8f3a0aeb 100644
--- a/doc/user/project/wiki/index.md
+++ b/doc/user/project/wiki/index.md
@@ -288,7 +288,7 @@ To add a link to an external wiki from a project's left sidebar:
 1. On the left sidebar, select **Settings > Integrations**.
 1. Select **External wiki**.
 1. Add the URL to your external wiki.
-1. Optional. To verify the connection, select **Test settings**.
+1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
 You can now see the **External wiki** option from your project's
-- 
GitLab


From b7081749014ba55128b08da6ea5e6ff3bbaee303 Mon Sep 17 00:00:00 2001
From: Ashraf Khamis <akhamis@gitlab.com>
Date: Thu, 25 May 2023 12:27:44 +0000
Subject: [PATCH 2/3] Apply 1 suggestion(s) to 1 file(s)

---
 doc/user/project/integrations/irker.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/user/project/integrations/irker.md b/doc/user/project/integrations/irker.md
index 7a982d3cc3efff..1e439808e108f0 100644
--- a/doc/user/project/integrations/irker.md
+++ b/doc/user/project/integrations/irker.md
@@ -50,7 +50,7 @@ network. For more details, read
    It's prepended to every channel or user provided under **Recipients**, which is not a full URI.
 1. Under **Recipients**, enter the users or channels to receive updates, separated by spaces
    (for example, `#channel1 user1`). For more details, see [Enter irker recipients](#enter-irker-recipients).
-1. Optional. Select the **Colorize messages** checkbox to highlight messages.
+1. Optional. To highlight messages, select the **Colorize messages** checkbox.
 1. Optional. To test the integration, select **Test settings**.
 1. Select **Save changes**.
 
-- 
GitLab


From 5437ea4aabc6fd5190c83851f253b47562ac8aae Mon Sep 17 00:00:00 2001
From: Ashraf Khamis <akhamis@gitlab.com>
Date: Thu, 25 May 2023 14:35:11 +0200
Subject: [PATCH 3/3] Delete redundant language

---
 doc/integration/datadog.md                            | 2 +-
 doc/integration/jenkins.md                            | 2 +-
 doc/integration/jira/configure.md                     | 4 ++--
 doc/user/project/integrations/asana.md                | 2 +-
 doc/user/project/integrations/bamboo.md               | 2 +-
 doc/user/project/integrations/bugzilla.md             | 2 +-
 doc/user/project/integrations/clickup.md              | 2 +-
 doc/user/project/integrations/custom_issue_tracker.md | 2 +-
 doc/user/project/integrations/ewm.md                  | 2 +-
 doc/user/project/integrations/github.md               | 2 +-
 doc/user/project/integrations/hangouts_chat.md        | 2 +-
 doc/user/project/integrations/irker.md                | 2 +-
 doc/user/project/integrations/pivotal_tracker.md      | 2 +-
 doc/user/project/integrations/pumble.md               | 2 +-
 doc/user/project/integrations/redmine.md              | 2 +-
 doc/user/project/integrations/slack.md                | 2 +-
 doc/user/project/integrations/unify_circuit.md        | 2 +-
 doc/user/project/integrations/webex_teams.md          | 2 +-
 doc/user/project/integrations/youtrack.md             | 2 +-
 doc/user/project/integrations/zentao.md               | 2 +-
 doc/user/project/wiki/index.md                        | 2 +-
 21 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md
index 04d03034b25fa2..cc4e350d2bbe75 100644
--- a/doc/integration/datadog.md
+++ b/doc/integration/datadog.md
@@ -45,7 +45,7 @@ project, group, or instance level:
 <!-- vale gitlab.Spelling = YES -->
 1. Optional. To define any custom tags for all spans at which the integration is being configured,
    enter one tag per line in **Tags**. Each line must be in the format `key:value`. ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79665) in GitLab 14.8.)
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 When the integration sends data, you can view it in the [CI Visibility](https://app.datadoghq.com/ci)
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md
index d7a6a891159178..89ba8702a831ae 100644
--- a/doc/integration/jenkins.md
+++ b/doc/integration/jenkins.md
@@ -134,7 +134,7 @@ than the [webhook integration](#configure-a-webhook).
    project.
 1. If your Jenkins server requires
    authentication, enter the **Username** and **Password**.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 ### Configure a webhook
diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md
index 32e47055ce3425..22c127860607a9 100644
--- a/doc/integration/jira/configure.md
+++ b/doc/integration/jira/configure.md
@@ -63,7 +63,7 @@ To configure your project settings in GitLab:
    can view all issues from the Jira project you've specified.
 
    - To [create Jira issues for vulnerabilities](../../user/application_security/vulnerabilities/index.md#create-a-jira-issue-for-a-vulnerability), select the **Enable Jira issue creation from vulnerabilities** checkbox.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 Your GitLab project can now interact with all Jira projects in your instance, and the project
@@ -96,7 +96,7 @@ To migrate from Jira Server to Jira Cloud in GitLab and maintain your Jira integ
 1. In **Email or username**, enter the email or username registered on your Jira profile.
 1. [Create a Jira Cloud API token](#create-a-jira-cloud-api-token), and copy the token value.
 1. In **API token or password**, paste the API token value.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 To update existing Jira issue references in GitLab to use the new Jira site URL, you must [invalidate the Markdown cache](../../administration/invalidate_markdown_cache.md#invalidate-the-cache).
diff --git a/doc/user/project/integrations/asana.md b/doc/user/project/integrations/asana.md
index d371d0cf68563b..352f6cdc2bbb52 100644
--- a/doc/user/project/integrations/asana.md
+++ b/doc/user/project/integrations/asana.md
@@ -39,7 +39,7 @@ Complete these steps in GitLab:
 1. Paste the token you generated in Asana.
 1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 <!-- ## Troubleshooting -->
diff --git a/doc/user/project/integrations/bamboo.md b/doc/user/project/integrations/bamboo.md
index 63a8e065bbf97d..05bdd039f12fae 100644
--- a/doc/user/project/integrations/bamboo.md
+++ b/doc/user/project/integrations/bamboo.md
@@ -47,7 +47,7 @@ integration in GitLab.
 1. If necessary, enter a username and password for a Bamboo user that has
    access to trigger the build plan. Leave these fields blank if you do not require
    authentication.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 ### Identify the Bamboo build plan build key
diff --git a/doc/user/project/integrations/bugzilla.md b/doc/user/project/integrations/bugzilla.md
index 2514c421199404..cb6abaa4c7bdd6 100644
--- a/doc/user/project/integrations/bugzilla.md
+++ b/doc/user/project/integrations/bugzilla.md
@@ -31,7 +31,7 @@ To enable the Bugzilla integration in a project:
      For example, for a project named "My Cool App":
      `https://bugzilla.example.org/enter_bug.cgi#h=dupes%7CMy+Cool+App`.
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 After you configure and enable Bugzilla, a link appears on the GitLab
diff --git a/doc/user/project/integrations/clickup.md b/doc/user/project/integrations/clickup.md
index c2db7c7fb444b3..4353749dd33130 100644
--- a/doc/user/project/integrations/clickup.md
+++ b/doc/user/project/integrations/clickup.md
@@ -21,7 +21,7 @@ To enable the ClickUp integration in a project:
    - **Issue URL**: The URL to the ClickUp project issue to link to this GitLab project.
      The URL must contain `:id`. GitLab replaces this ID with the issue number.
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 After you have configured and enabled ClickUp, you see the ClickUp link on the GitLab project pages,
diff --git a/doc/user/project/integrations/custom_issue_tracker.md b/doc/user/project/integrations/custom_issue_tracker.md
index 660c18186fd2c5..b529d728e3be0c 100644
--- a/doc/user/project/integrations/custom_issue_tracker.md
+++ b/doc/user/project/integrations/custom_issue_tracker.md
@@ -36,7 +36,7 @@ To enable a custom issue tracker in a project:
      **This URL is not used and an [issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/327503) to remove it.**
      Enter any URL.
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 ## Reference issues in a custom issue tracker
diff --git a/doc/user/project/integrations/ewm.md b/doc/user/project/integrations/ewm.md
index 9a00eed61642a4..7f87e9fc81f2d7 100644
--- a/doc/user/project/integrations/ewm.md
+++ b/doc/user/project/integrations/ewm.md
@@ -35,7 +35,7 @@ To enable the EWM integration, in a project:
      Append the following fragment to your project area URL: `#action=com.ibm.team.workitem.newWorkItem`.
      For example, `https://example.com/ccm/web/projects/JKE%20Banking#action=com.ibm.team.workitem.newWorkItem`.
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 ## Reference EWM work items in commit messages
diff --git a/doc/user/project/integrations/github.md b/doc/user/project/integrations/github.md
index 5b0d55cca29c97..3e75106a9bc8e5 100644
--- a/doc/user/project/integrations/github.md
+++ b/doc/user/project/integrations/github.md
@@ -36,7 +36,7 @@ Complete these steps in GitLab:
 1. In **Token**, paste the token you generated on GitHub.
 1. In **Repository URL**, enter the path to your project on GitHub, such as `https://github.com/username/repository`.
 1. Optional. To disable [static status check names](#static-or-dynamic-status-check-names), clear the **Enable static status check names** checkbox.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 After configuring the integration, see [Pipelines for external pull requests](../../../ci/ci_cd_for_external_repos/index.md#pipelines-for-external-pull-requests)
diff --git a/doc/user/project/integrations/hangouts_chat.md b/doc/user/project/integrations/hangouts_chat.md
index f5fc03fb9edf65..4046869072da97 100644
--- a/doc/user/project/integrations/hangouts_chat.md
+++ b/doc/user/project/integrations/hangouts_chat.md
@@ -61,7 +61,7 @@ To enable the integration in GitLab:
 1. Scroll down to the end of the page where you find a **Webhook** field.
 1. Enter the webhook URL you copied from Google Chat.
 1. Select the events you want to be notified about in your Google Chat space.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 To test the integration, make a change based on the events you selected and
diff --git a/doc/user/project/integrations/irker.md b/doc/user/project/integrations/irker.md
index 1e439808e108f0..c77fffaa1ba7a6 100644
--- a/doc/user/project/integrations/irker.md
+++ b/doc/user/project/integrations/irker.md
@@ -51,7 +51,7 @@ network. For more details, read
 1. Under **Recipients**, enter the users or channels to receive updates, separated by spaces
    (for example, `#channel1 user1`). For more details, see [Enter irker recipients](#enter-irker-recipients).
 1. Optional. To highlight messages, select the **Colorize messages** checkbox.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 ## Enter irker recipients
diff --git a/doc/user/project/integrations/pivotal_tracker.md b/doc/user/project/integrations/pivotal_tracker.md
index c31e9a59702958..c2392061b8f7ad 100644
--- a/doc/user/project/integrations/pivotal_tracker.md
+++ b/doc/user/project/integrations/pivotal_tracker.md
@@ -44,5 +44,5 @@ Complete these steps in GitLab:
 1. Paste the token you generated in Pivotal Tracker.
 1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
diff --git a/doc/user/project/integrations/pumble.md b/doc/user/project/integrations/pumble.md
index e05ff9489caaae..5199d1a9935b67 100644
--- a/doc/user/project/integrations/pumble.md
+++ b/doc/user/project/integrations/pumble.md
@@ -33,7 +33,7 @@ notifications:
 1. Select the checkboxes corresponding to the GitLab events you want to receive in Pumble.
 1. Paste the **Webhook** URL for the Pumble channel.
 1. Configure the remaining options.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 The Pumble channel begins to receive all applicable GitLab events.
diff --git a/doc/user/project/integrations/redmine.md b/doc/user/project/integrations/redmine.md
index 89512dfbfbf708..5ef30cf413d211 100644
--- a/doc/user/project/integrations/redmine.md
+++ b/doc/user/project/integrations/redmine.md
@@ -24,7 +24,7 @@ To enable the Redmine integration in a project:
      **This URL is not used and removal is planned in a future release.**
      For more information, see [issue 327503](https://gitlab.com/gitlab-org/gitlab/-/issues/327503).
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 After you have configured and enabled Redmine, you see the Redmine link on the GitLab project pages,
diff --git a/doc/user/project/integrations/slack.md b/doc/user/project/integrations/slack.md
index a3161a30a44e4d..2ce1e15ff63486 100644
--- a/doc/user/project/integrations/slack.md
+++ b/doc/user/project/integrations/slack.md
@@ -56,7 +56,7 @@ to control GitLab from Slack. Slash commands are configured separately.
 1. Leave the **Labels to be notified** field blank to get all notifications, or
    add labels that the issue or merge request must have to trigger a
    notification.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 Your Slack team now starts receiving GitLab event notifications as configured.
diff --git a/doc/user/project/integrations/unify_circuit.md b/doc/user/project/integrations/unify_circuit.md
index 76f57a187c6016..4a40a6250f1abd 100644
--- a/doc/user/project/integrations/unify_circuit.md
+++ b/doc/user/project/integrations/unify_circuit.md
@@ -23,7 +23,7 @@ In GitLab:
 1. Paste the **Webhook URL** that you copied from the Unify Circuit configuration step.
 1. Select the **Notify only broken pipelines** checkbox to notify only on failures.
 1. In the **Branches for which notifications are to be sent** dropdown list, select which types of branches to send notifications for.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 Your Unify Circuit conversation now starts receiving GitLab event notifications.
diff --git a/doc/user/project/integrations/webex_teams.md b/doc/user/project/integrations/webex_teams.md
index b974e822d13c82..2388014db06b35 100644
--- a/doc/user/project/integrations/webex_teams.md
+++ b/doc/user/project/integrations/webex_teams.md
@@ -33,7 +33,7 @@ notifications:
 1. Ensure that the **Active** toggle is enabled.
 1. Select the checkboxes corresponding to the GitLab events you want to receive in Webex Teams.
 1. Paste the **Webhook** URL for the Webex Teams space.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 The Webex Teams space begins to receive all applicable GitLab events.
diff --git a/doc/user/project/integrations/youtrack.md b/doc/user/project/integrations/youtrack.md
index cf97361a3f08ab..b1c7b533c0fc41 100644
--- a/doc/user/project/integrations/youtrack.md
+++ b/doc/user/project/integrations/youtrack.md
@@ -22,7 +22,7 @@ To enable the YouTrack integration in a project:
    - **Project URL**: The URL to the project in YouTrack.
    - **Issue URL**: The URL to view an issue in the YouTrack project.
      The URL must contain `:id`. GitLab replaces `:id` with the issue number.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 After you configure and enable YouTrack, a link appears on the GitLab
diff --git a/doc/user/project/integrations/zentao.md b/doc/user/project/integrations/zentao.md
index 8652cc88993013..b14b9eac9da172 100644
--- a/doc/user/project/integrations/zentao.md
+++ b/doc/user/project/integrations/zentao.md
@@ -52,7 +52,7 @@ Complete these steps in GitLab:
 
    ![ZenTao settings page](img/zentao_product_id.png)
 
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 <!--- end_remove -->
diff --git a/doc/user/project/wiki/index.md b/doc/user/project/wiki/index.md
index 4d88fd8f3a0aeb..a6784e598daedd 100644
--- a/doc/user/project/wiki/index.md
+++ b/doc/user/project/wiki/index.md
@@ -288,7 +288,7 @@ To add a link to an external wiki from a project's left sidebar:
 1. On the left sidebar, select **Settings > Integrations**.
 1. Select **External wiki**.
 1. Add the URL to your external wiki.
-1. Optional. To test the integration, select **Test settings**.
+1. Optional. Select **Test settings**.
 1. Select **Save changes**.
 
 You can now see the **External wiki** option from your project's
-- 
GitLab