diff --git a/doc/api/repositories.md b/doc/api/repositories.md
index ce9781241ed81a801c2e878ed1fa5eb2a243d429..bf2ead4351973a4691bc8defc8a63811406a0b00 100644
--- a/doc/api/repositories.md
+++ b/doc/api/repositories.md
@@ -342,9 +342,8 @@ tags using these formats:
 - `vX.Y.Z`
 - `X.Y.Z`
 
-Where `X.Y.Z` is a version that follows [semantic
-versioning](https://semver.org/). For example, consider a project with the
-following tags:
+Where `X.Y.Z` is a version that follows [semantic versioning](https://semver.org/). 
+For example, consider a project with the following tags:
 
 - v1.0.0-pre1
 - v1.0.0
diff --git a/doc/development/internal_api/index.md b/doc/development/internal_api/index.md
index 327e750145c292e11db55453f462f3fda3422761..c3703417f394dc3d88df9b6ab4011466044bd4ff 100644
--- a/doc/development/internal_api/index.md
+++ b/doc/development/internal_api/index.md
@@ -148,8 +148,8 @@ curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" \
 ## Authorized Keys Check
 
 This endpoint is called by the GitLab Shell authorized keys
-check. Which is called by OpenSSH for [fast SSH key
-lookup](../../administration/operations/fast_ssh_key_lookup.md).
+check. Which is called by OpenSSH for 
+[fast SSH key lookup](../../administration/operations/fast_ssh_key_lookup.md).
 
 | Attribute | Type   | Required | Description |
 |:----------|:-------|:---------|:------------|
diff --git a/doc/development/lfs.md b/doc/development/lfs.md
index 9b78c8869b1fe7da615d400ddfcab4a1b5de80b9..5900eb68294e2ddb08578673d123e3f0300abc81 100644
--- a/doc/development/lfs.md
+++ b/doc/development/lfs.md
@@ -76,14 +76,13 @@ process, which writes the contents to the standard output.
 1. The archive data is sent back to the client.
 
 In step 7, the `gitaly-lfs-smudge` filter must talk to Workhorse, not to
-Rails, or an invalid LFS blob is saved. To support this, GitLab
-13.5 [changed the default Omnibus configuration to have Gitaly talk to
-the Workhorse](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4592)
+Rails, or an invalid LFS blob is saved. To support this, GitLab 13.5 
+[changed the default Omnibus configuration to have Gitaly talk to the Workhorse](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4592)
 instead of Rails.
 
 One side effect of this change: the correlation ID of the original
 request is not preserved for the internal API requests made by Gitaly
 (or `gitaly-lfs-smudge`), such as the one made in step 8. The
-correlation IDs for those API requests are random values until [this
-Workhorse issue](https://gitlab.com/gitlab-org/gitlab-workhorse/-/issues/309) is
+correlation IDs for those API requests are random values until 
+[this Workhorse issue](https://gitlab.com/gitlab-org/gitlab-workhorse/-/issues/309) is
 resolved.
diff --git a/doc/development/workhorse/index.md b/doc/development/workhorse/index.md
index de3636fa112629092c4b48efcb8cbdec5a65fe8d..962124248efe1df700bc7de804572c266325d0ac 100644
--- a/doc/development/workhorse/index.md
+++ b/doc/development/workhorse/index.md
@@ -10,8 +10,8 @@ GitLab Workhorse is a smart reverse proxy for GitLab. It handles
 "large" HTTP requests such as file downloads, file uploads, Git
 push/pull and Git archive downloads.
 
-Workhorse itself is not a feature, but there are [several features in
-GitLab](gitlab_features.md) that would not work efficiently without Workhorse.
+Workhorse itself is not a feature, but there are 
+[several features in GitLab](gitlab_features.md) that would not work efficiently without Workhorse.
 
 The canonical source for Workhorse is
 [`gitlab-org/gitlab/workhorse`](https://gitlab.com/gitlab-org/gitlab/tree/master/workhorse).
diff --git a/doc/topics/git/lfs/index.md b/doc/topics/git/lfs/index.md
index 3d52d5446b9089d0ae6036c34e123e7c69dd93e8..6fd7f4a520730ba897996dfdf24b0b4ab9fc2a44 100644
--- a/doc/topics/git/lfs/index.md
+++ b/doc/topics/git/lfs/index.md
@@ -115,8 +115,7 @@ See the documentation on [File Locking](../../../user/project/file_lock.md).
 > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46572) in GitLab 13.6.
 > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62539) in GitLab 14.0. Feature flag `include_lfs_blobs_in_archive` removed.
 
-Prior to GitLab 13.5, [project source
-downloads](../../../user/project/repository/index.md) would include Git
+Prior to GitLab 13.5, [project source downloads](../../../user/project/repository/index.md) would include Git
 LFS pointers instead of the actual objects. For example, LFS pointers
 look like the following:
 
diff --git a/doc/user/project/git_attributes.md b/doc/user/project/git_attributes.md
index 11d1db195e11039eb8eb9abfbd8ef1d07208d1ce..90f64b7262ced1a69f50b47f62e5ba0226293cef 100644
--- a/doc/user/project/git_attributes.md
+++ b/doc/user/project/git_attributes.md
@@ -23,5 +23,5 @@ ignored.
 ## Syntax Highlighting
 
 The `.gitattributes` file can be used to define which language to use when
-syntax highlighting files and diffs. See ["Syntax
-Highlighting"](highlighting.md) for more information.
+syntax highlighting files and diffs. See 
+["Syntax Highlighting"](highlighting.md) for more information.
diff --git a/doc/user/project/push_options.md b/doc/user/project/push_options.md
index 6ef8477b6b6f273e871424587ed432257ce01c48..d02609cbdc7d33969cc2901392ee2dfe54fbde91 100644
--- a/doc/user/project/push_options.md
+++ b/doc/user/project/push_options.md
@@ -95,15 +95,15 @@ git push -o merge_request.create -o merge_request.target=my-target-branch -o mer
 ## Useful Git aliases
 
 As shown above, Git push options can cause Git commands to grow very long. If
-you use the same push options frequently, it's useful to create [Git
-aliases](https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases). Git aliases
+you use the same push options frequently, it's useful to create
+[Git aliases](https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases). Git aliases
 are command line shortcuts for Git which can significantly simplify the use of
 long Git commands.
 
 ### Merge when pipeline succeeds alias
 
-To set up a Git alias for the [merge when pipeline succeeds Git push
-option](#push-options-for-merge-requests):
+To set up a Git alias for the 
+[merge when pipeline succeeds Git push option](#push-options-for-merge-requests):
 
 ```shell
 git config --global alias.mwps "push -o merge_request.create -o merge_request.target=master -o merge_request.merge_when_pipeline_succeeds"