DOCS-16166 v7.0 (#4707)

Author: jmd-mongo

source/core/sharded-cluster-requirements.txt

@@ -75,8 +75,3 @@ To check a sharded cluster for consistent indexes, use the
    } )
 
 
-Sharding Existing Collection Data Size
---------------------------------------
-
-.. include:: /includes/limits-sharding-existing-collection-data-size.rst
-

source/core/sharding-data-partitioning.txt

@@ -111,10 +111,6 @@ the default chunk size:
 #. Range size affects the
    :limit:`Maximum Number of Documents Per Range to Migrate`.
 
-#. Range size affects the maximum collection size when sharding an
-   :limit:`existing collection<Sharding Existing Collection Data Size>`.
-   Post-sharding, data range size does not constrain collection size.
-
 For many deployments, it makes sense to avoid frequent and potentially
 spurious migrations at the expense of a slightly less evenly
 distributed data set.

source/includes/limits-sharding-existing-collection-data-size.rst

@@ -733,10 +733,6 @@ Sharding Operational Restrictions
 
    .. include:: /includes/extracts/fact-covered-query-sharded-collection-covered-queries.rst
 
-.. limit:: Sharding Existing Collection Data Size
-
-   .. include:: /includes/limits-sharding-existing-collection-data-size.rst
-
 .. limit:: Single Document Modification Operations in Sharded Collections
 
    .. |single-modification-operation-names| replace:: :dbcommand:`update` and :method:`~db.collection.remove()`