diff --git a/db/fixtures/production/998_gitlab_instance_administration_project.rb b/db/fixtures/production/998_gitlab_instance_administration_project.rb
index 7148c01121a1970ffb02e718dd353992c466197d..8be707ffb08653b3c7dda0abfdd88c7669102b03 100644
--- a/db/fixtures/production/998_gitlab_instance_administration_project.rb
+++ b/db/fixtures/production/998_gitlab_instance_administration_project.rb
@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
-::Gitlab::DatabaseImporters::SelfMonitoring::Project::CreateService.new.execute
+response = ::Gitlab::DatabaseImporters::SelfMonitoring::Project::CreateService.new.execute
 
 if response[:status] == :success
   puts "Successfully created self monitoring project."
diff --git a/doc/ci/unit_test_reports.md b/doc/ci/unit_test_reports.md
index 0a62eab38deaa5759e097e546d572e1e45917659..9d803c300f2140e76867f98b9bec50f32790618a 100644
--- a/doc/ci/unit_test_reports.md
+++ b/doc/ci/unit_test_reports.md
@@ -28,8 +28,6 @@ output without searching through job logs, the full
 [Unit test reports](#viewing-unit-test-reports-on-gitlab) are available 
 in the pipeline detail view.
 
-## Use cases
-
 Consider the following workflow:
 
 1. Your `master` branch is rock solid, your project is using GitLab CI/CD and
@@ -44,9 +42,9 @@ Consider the following workflow:
 
 ## How it works
 
-First, GitLab Runner uploads all JUnit report format XML files as artifacts to GitLab. Then,
-when you visit a merge request, GitLab starts comparing the head and base branch's
-JUnit report format XML files, where:
+First, GitLab Runner uploads all [JUnit report format XML files](https://www.ibm.com/support/knowledgecenter/en/SSQ2R2_14.1.0/com.ibm.rsar.analysis.codereview.cobol.doc/topics/cac_useresults_junit.html)
+as [artifacts](pipelines/job_artifacts.md#artifactsreportsjunit) to GitLab. Then, when you visit a merge request, GitLab starts
+comparing the head and base branch's JUnit report format XML files, where:
 
 - The base branch is the target branch (usually `master`).
 - The head branch is the source branch (the latest pipeline in each merge request).
diff --git a/doc/development/cicd/templates.md b/doc/development/cicd/templates.md
index 44bbd4c83f042cbe8c6041ddcf6d7edb6cc210d9..7d0cd1ec08a7bb9fa2a7f7ef6b7ac147b1a94455 100644
--- a/doc/development/cicd/templates.md
+++ b/doc/development/cicd/templates.md
@@ -13,15 +13,15 @@ This document explains how to develop [GitLab CI/CD templates](../../ci/examples
 
 All template files reside in the `lib/gitlab/ci/templates` directory, and are categorized by the following sub-directories:
 
-| Sub-directory | Content                                                      | [Selectable in UI](#make-sure-the-new-template-can-be-selected-in-ui) |
-|---------------|--------------------------------------------------------------|-----------------------------------------------------------------------|
-| `/AWS/*`      | Cloud Deployment (AWS) related jobs                          | No                                                                    |
-| `/Jobs/*`     | Auto DevOps related jobs                                     | Yes                                                                   |
-| `/Pages/*`    | Static site generators for GitLab Pages (for example Jekyll) | Yes                                                                   |
-| `/Security/*` | Security related jobs                                        | Yes                                                                   |
-| `/Verify/*`   | Verify/testing related jobs                                  | Yes                                                                   |
-| `/Worklows/*` | Common uses of the `workflow:` keyword                       | No                                                                    |
-| `/*` (root)   | General templates                                            | Yes                                                                   |
+| Sub-directory  | Content                                                      | [Selectable in UI](#make-sure-the-new-template-can-be-selected-in-ui) |
+|----------------|--------------------------------------------------------------|-----------------------------------------------------------------------|
+| `/AWS/*`       | Cloud Deployment (AWS) related jobs                          | No                                                                    |
+| `/Jobs/*`      | Auto DevOps related jobs                                     | Yes                                                                   |
+| `/Pages/*`     | Static site generators for GitLab Pages (for example Jekyll) | Yes                                                                   |
+| `/Security/*`  | Security related jobs                                        | Yes                                                                   |
+| `/Verify/*`    | Verify/testing related jobs                                  | Yes                                                                   |
+| `/Workflows/*` | Common uses of the `workflow:` keyword                       | No                                                                    |
+| `/*` (root)    | General templates                                            | Yes                                                                   |
 
 ## Criteria