(DOCS-15142): Add inaccurate count warning for fcbis (#1189)

* (DOCS-15142): Add inaccurate count warning for fcbis

* update count method page

* refactor count method page

* formatting

* add ref and link

* update count method page

* tweaks

Author: jeff-allen-mongo

source/core/replica-set-sync.txt

@@ -41,8 +41,7 @@ based*.
 Logical Initial Sync Process
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-When you perform a 
-:ref:`logical initial sync <replica-set-initial-sync-logical>`, MongoDB:
+When you perform a logical initial sync, MongoDB:
 
 #. Clones all databases except the :ref:`local
    <replica-set-local-database>` database. To clone, the
@@ -72,15 +71,25 @@ To perform an initial sync, see
 File Copy Based Initial Sync
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-:ref:`File copy based initial sync 
-<replica-set-initial-sync-file-copy-based>` runs the initial sync
-process by copying and moving files on the file system. 
+File copy based initial sync runs the initial sync process by copying
+and moving files on the file system. 
 
 File copy based initial sync can be faster than 
 :ref:`logical initial sync <replica-set-initial-sync-logical>`.
 
 It is only available on Enterprise Server.
 
+.. important:: File copy based initial sync may cause inaccurate counts
+
+   After file copy based initial sync completes, if you run the
+   :method:`~db.collection.count()` method without a query predicate, the
+   count of documents returned may be inaccurate.
+
+   A ``count`` method without a query predicate looks like this:
+   ``db.<collection>.count()``.
+
+   To learn more, see :ref:`count-method-behavior-query-predicate`.
+
 Limitations
 ```````````
 

source/reference/command/count.txt

@@ -146,25 +146,6 @@ Command Fields
 - :method:`db.collection.estimatedDocumentCount()`
 - :method:`db.collection.count()`
 
-.. important::
-
-  - Avoid using the :dbcommand:`count` and its wrapper methods
-    without a query predicate (note:
-    :method:`db.collection.estimatedDocumentCount()` does not take
-    a query predicate) since without the query predicate, these
-    operations return results based on the collection's metadata,
-    which may result in an approximate count. In particular,
-
-    - On a sharded cluster, the resulting count will not correctly
-      filter out :term:`orphaned documents <orphaned document>`.
-
-    - :ref:`After an unclean shutdown <count-accuracy-shutdown>`,
-      the count may be incorrect.
-
-  - For counts based on collection metadata, see also 
-    :ref:`collStats pipeline stage with the count <collstat-count>`
-    option.
-
 Stable API Support
 ------------------
 
@@ -176,6 +157,27 @@ MongoDB 6.0 or greater.
 Behavior
 --------
 
+.. _count-command-behavior-query-predicate:
+
+Inaccurate Counts Without Query Predicate
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you call :dbcommand:`count` without a query predicate, you may
+receive inaccurate document counts. Without a query predicate,
+:dbcommand:`count` commands return results based on the collection's
+metadata, which may result in an approximate count. In particular,
+
+- On a sharded cluster, the resulting count will not correctly
+  filter out :term:`orphaned documents <orphaned document>`.
+
+- After an unclean shutdown or :ref:`file copy based initial sync
+  <replica-set-initial-sync-file-copy-based>`, the count may be
+  incorrect.
+
+For counts based on collection metadata, see also
+:ref:`collStats pipeline stage with the count <collstat-count>`
+option.
+
 Count and Transactions
 ~~~~~~~~~~~~~~~~~~~~~~
 

source/reference/method/cursor.count.txt

@@ -33,25 +33,6 @@ Definition
    matching documents. The operation does not perform the query but
    instead counts the results that would be returned by the query.
 
-   .. important::
-
-      - Avoid using :method:`~cursor.count()` if the
-        :method:`~db.collection.find()` operation is run without a
-        query predicate since without the query predicate, these
-        :method:`~cursor.count()` returns results based on the
-        collection's metadata, which may result in an approximate
-        count. In particular,
-        
-        - On a sharded cluster, the resulting count will not correctly
-          filter out :term:`orphaned documents <orphaned document>`.
-
-        - After an unclean shutdown, the count may be
-          incorrect.
-
-      - For counts based on collection metadata, see also
-        :ref:`collStats pipeline stage with the count <collstat-count>`
-        option.
-
 
    The :method:`~cursor.count()` method has the following
    prototype form:
@@ -105,6 +86,29 @@ Definition
 Behavior
 --------
 
+.. _count-cursor-behavior-query-predicate:
+
+Inaccurate Counts Without Query Predicate
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you call :method:`~cursor.count()` on a
+:method:`~db.collection.find()` operation which does not specify a query
+predicate, the :method:`~cursor.count()` method can return inaccurate
+document counts. These :method:`~cursor.count()` methods return results
+based on the collection's metadata, which may result in an approximate
+count. In particular,
+
+- On a sharded cluster, the resulting count will not correctly
+  filter out :term:`orphaned documents <orphaned document>`.
+
+- After an unclean shutdown or :ref:`file copy based initial sync
+  <replica-set-initial-sync-file-copy-based>`, the count may be
+  incorrect.
+
+For counts based on collection metadata, see also
+:ref:`collStats pipeline stage with the count <collstat-count>`
+option.
+
 Count and Transactions
 ~~~~~~~~~~~~~~~~~~~~~~
 

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

@@ -33,25 +33,6 @@ Definition
    :method:`~db.collection.find()` operation but instead counts and
    returns the number of results that match a query.
 
-   .. important::
-
-      - Avoid using the :method:`db.collection.count()` method without
-        a query predicate since without the query predicate, the method
-        returns results based on the collection's metadata, which may
-        result in an approximate count. In particular,
-
-        - On a sharded cluster, the resulting count will not correctly
-          filter out :term:`orphaned documents <orphaned document>`.
-
-        - :ref:`After an unclean shutdown
-          <collection-count-accuracy-shutdown>`, the count may be
-          incorrect.
-
-      - For counts based on collection metadata, see also
-        :ref:`collStats pipeline stage with the count <collstat-count>`
-        option.
-
-
    .. list-table::
       :header-rows: 1
       :widths: 20 20 80
@@ -162,6 +143,28 @@ Definition
 Behavior
 --------
 
+.. _count-method-behavior-query-predicate:
+
+Inaccurate Counts Without Query Predicate
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you call :method:`~db.collection.count()` without a query
+predicate, you may receive inaccurate document counts. Without a query
+predicate, :method:`~db.collection.count()` methods return results based
+on the collection's metadata, which may result in an approximate count.
+In particular,
+
+- On a sharded cluster, the resulting count will not correctly
+  filter out :term:`orphaned documents <orphaned document>`.
+
+- After an unclean shutdown or :ref:`file copy based initial sync
+  <replica-set-initial-sync-file-copy-based>`, the count may be
+  incorrect.
+
+For counts based on collection metadata, see also
+:ref:`collStats pipeline stage with the count <collstat-count>`
+option.
+
 Count and Transactions
 ~~~~~~~~~~~~~~~~~~~~~~