From 38b2c1082b7bcf3ba3988c94869f7393fe269ca9 Mon Sep 17 00:00:00 2001 From: Philipp Hagemeister Date: Sun, 28 Feb 2016 19:24:12 +0100 Subject: [PATCH] Fix typo in README Fix a simple typo in the README file. I don't dare to delete `and updated`, which seems totally wrong in this sentence. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b2ce81d..203bcf4 100755 --- a/README.md +++ b/README.md @@ -440,7 +440,7 @@ db.count({}, function (err, count) { * `options` is an object with two possible parameters * `multi` (defaults to `false`) which allows the modification of several documents if set to true * `upsert` (defaults to `false`) if you want to insert a new document corresponding to the `update` rules if your `query` doesn't match anything. If your `update` is a simple object with no modifiers, it is the inserted document. In the other case, the `query` is stripped from all operator recursively, and the `update` is applied to it. - * `returnUpdatedDocs` (defaults to `false`, not MongoDB-compatible) if set to true and update is not an upsert, will return the array of documents matched bu the find query and updated. Updated documents will be returned even if the update did not actually modify them + * `returnUpdatedDocs` (defaults to `false`, not MongoDB-compatible) if set to true and update is not an upsert, will return the array of documents matched by the find query and updated. Updated documents will be returned even if the update did not actually modify them. * `callback` (optional) signature: `(err, numAffected, affectedDocuments, upsert)`. **Warning**: the API was changed between v1.7.4 and v1.8. Please refer to the change log to see the change. * For an upsert, `affectedDocuments` contains the inserted document and the `upsert` flag is set to `true`. * For a standard update with `returnUpdatedDocs` flag set to `false`, `affectedDocuments` is not set.