diff --git a/data/removals/15_0/15-0-removal-testcoveragesetting.yml b/data/removals/15_0/15-0-removal-testcoveragesetting.yml
index b929eaa96dd9438a5fe55f96c59044644884fb51..bd72a28f0db4823e9059d92c6e2e70e5b0a6fc9a 100644
--- a/data/removals/15_0/15-0-removal-testcoveragesetting.yml
+++ b/data/removals/15_0/15-0-removal-testcoveragesetting.yml
@@ -4,10 +4,10 @@
   removal_milestone: "15.0"  # The milestone when this feature is being removed.
   removal_date: "2022-05-22"  # This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed.
   breaking_change: true  # Change to true if this removal is a breaking change.
-  reporter: exampleuser  # GitLab username of the person reporting the removal
+  reporter: jreporter  # GitLab username of the person reporting the removal
   body: |  # Do not modify this line, instead modify the lines below.
-     To specify a test coverage pattern, beginning in GitLab 15.0 the
-     [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-deprecated)
+     To specify a test coverage pattern, in GitLab 15.0 the
+     [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-removed)
      has been removed.
 
      To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by providing a regular expression with the
diff --git a/doc/ci/pipelines/settings.md b/doc/ci/pipelines/settings.md
index f4a658275c0437ddaa7eeeaf306950536757b72b..a1180064c2101867112de62cff8d46ff1af94288 100644
--- a/doc/ci/pipelines/settings.md
+++ b/doc/ci/pipelines/settings.md
@@ -222,37 +222,17 @@ averaged.
 To add test coverage results to a merge request using the project's `.gitlab-ci.yml` file, provide a regular expression
 using the [`coverage`](../yaml/index.md#coverage) keyword.
 
-Setting the regular expression this way takes precedence over project settings.
+<!-- start_remove The following content will be removed on remove_date: '2023-08-22' -->
 
-### Add test coverage results using project settings (REMOVED)
+### Add test coverage results using project settings (removed)
 
 > [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) in GitLab 14.8. Replaced by [`coverage` keyword](../yaml/index.md#coverage).
 > [Removed](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) in GitLab 15.0.
 
-WARNING:
 This feature is in its end-of-life process. It was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/17633)
 in GitLab 14.8. The feature is [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/17633) in GitLab 15.0.
 
-You can add test coverage results to merge requests using the Project's CI/CD settings:
-
-- Set using the GitLab UI:
-
-  1. On the top bar, select **Menu > Projects** and find your project.
-  1. On the left sidebar, select **Settings > CI/CD**.
-  1. Expand **General pipelines**.
-  1. In the **Test coverage parsing** field, enter a regular expression. Leave blank to disable this feature.
-
-- Set when [editing a project](../../api/projects.md#edit-project) or [creating a project](../../api/projects.md#create-project)
-  using the GitLab API with the `build_coverage_regex` attribute:
-
-  ```shell
-  curl --request PUT --header "PRIVATE-TOKEN: <your-token>" \
-     --url 'https://gitlab.com/api/v4/projects/<your-project-ID>' \
-     --data "build_coverage_regex=<your-regular-expression>"
-  ```
-
-You can use <https://rubular.com> to test your regular expression. The regular expression returns the **last**
-match found in the output.
+<!-- end_remove -->
 
 ### Test coverage examples
 
diff --git a/doc/update/removals.md b/doc/update/removals.md
index 88901d9af241cc215157c1a4a4872c92ac90cf25..266b6e9fa7b3e90d3e7857cb779b3fe8b2c46ea1 100644
--- a/doc/update/removals.md
+++ b/doc/update/removals.md
@@ -137,8 +137,8 @@ as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#brea
 Before updating GitLab, review the details carefully to determine if you need to make any
 changes to your code, settings, or workflow.
 
-To specify a test coverage pattern, beginning in GitLab 15.0 the
-[project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-deprecated)
+To specify a test coverage pattern, in GitLab 15.0 the
+[project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-removed)
 has been removed.
 
 To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by providing a regular expression with the