From 42ef4b77456c537029ae87019da2cae5c8c78a64 Mon Sep 17 00:00:00 2001
From: Ashraf Khamis <akhamis@gitlab.com>
Date: Tue, 13 Feb 2024 17:45:29 +0000
Subject: [PATCH] Add HAR to spelling exceptions

---
 doc/.vale/gitlab/Uppercase.yml                  |  1 +
 doc/.vale/gitlab/spelling-exceptions.txt        |  1 +
 .../settings/jira_cloud_app_troubleshooting.md  | 17 +++++++++--------
 3 files changed, 11 insertions(+), 8 deletions(-)

diff --git a/doc/.vale/gitlab/Uppercase.yml b/doc/.vale/gitlab/Uppercase.yml
index 01837726b91c8..0a8f8f8f1672d 100644
--- a/doc/.vale/gitlab/Uppercase.yml
+++ b/doc/.vale/gitlab/Uppercase.yml
@@ -104,6 +104,7 @@ exceptions:
   - GPU
   - GUI
   - HAML
+  - HAR
   - HDD
   - HEAD
   - HIPAA
diff --git a/doc/.vale/gitlab/spelling-exceptions.txt b/doc/.vale/gitlab/spelling-exceptions.txt
index 03b4ecafd7812..b2e98a7308c6a 100644
--- a/doc/.vale/gitlab/spelling-exceptions.txt
+++ b/doc/.vale/gitlab/spelling-exceptions.txt
@@ -426,6 +426,7 @@ Gzip
 Hackathon
 Haml
 HAProxy
+HAR
 hardcode
 hardcoded
 hardcodes
diff --git a/doc/administration/settings/jira_cloud_app_troubleshooting.md b/doc/administration/settings/jira_cloud_app_troubleshooting.md
index 829cf77d7ee93..1823f8a8d6f6c 100644
--- a/doc/administration/settings/jira_cloud_app_troubleshooting.md
+++ b/doc/administration/settings/jira_cloud_app_troubleshooting.md
@@ -121,16 +121,17 @@ You should see a `GET` request to `https://gitlab.com/-/jira_connect/installatio
 This request should return a `200 OK`, but it might return a `422 Unprocessable Entity` if there was a problem.
 You can check the response body for the error.
 
-If you cannot resolve the problem and you are a GitLab customer, contact [GitLab Support](https://about.gitlab.com/support/) for assistance. Provide
-GitLab Support with:
+If you cannot resolve the issue and you're a GitLab customer, contact [GitLab Support](https://about.gitlab.com/support/) for assistance.
+Provide GitLab Support with:
 
-1. Your GitLab self-managed instance URL.
-1. Your GitLab.com username.
-1. If possible, the `X-Request-Id` response header for the failed `GET` request to `https://gitlab.com/-/jira_connect/installations`.
-1. Optional. [A HAR file that captured the problem](https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting) that you have
-   processed with the [harcleaner](https://gitlab.com/gitlab-com/support/toolbox/harcleaner) utility.
+- Your self-managed instance URL.
+- Your GitLab.com username.
+- Optional. The `X-Request-Id` response header for the failed `GET`
+  request to `https://gitlab.com/-/jira_connect/installations`.
+- Optional. [A HAR file](https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting)
+  you've processed with [`harcleaner`](https://gitlab.com/gitlab-com/support/toolbox/harcleaner) that captures the issue.
 
-The GitLab Support team can then look up why this is failing in the GitLab.com server logs.
+GitLab Support can then investigate the issue in the GitLab.com server logs.
 
 #### GitLab Support
 
-- 
GitLab