diff --git a/data/release-notes/enterprise-server/2-22/17.yml b/data/release-notes/enterprise-server/2-22/17.yml
index e9047d7ef9..7f9b37ef4b 100644
--- a/data/release-notes/enterprise-server/2-22/17.yml
+++ b/data/release-notes/enterprise-server/2-22/17.yml
@@ -6,7 +6,7 @@ sections:
   bugs:
     - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
     - Collectd would not resolve the forwarding destination hostname after the initial startup.
-    - The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
+    - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
     - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.
     - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled.
   changes:
diff --git a/data/release-notes/enterprise-server/3-0/11.yml b/data/release-notes/enterprise-server/3-0/11.yml
index 4c30184211..c649896c06 100644
--- a/data/release-notes/enterprise-server/3-0/11.yml
+++ b/data/release-notes/enterprise-server/3-0/11.yml
@@ -9,7 +9,7 @@ sections:
     - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
     - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.
     - Collectd would not resolve the forwarding destination hostname after the initial startup.
-    - The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
+    - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
     - Running `git nw-gc --pristine` would result in an error.
     - Background jobs were being queued to the `spam` queue which were not being processed.
     - The preferred merge method would be reset when retrying after a failed PR merge.
diff --git a/data/release-notes/enterprise-server/3-1/3.yml b/data/release-notes/enterprise-server/3-1/3.yml
index 458c22771a..8f0f5295fd 100644
--- a/data/release-notes/enterprise-server/3-1/3.yml
+++ b/data/release-notes/enterprise-server/3-1/3.yml
@@ -9,7 +9,7 @@ sections:
     - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
     - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.
     - Collectd would not resolve the forwarding destination hostname after the initial startup.
-    - The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
+    - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
     - Background jobs were being queued to the `spam` queue which were not being processed.
     - The preferred merge method would be reset when retrying after a failed PR merge.
     - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.