From 2703128e7a2de991c0260fb54cfee64b69da6b47 Mon Sep 17 00:00:00 2001
From: Russell Dickenson <rdickenson@gitlab.com>
Date: Wed, 2 Oct 2024 09:50:42 +1000
Subject: [PATCH] Correct role required to remove blob

---
 .../project/repository/reducing_the_repo_size_using_git.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/user/project/repository/reducing_the_repo_size_using_git.md b/doc/user/project/repository/reducing_the_repo_size_using_git.md
index 6a83fff28594..729ab72e9e90 100644
--- a/doc/user/project/repository/reducing_the_repo_size_using_git.md
+++ b/doc/user/project/repository/reducing_the_repo_size_using_git.md
@@ -53,8 +53,9 @@ These refs are not automatically downloaded and hidden refs are not advertised,
 
 WARNING:
 This process is not suitable for removing sensitive data like password or keys from your repository.
-Information about commits, including file content, is cached in the database, and remain
-visible even after they have been removed from the repository.
+Information about commits, including file content, is cached in the database, and remain visible
+even after they have been removed from the repository. To remove sensitive data, use the method
+described in [Remove blobs](#remove-blobs).
 
 To purge files from a GitLab repository:
 
@@ -256,7 +257,7 @@ Alternatively, to replace strings with `***REMOVED***`, see
 
 Prerequisites:
 
-- You must have the Owner role for the instance.
+- You must have the Owner role for the project.
 - You must have [a list of object IDs](#get-a-list-of-object-ids) to remove.
 
 To remove blobs from your repository:
-- 
GitLab