diff --git a/source/core/capped-collections.txt b/source/core/capped-collections.txt
index 97af39f65a1..79e88ec5ae8 100644
--- a/source/core/capped-collections.txt
+++ b/source/core/capped-collections.txt
@@ -48,6 +48,8 @@ result, queries do not need an index to return documents in insertion
 order. Without this indexing overhead, capped collections can support
 higher insertion throughput.
 
+.. _capped_collections_remove_documents:
+
 Automatic Removal of Oldest Documents
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/source/release-notes/5.0.txt b/source/release-notes/5.0.txt
index bb327ed48c3..aa236014dfc 100644
--- a/source/release-notes/5.0.txt
+++ b/source/release-notes/5.0.txt
@@ -661,6 +661,15 @@ Transactions
 General Improvements
 --------------------
 
+Capped Collection Deletes Process On Secondaries
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, the
+:ref:`implicit delete operations <capped_collections_remove_documents>`
+of :doc:`replica set </replication>` 
+:term:`capped collections <capped collection>` are processed by 
+the :doc:`secondary members </core/replica-set-secondary/>`.
+
 Execution Plan Statistics for Query with ``$lookup`` Pipeline Stage
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~