Add latest changes from gitlab-org/gitlab@master

2 files changed, 13 insertions, 13 deletions

diff --git a/doc/integration/jira/dvcs/troubleshooting.md b/doc/integration/jira/dvcs/troubleshooting.md
index ee697f1bffd..6de54136f3e 100644
--- a/doc/integration/jira/dvcs/troubleshooting.md
+++ b/doc/integration/jira/dvcs/troubleshooting.md
@@ -6,9 +6,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Troubleshooting Jira DVCS connector **(FREE ALL)**
 
-Refer to the items in this section if you're having problems with your Jira DVCS connector.
+When working with the [Jira DVCS connector](index.md), you might encounter the following issues.
 
-## Jira cannot access GitLab server
+## Jira cannot access the GitLab server
 
 If you complete the **Add New Account** form, authorize access, and you receive
 this error, Jira and GitLab cannot connect. No other error messages
@@ -68,7 +68,7 @@ The message `Successfully connected` indicates a successful TLS handshake.
 If there are problems, the Java TLS library generates errors that you can
 look up for more detail.
 
-## Scope error when connecting to Jira using DVCS
+## Scope error when connecting to Jira with DVCS
 
 ```plaintext
 The requested scope is invalid, unknown, or malformed.
@@ -83,7 +83,7 @@ Potential resolutions:
    [GitLab account configuration](index.md#create-a-gitlab-application-for-dvcs). Review
    the **Scopes** field and ensure the `api` checkbox is selected.
 
-## Jira error adding account and no repositories listed
+## Error when adding an account in Jira
 
 After you complete the **Add New Account** form in Jira and authorize access, you might
 encounter these issues:
@@ -100,13 +100,13 @@ To resolve this issue:
 
 [Contact GitLab Support](https://about.gitlab.com/support/) if none of these reasons apply.
 
-## `410 : Gone` error when connecting to Jira
+## `410 Gone` when connecting to Jira
 
-When you connect to Jira and synchronize repositories, you may receive a `410 : Gone` error.
+When you connect to Jira and synchronize repositories, you might get a `410 Gone` error.
 
 This issue occurs when you use the Jira DVCS connector and your integration is configured to use **GitHub Enterprise**.
 
-For more information and possible fixes, see [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/340160).
+For more information, see [issue 340160](https://gitlab.com/gitlab-org/gitlab/-/issues/340160).
 
 ## Synchronization issues
 
@@ -123,7 +123,7 @@ resynchronize the information:
 For more information, see the
 [Atlassian documentation](https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-development-tools/).
 
-## `Sync Failed` error when refreshing repository data
+## `Sync Failed` when refreshing repository data
 
 If you get a `Sync Failed` error in Jira when [refreshing repository data](index.md#refresh-data-imported-to-jira) for specific projects, check your Jira DVCS connector logs. Look for errors that occur when executing requests to API resources in GitLab. For example:
 
@@ -132,8 +132,8 @@ Failed to execute request [https://gitlab.com/api/v4/projects/:id/merge_requests
 {"message":"403 Forbidden"}
 ```
 
-If you find a `{"message":"403 Forbidden"}` error, it is possible that this specific project has some [GitLab features disabled](../../../user/project/settings/project_features_permissions.md#configure-project-features-and-permissions).
-In the example above, the merge requests feature is disabled.
+If you get a `403 Forbidden` error, this project might have some [GitLab features disabled](../../../user/project/settings/project_features_permissions.md#configure-project-features-and-permissions).
+In the previous example, the merge requests feature is disabled.
 
 To resolve the issue, enable the relevant feature:
 
diff --git a/doc/integration/jira/troubleshooting.md b/doc/integration/jira/troubleshooting.md
index 6c8b49b4159..14d8c65bcda 100644
--- a/doc/integration/jira/troubleshooting.md
+++ b/doc/integration/jira/troubleshooting.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Troubleshooting Jira issue integration **(FREE ALL)**
 
-This page contains a list of common issues you might encounter when working with the [Jira issue integration](configure.md).
+When working with the [Jira issue integration](configure.md), you might encounter the following issues.
 
 ## GitLab cannot link to a Jira issue
 
@@ -122,7 +122,7 @@ To resolve this issue, see
 WARNING:
 Commands that change data can cause damage if not run correctly or under the right conditions. Always run commands in a test environment first and have a backup instance ready to restore.
 
-### Change all projects on the instance
+### Change all projects on an instance
 
 To change all Jira projects to use instance-level integration settings:
 
@@ -189,7 +189,7 @@ To change all Jira projects in a group (and its subgroups) to use group-level in
   end
   ```
 
-## Update the Jira issue integration password for all projects
+## Update the integration password for all projects
 
 WARNING:
 Commands that change data can cause damage if not run correctly or under the right conditions. Always run commands in a test environment first and have a backup instance ready to restore.