(DOCS-15080): Deletes allowed on capped collections (#2333)

* (DOCS-15080): deletes allowed on capped collections

* more updates

* remove unused include

* address review feedback

Author: jeff-allen-mongo

source/core/capped-collections.txt

@@ -99,13 +99,6 @@ Updates
 If you plan to update documents in a capped collection, create an index
 so that these update operations do not require a collection scan.
 
-Document Deletion
-~~~~~~~~~~~~~~~~~
-
-You cannot delete documents from a capped collection. To remove all
-documents from a collection, use the :method:`~db.collection.drop()`
-method to drop the collection and recreate the capped collection.
-
 Sharding
 ~~~~~~~~
 

source/core/index-ttl.txt

@@ -174,9 +174,8 @@ Restrictions
 
 - The ``_id`` field does not support TTL indexes.
 
-- You cannot create a TTL index on a :doc:`capped collection
-  </core/capped-collections>` because MongoDB cannot remove documents
-  from a capped collection.
+- You cannot create a TTL index on a :ref:`capped collection
+  <manual-capped-collection>`.
 
 - You cannot create a TTL index on a :doc:`time series collection
   </core/timeseries-collections>`. Similar functionality is provided

source/includes/fact-remove-capped-collection-restriction.rst

@@ -17,9 +17,8 @@ Definition
 
    The :dbcommand:`delete` command removes documents from a collection.
    A single :dbcommand:`delete` command can contain multiple delete
-   specifications. The command cannot operate on :doc:`capped
-   collections </core/capped-collections>`. The remove methods provided
-   by the MongoDB drivers use this command internally.
+   specifications. The delete methods provided by the MongoDB drivers
+   use this command internally.
 
    .. versionchanged:: 5.0
 
@@ -500,18 +499,22 @@ The following is an example document returned for a successful
    { ok: 1, n: 1 }
 
 The following is an example document returned for a :dbcommand:`delete`
-command that encountered an error:
+command that encountered an error because it specified a non-existent
+index in the ``hint`` field:
 
 .. code-block:: javascript
 
    {
-      "ok" : 1,
-      "n" : 0,
-      "writeErrors" : [
-         {
-            "index" : 0,
-            "code" : 10101,
-            "errmsg" : "can't remove from a capped collection: test.cappedLog"
-         }
-      ]
+     n: 0,
+     writeErrors: [
+       {
+         index: 0,
+         code: 2,
+         errmsg: 'error processing query: ns=test.products: hat $eq "bowler"\n' +
+           'Sort: {}\n' +
+           'Proj: {}\n' +
+           ' planner returned error :: caused by :: hint provided does not correspond to an existing index'
+       }
+     ],
+     ok: 1
    }

source/reference/command/delete.txt

@@ -109,15 +109,6 @@ Definition
 Behavior
 --------
 
-.. _deleteMany-capped-collection:
-
-Capped Collections
-~~~~~~~~~~~~~~~~~~
-
-:method:`db.collection.deleteMany()` throws a ``WriteError`` exception
-if used on a :term:`capped collection`. To remove all documents from a
-capped collection, use :method:`db.collection.drop()`.
-
 .. _deleteMany-timeseries-collection:
 
 Time Series Collections

source/reference/method/db.collection.deleteMany.txt

@@ -122,14 +122,6 @@ Deletion Order
 the filter. Use a field that is part of a :term:`unique index` such as ``_id`` 
 for precise deletions.
 
-.. _deleteOne-capped-collection:
-
-Capped Collections
-~~~~~~~~~~~~~~~~~~
-
-:method:`db.collection.deleteOne()` returns a ``WriteError`` exception
-if used on a :term:`capped collection`.
-
 .. _deleteOne-timeseries-collection:
 
 Time Series Collections

source/reference/method/db.collection.deleteOne.txt

@@ -146,11 +146,6 @@ document sorted by a specified order, use the :ref:`findAndModify()
 When removing multiple documents, the remove operation may interleave
 with other read and/or write operations to the collection.
 
-Capped Collections
-~~~~~~~~~~~~~~~~~~
-
-.. include:: /includes/fact-remove-capped-collection-restriction.rst
-
 Time Series Collections
 ~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -360,4 +355,3 @@ concern error, the results include :data:`WriteResult.writeError` field:
 .. seealso::
 
    :method:`WriteResult.hasWriteError()`
-

source/reference/method/db.collection.remove.txt

@@ -591,6 +591,27 @@ Starting in MongoDB 5.0:
 - DDL operations auditing on :term:`secondaries <secondary>` has
   changes. See :ref:`auditing-audit-events-and-filter`.
 
+.. _5.0-rel-notes-capped-collections:
+
+Capped Collections
+------------------
+
+Capped Collection Deletes Are Replicated to Secondaries
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, the :ref:`implicit delete operations
+<capped_collections_remove_documents>` for :ref:`replica set
+<replication>` :term:`capped collections <capped collection>` are
+processed by the primary and replicated to the :ref:`secondary members
+<replica-set-secondary-members-ref>`.
+
+Explicit Deletes Allowed on Capped Collections
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0.7, you can delete documents from :ref:`capped
+collections <manual-capped-collection>` using :ref:`delete methods
+<delete-additional-methods>`.
+
 .. _5.0-rel-notes-change-streams:
 
 Change Streams
@@ -989,16 +1010,6 @@ with this naming change.
 General Improvements
 --------------------
 
-Capped Collection Deletes Are Replicated to Secondaries
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Starting in MongoDB 5.0, the 
-:ref:`implicit delete operations <capped_collections_remove_documents>`
-for :doc:`replica set </replication>` 
-:term:`capped collections <capped collection>` are processed by 
-the primary and replicated to the 
-:doc:`secondary members </core/replica-set-secondary/>`.
-
 Execution Plan Statistics for Query with ``$lookup`` Pipeline Stage
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~