(DOCSP-28580): Backport DOCSP-27811 to v6.0. (#2510) (#3578)

Co-authored-by: jmd-mongo <[email protected]>

Author: corryroot

source/tutorial/sort-results-with-indexes.txt

@@ -24,12 +24,14 @@ A blocking sort indicates that MongoDB must consume and process all
 input documents to the sort before returning results. Blocking sorts do
 not block concurrent operations on the collection or database.
 
-If MongoDB needs more than 100 megabytes of system memory for
-the blocking sort operation, MongoDB returns an error *unless* the query
-specifies :method:`cursor.allowDiskUse()` (*New in MongoDB 4.4*).
-:method:`~cursor.allowDiskUse()` allows MongoDB to use temporary files
-on disk to store data exceeding the 100 megabyte system memory limit
-while processing a blocking sort operation.
+Starting in MongoDB 6.0, if the server requires more than 100 megabytes 
+of memory for a pipeline execution stage, MongoDB automatically writes 
+temporary files to disk unless that query specifies
+``{ allowDiskUse: false }``. In versions 4.4 and 5.0, if the server 
+needs more than 100 megabytes of system memory for the blocking sort 
+operation, MongoDB returns an error unless that query specifies 
+:method:`cursor.allowDiskUse()`. For details, see 
+:parameter:`allowDiskUseByDefault`.
 
 Sort operations that use an index often have better performance than
 blocking sorts.