change batchsize wording

Author: shuangela

source/includes/extracts-watch-option.yaml

@@ -1,9 +1,11 @@
 ref: watch-option-batchSize
 content: |
-  Specifies the batch size for the cursor, which will apply to both the initial
-  ``aggregate`` command and any subsequent ``getMore`` commands. This determines
-  the maximum number of change events to return in each response from the
-  server.
+
+  Specifies the batch size for the cursor, which will apply to both the
+  initial ``aggregate`` command and any subsequent ``getMore`` commands.
+  If batchSize is set, ``aggregate`` and any subsequent ``getMore`` commands returns the smaller of 16 megabytes of data 
+  or batchSize documents. Operations of type ``find()``, ``aggregate()``, ``listIndexes``, and ``listCollections`` return a maximum of ``16`` megabytes per batch. 
+  batchSize can enforce a smaller limit than ``16`` megabytes, but not a larger one. 
 
   Irrespective of the ``batchSize`` option, the initial ``aggregate`` command
   response for a change stream generally does not include any documents

source/read/retrieve.txt

@@ -180,7 +180,9 @@ you can set in the array:
      - Description
 
    * - ``batchSize`` 
-     - | The number of documents to return per batch. The default value is ``101``.
+     - | The limit for each batch returned in a query result. The ``find()`` method has an initial batch size of 101 documents by default and returns a maximum of 16
+         megabytes per batch. Subsequent ``getMore`` operations issued against the resulting cursor have no default batch size, 
+         so they are limited only by the ``16`` megabyte message size. batchSize can enforce a smaller limit than ``16`` megabytes, but not a larger one. 
        | **Type**: ``integer``
 
    * - ``collation`` 

source/reference/method/MongoDBCollection-find.txt

@@ -52,8 +52,8 @@ Parameters
 
      * - batchSize
        - integer
-       - The number of documents to return in the first batch. Defaults to
-         ``101``. A batchSize of ``0`` means that the cursor will be
+       - Sets the number of documents to return in the first batch if the number of documents to return is over ``101``.
+         Defaults to `101``. A batchSize of ``0`` means that the cursor will be
          established, but no documents will be returned in the first batch.
 
          Unlike the previous wire protocol version, a batchSize of ``1`` for the

source/reference/method/MongoDBCollection-listSearchIndexes.txt

@@ -40,10 +40,13 @@ Parameters
 
      * - batchSize
        - integer
-       - Specifies the batch size for the cursor, which will apply to both the
+       - Specifies the batch size for the cursor, which will apply to both thex
          initial ``aggregate`` command and any subsequent ``getMore`` commands.
-         This determines the maximum number of documents to return in each
-         response from the server.
+         If batchSize is set, ``aggregate`` and any subsequent ``getMore`` commands returns the smaller of ``16`` megabytes of data 
+         or batchSize documents. Operations of type ``find()``, ``aggregate()``, ``listIndexes``, and ``listCollections`` return a maximum of ``16`` megabytes per batch. 
+         batchSize can enforce a smaller limit than ``16`` megabytes, but not a larger one. 
+
+         If batchSize is not set, ``aggregate`` and ``getMore`` commands return up to ``16`` megabytes of data. 
 
          A batchSize of ``0`` is special in that and will only apply to the
          initial ``aggregate`` command; subsequent ``getMore`` commands will use

source/reference/method/MongoDBDatabase-aggregate.txt

@@ -56,8 +56,16 @@ Parameters
        - integer
        - Specifies the batch size for the cursor, which will apply to both the
          initial ``aggregate`` command and any subsequent ``getMore`` commands.
-         This determines the maximum number of documents to return in each
-         response from the server.
+         
+         The ``aggregate`` command has an initial batch size of 101 documents by default.
+         Subsequent ``getMore`` operations issued against the resulting cursor have no default batch size, 
+         so they are limited only by the ``16`` megabyte message size.
+
+         If batchSize is set, ``aggregate`` and any subsequent ``getMore`` commands returns the smaller of 16 megabytes of data 
+         or batchSize documents. Operations of type ``aggregate`` return a maximum of ``16`` megabytes per batch. 
+         batchSize can enforce a smaller limit than ``16`` megabytes, but not a larger one. 
+
+         If batchSize is not set, ``aggregate`` and ``getMore`` commands return up to ``16`` megabytes of data. 
 
          A batchSize of ``0`` is special in that and will only apply to the
          initial ``aggregate`` command; subsequent ``getMore`` commands will use