DOCS-693 review edits

Author: Bob Grabar

source/faq/storage.txt

@@ -105,9 +105,9 @@ RAM.
 Why are the files in my data directory larger than the data in my database?
 ---------------------------------------------------------------------------
 
-The data files in your data directory, which is the ``/data/db``
+The data files in your data directory, which is the :file:`/data/db`
 directory in default configurations, might be larger than the data set
-inserted into the database. This is caused by pre-allocated files and by
+inserted into the database. This is caused by preallocated files and by
 empty blocks, as explained here.
 
 - Preallocated data files
@@ -119,20 +119,20 @@ empty blocks, as explained here.
   megabytes, the next 128 megabytes, and so on, up to 2 gigabytes, at
   which point all subsequent files are 2 gigabytes. The data files,
   therefore, contain files for which space is allocated but no data yet
-  exists. A file might preallocated 1 gigabyte but be 90% empty. For
+  exists. A file might preallocate 1 gigabyte but be 90% empty. For
   databases of hundreds of gigabytes, unallocated space is small
   compared to the database and is insignificant.
 
   On UNIX, :program:`mongod` preallocates an additional data file
-  prefilled with zero bytes. Pre-filling in the background prevents
+  filled with zero bytes. Pre-filling in the background prevents
   significant delays when a new database file is next allocated.
 
-  You can disable preallocation with the :option:`--nopreallo <mongod
-  --repair>` command line option. Do not use this option in production
+  You can disable preallocation with the :option:`--noprealloc <mongod
+  --noprealloc>` command line option. Do not use this option in production
   environments. This option is intended for tests with small data sets
   where you drop the database after each test.
 
-  On Linux systems you can use ``hdparam`` to get an idea of how costly
+  On Linux systems you can use ``hdparm`` to get an idea of how costly
   allocation might be:
 
   .. code-block:: sh
@@ -192,7 +192,7 @@ Alternately, you can view specific measures of size using any of these methods:
 Can I check the size of indexes?
 --------------------------------
 
-To view the size of the data allocated for an index, :method:`validate()
+To view the size of the data allocated for an index, issue the :method:`validate()
 <db.collection.validate()>` method using the index namespace.
 
 .. example:: You look up an index namespace in the ``system.namespaces``
@@ -234,7 +234,7 @@ something like this in the log:
 
 The server remains in this state forever, blocking all writes including
 deletes. However, reads still work. To delete some data and compact,
-using the :dbcommand:`compact` command, you must first restart the server
+using the :dbcommand:`compact` command, you must restart the server
 first.
 
 If your server runs out of disk space for journal files, the server