Revisions for tone and style

Revise the section to deal with Markdownlint issues, and handle
tone and style polishing.

doc/user/project/repository/repository_mirroring.md

@@ -595,6 +595,24 @@ As the error indicates, the connection is getting blocked between GitLab and the
 
 For example, we've seen this error when a Firewall was performing a `Deep SSH Inspection` on outgoing packets.
 
-### 2:fetch remote: "fatal: could not read Username for 'https://bitbucket.org': terminal prompts disabled\n": exit status 128.
+### Could not read username: terminal prompts disabled
 
-If you receive an `"2:fetch remote: "fatal: could not read Username for 'https://bitbucket.org': terminal prompts disabled\n": exit status 128."` after creating a new project using [GitLab CI/CD for external repositories](../../../ci/ci_cd_for_external_repos/), please check if the repository owner is specified in the URL of your mirrored repository: **Project** > **Settings** > **Repository** > **Mirroring repositories**. If it is not specified, please delete and add the URL again in the following format: `https://**<repo_owner>**@bitbucket.org/<accountname>/<reponame>.git`. The repository owner is needed in order for BitBucket to connect to the repository for mirroring.
+If you receive this error after creating a new project using
+[GitLab CI/CD for external repositories](../../../ci/ci_cd_for_external_repos/):
+
+```plaintext
+"2:fetch remote: "fatal: could not read Username for 'https://bitbucket.org': terminal prompts disabled\n": exit status 128."
+```
+
+Check if the repository owner is specified in the URL of your mirrored repository:
+
+1. Go to your project.
+1. In the left sidebar, select **Settings > Repository**.
+1. Select **Mirroring repositories**.
+1. If no repository owner is specified, delete and add the URL again in this format:
+
+   ```plaintext
+   https://**<repo_owner>**@bitbucket.org/<accountname>/<reponame>.git
+   ```
+
+The repository owner is needed for Bitbucket to connect to the repository for mirroring.