Skip to content

Commit 76d9bd5

Browse files
committed
clarify wording from jm feedback
1 parent 269819f commit 76d9bd5

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

source/reference/method/MongoDBCollection-find.txt

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,8 @@ Parameters
5252

5353
* - batchSize
5454
- integer
55-
- The maximum number of documents within each batch returned in a query result, which applies
56-
to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of
57-
`101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
55+
- The maximum number of documents to return in the first batch. By default, the ``find()``
56+
command has an initial batch size of `101`` documents. This
5857
option can enforce a smaller limit than 16 mebibytes, but not a larger
5958
one. If you set ``batchSize`` to a limit that results in batches larger than
6059
16 MiB, this option has no effect.

source/reference/method/MongoDBDatabase-aggregate.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ Parameters
5454

5555
* - batchSize
5656
- integer
57-
- The maximum number of documents within each batch returned in a query result, which applies
58-
to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of
57+
- The maximum number of documents within each batch returned in a query result.
58+
By default, the ``aggregate`` command has an initial batch size of
5959
`101`` documents and a maximum size of 16 mebibytes for each subsequent batch. This
6060
option can enforce a smaller limit than 16 mebibytes, but not a larger
6161
one. If you set ``batchSize`` to a limit that results in batches larger than

0 commit comments

Comments
 (0)