Summary
Update the statement in the "Requires a write lock for the duration of the operation" and statement in JSDoc comments (and documentation) for `findOneAndUpdate`, `findOneAndDelete`, and `findOneAndReplace` methods.
 
Background
The write lock statement seems to describe MMAPv1 storage engine behaviour (database-level locking). Since MongoDB 3.2, WiredTiger is the default engine, which uses document-level concurrency control, not collection-level write locks, and uses only intent locks at collection levels.
 
Other References * [MongoDB 3.0: Seizing Opportunities | Eliot's Blog|http://www.eliothorowitz.com/blog/2015/03/03/mongodb-3.0-seizing-opportunities/]