change based on feedback

Author: shuangela

source/includes/extracts-watch-option.yaml

@@ -1,16 +1,14 @@
 ref: watch-option-batchSize
 content: |
-  The maximum number of documents within each batch returned in a query result. By default,
-  the ``find()`` method has an initial batch size of ``101`` documents
-  and a maximum of 16 megabytes for each subsequent batch. This
-  option can enforce a smaller limit than 16 megabytes, but not a larger
+  The maximum number of documents within each batch returned in a query result, which applies 
+  to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of 
+  ``101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
+  option can enforce a smaller limit than 16 mebibytes, but not a larger
   one. If you set ``batchSize`` to a limit that results in batches larger than
-  16 MB, this option has no effect.
+  16 MiB, this option has no effect.
 
-  Irrespective of the ``batchSize`` option, the initial ``aggregate`` command
-  response for a change stream generally does not include any documents
-  unless another option is used to configure its starting point (e.g.
-  ``startAfter``).
+  This command determines the maximum number of change events to return in each response from the
+  server.
 ---
 ref: watch-option-fullDocument
 content: |

source/read/retrieve.txt

@@ -182,10 +182,10 @@ you can set in the array:
    * - ``batchSize`` 
      - | The maximum number of documents within each batch returned in a query result. By default,
          the ``find()`` method has an initial batch size of ``101`` documents
-         and a maximum of 16 megabytes for each subsequent batch. This
-         option can enforce a smaller limit than 16 megabytes, but not a larger
+         and a maximum size of 16 mebibytes for each subsequent batch. This
+         option can enforce a smaller limit than 16 mebibytes, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
-         16 MB, this option has no effect.
+         16 MiB, this option has no effect.
        | **Type**: ``integer``
 
    * - ``collation`` 

source/reference/method/MongoDBCollection-find.txt

@@ -52,12 +52,16 @@ Parameters
 
      * - batchSize
        - integer
-       - The maximum number of documents within each batch returned in a query result. By default,
-         the ``find()`` method has an initial batch size of ``101`` documents
-         and a maximum of 16 megabytes for each subsequent batch. This
-         option can enforce a smaller limit than 16 megabytes, but not a larger
+       - The maximum number of documents within each batch returned in a query result, which applies 
+         to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of 
+         `101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
+         option can enforce a smaller limit than 16 mebibytes, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
-         16 MB, this option has no effect.
+         16 MiB, this option has no effect.
+
+         A batchSize of ``0`` means that the cursor will be established, but no documents 
+         will be returned in the first batch. This may be useful for quickly returning a cursor
+         or failure from ``aggregate`` without doing significant server-side work.
 
          Unlike the previous wire protocol version, a batchSize of ``1`` for the
          :dbcommand:`find` command does not close the cursor.

source/reference/method/MongoDBCollection-listSearchIndexes.txt

@@ -40,18 +40,16 @@ Parameters
 
      * - batchSize
        - integer
-       - The maximum number of documents within each batch returned in a query result. By default,
-         the ``find()`` method has an initial batch size of ``101`` documents
-         and a maximum of 16 megabytes for each subsequent batch. This
-         option can enforce a smaller limit than 16 megabytes, but not a larger
+       - The maximum number of documents within each batch returned in a query result, which applies 
+         to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of 
+         `101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
+         option can enforce a smaller limit than 16 mebibytes, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
-         16 MB, this option has no effect. 
+         16 MiB, this option has no effect.
 
-         A batchSize of ``0`` is special in that and will only apply to the
-         initial ``aggregate`` command; subsequent ``getMore`` commands will use
-         the server's default batch size. This may be useful for quickly
-         returning a cursor or failure from ``aggregate`` without doing
-         significant server-side work.
+         A batchSize of ``0`` means that the cursor will be established, but no documents 
+         will be returned in the first batch. This may be useful for quickly returning a cursor
+         or failure from ``aggregate`` without doing significant server-side work.
 
      * - codec
        - MongoDB\\Codec\\DocumentCodec

source/reference/method/MongoDBDatabase-aggregate.txt

@@ -54,18 +54,16 @@ Parameters
 
      * - batchSize
        - integer
-       - The maximum number of documents within each batch returned in a query result. By default,
-         the ``find()`` method has an initial batch size of ``101`` documents
-         and a maximum of 16 megabytes for each subsequent batch. This
-         option can enforce a smaller limit than 16 megabytes, but not a larger
+       - The maximum number of documents within each batch returned in a query result, which applies 
+         to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of 
+         `101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
+         option can enforce a smaller limit than 16 mebibytes, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
-         16 MB, this option has no effect.
-         
-         A batchSize of ``0`` is special in that and will only apply to the
-         initial ``aggregate`` command; subsequent ``getMore`` commands will use
-         the server's default batch size. This may be useful for quickly
-         returning a cursor or failure from ``aggregate`` without doing
-         significant server-side work.
+         16 MiB, this option has no effect.
+
+         A batchSize of ``0`` means that the cursor will be established, but no documents 
+         will be returned in the first batch. This may be useful for quickly returning a cursor
+         or failure from ``aggregate`` without doing significant server-side work.
 
      * - bypassDocumentValidation
        - boolean