DOCS-15797 Adding clarification for same name collection deletes (#2313)

* DOCS-15797 Adding clarification for same name collection deletes

* behavior section

* add note

* header name update

* bullet list

* indent

* remove flushing cache

* internal feedback .5

* internal review 1

* feedback 1

* verbiage

* Review Feedback 2

* remove note

Author: ianf-mongodb

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

@@ -25,18 +25,6 @@ Definition
    collection. The method provides a wrapper around the
    :dbcommand:`drop` command.
 
-   .. note::
-
-      For a sharded cluster, if you use :method:`db.collection.drop()`
-      and then create a new collection with the same name, you must
-      either:
-
-      - Flush the cached routing table on every :binary:`~bin.mongos`
-        using :dbcommand:`flushRouterConfig`.
-      - Use :method:`db.collection.remove()` to remove the existing
-        documents and reuse the collection. Use this approach to avoid
-        flushing the cache.
-
    :method:`db.collection.drop()` has the form:
 
    .. code-block:: javascript
@@ -92,7 +80,37 @@ Behavior
      encrypted fields. ``mongosh`` *always* drops the specified 
      collection and any internal collections related to encrypted
      fields.
-  
+
+
+.. _sharding-drop-collections-same-name:
+
+Reusing Dropped Collection Names on Sharded Clusters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+On a sharded cluster, if you create a collection that has the same name 
+as a previously deleted collection prior to MongoDB 5.0, 
+:binary:`~bin.mongos` may forward operations to the wrong shard.
+To avoid this situation use the version-specific instructions below:
+
+For a sharded cluster running **MongoDB 5.0 or later**, 
+no special action is required. Use the ``drop()`` method
+and then create a new collection with the same name.
+
+For a sharded cluster running **MongoDB 4.4 or earlier**, 
+if you use the ``drop()`` method and then create a new collection with 
+the same name, you must either:
+
+-  Flush the cached routing table on every :binary:`~bin.mongos`
+   using :dbcommand:`flushRouterConfig`.
+
+-  Use :method:`db.collection.remove()` to remove the existing
+   documents and reuse the collection.
+
+Flushing the cached routing tables is the preferred procedure because it
+is faster than removing sharded collections with 
+:method:`db.collection.remove()`. Only use the ``remove()`` approach if 
+you want to avoid flushing the cache.
+
 Resource Locking
 ~~~~~~~~~~~~~~~~