rr feedback

Author: shuangela

source/includes/extracts-watch-option.yaml

@@ -2,13 +2,9 @@ ref: watch-option-batchSize
 content: |
   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 MiB, this option has no effect.
-
-  This command determines the maximum number of change events to return in each response from the
-  server.
+  ``101`` documents and a maximum size of 16 mebibytes (MiB) for each subsequent batch. This
+  option can enforce a smaller limit than 16 MiB, but not a larger one. If you set ``batchSize`` 
+  to a limit that results in batches larger than 16 MiB, this option has no effect.
 ---
 ref: watch-option-fullDocument
 content: |

source/read/retrieve.txt

@@ -182,8 +182,8 @@ 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 size of 16 mebibytes for each subsequent batch. This
-         option can enforce a smaller limit than 16 mebibytes, but not a larger
+         and a maximum size of 16 mebibytes (MiB) for each subsequent batch. This
+         option can enforce a smaller limit than 16 MiB, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
          16 MiB, this option has no effect.
        | **Type**: ``integer``

source/reference/method/MongoDBCollection-find.txt

@@ -54,13 +54,13 @@ Parameters
        - integer
        - The maximum number of documents to return in the first batch. By default, the ``find()`` 
          command has an initial batch size of ``101`` documents. This
-         option can enforce a smaller limit than 16 mebibytes, but not a larger
+         option can enforce a smaller limit than 16 mebibytes (MiB), but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
          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.
+         or failure 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/MongoDBDatabase-aggregate.txt

@@ -56,8 +56,8 @@ Parameters
        - integer
        - The maximum number of documents within each batch returned in a query result.
          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
+         ``101`` documents and a maximum size of 16 mebibytes (MiB) for each subsequent batch. This
+         option can enforce a smaller limit than 16 MiB, but not a larger
          one. If you set ``batchSize`` to a limit that results in batches larger than
          16 MiB, this option has no effect.