minor: reflowing lines and paragraphs

Author: Sam Kleinman

draft/faq/storage.txt

@@ -18,20 +18,32 @@ the :doc:`complete list of FAQs </faq>` or post your question to the
 What are Memory Mapped Files?
 -----------------------------
 
-Memory mapped files are segments of virtual memory which have been assigned a direct byte-for-byte correlation with some portion of a file or resource.  Once present, this correlation between the file and the memory space permits applications to treat the mapped portion as if it were primary memory.
+Memory mapped files are segments of virtual memory which have been
+assigned a direct byte-for-byte correlation with some portion of a
+file or resource.  Once present, this correlation between the file and
+the memory space permits applications to treat the mapped portion as
+if it were primary memory.
 
 How does memory-mapped file access work in MongoDB?
 ----------------------------------------
 
 MongoDB uses memory-mapped files for memory management.
 
-MongoDB memory maps the files when they are first accessed; you're letting the OS know you'd like the contents of the files available as if they were in some portion of memory.  It should be noted that each OS caches its own components in memory, and also provides memory buffers for network connections and disk drivers in addition to applications. 
+MongoDB memory maps the files when they are first accessed; you're
+letting the OS know you'd like the contents of the files available as
+if they were in some portion of memory.  It should be noted that each
+OS caches its own components in memory, and also provides memory
+buffers for network connections and disk drivers in addition to
+applications.
 
 This doesn't necessarily mean the files are in memory already-- when you go to
 access any point, the OS checks if this 'page' is in physical ram or
 not.  
 
-If the page is already in memory, it returns whatever's in memory in that location.  If the page is not in memory, then it will fetch that portion of the file, make sure it's in memory, and then return it to you.
+If the page is already in memory, it returns whatever's in memory in
+that location.  If the page is not in memory, then it will fetch that
+portion of the file, make sure it's in memory, and then return it to
+you.
 
 Writing works in the same fashion-- MongoDB tries to write to a memory
 page. If the page is in RAM, then it works quickly (just swapping some bits
@@ -53,25 +65,32 @@ load it into RAM...an expensive task, overall.
 What is the difference between soft and hard page faults?
 ---------------------------------------------------------
 
-A page fault implies a "hard" page fault, which requires disk access.  A "soft" page fault merely moves memory pages from one list to another, and is not as expensive.
+A page fault implies a "hard" page fault, which requires disk access.
+A "soft" page fault merely moves memory pages from one list to
+another, and is not as expensive.
 
 What tools can I use to investigate storage use in MongoDB?
 -----------------------------------------------------------
 
-There is a command whose output provides the current state of the "active" database, see :doc: 'Database Statistics Reference </reference/database-statistics>'.
+There is a command whose output provides the current state of the
+"active" database, see :doc: 'Database Statistics Reference
+</reference/database-statistics>'.
 
 What is the working set?
 ------------------------
 
-The working set is an approximation of the set of pages that a certain process will access in the future (say, during the next 't' time units), and more specifically is suggested to be an indication of what pages ought to be kept in main memory to allow most progress to be made in the execution of that process.
+The working set is an approximation of the set of pages that a certain
+process will access in the future (say, during the next 't' time
+units), and more specifically is suggested to be an indication of what
+pages ought to be kept in main memory to allow most progress to be
+made in the execution of that process.
 
 A common misconception in using MongoDB is that the working set can be
 reduced to a discrete value.  It's important to understand that the
 working set is simply a way of thinking about the data one is
 accessing and that which MongoDB is working with frequently.
 
-For instance, if you are running a query that has to do a full table scan, then your working set is every document scanned.
-Conversely, if your query only reads the most recent 100
-documents, then the working set will be those 100 documents.
-
------------------------------------------------------------
+For instance, if you are running a query that has to do a full table
+scan, then your working set is every document scanned.  Conversely, if
+your query only reads the most recent 100 documents, then the working
+set will be those 100 documents.