DOCS-5937 WT production notes cpu and swap space

Author: kay-kim

source/administration/production-notes.txt

@@ -197,19 +197,20 @@ Allocate Sufficient RAM and CPU
 MMAPv1
 ``````
 
-The MMAPv1 storage engine is not CPU bound due to its concurrency
-model. As such, increasing the number of cores can help but does not
-provide significant return.
+Due to its concurrency model, the MMAPv1 storage engine does not
+require many CPU cores . As such, increasing the number of cores can
+help but does not provide significant return.
 
 Increasing the amount of RAM accessible to MongoDB may help reduce the
 frequency of page faults.
 
 WiredTiger
 ``````````
 
-The WiredTiger storage engine is CPU bound. Specifically, the total
-number of active threads (i.e. concurrent operations) relative to the
-number of CPUs can impact performance:
+The WiredTiger storage engine is multithreaded and can take advantage
+of many CPU cores. Specifically, the total number of active threads
+(i.e. concurrent operations) relative to the number of CPUs can impact
+performance:
 
 - Throughput *increases* as the number of concurrent active operations
   increases up to the number of CPUs.
@@ -319,8 +320,8 @@ store MongoDB data in swap space.  On Windows systems, using MMAPv1
 requires extra swap space due to commitment limits. For details,
 see :ref:`MongoDB on Windows <production-windows-pagefile>`.
 
-The WiredTiger storage engine also ensures that the operating system
-does not store MongoDB data in swap space.
+For the WiredTiger storage engine, given sufficient memory pressure,
+WiredTiger may store data in swap space .
 
 RAID
 ````