minor: edits and tweaks to unexpected shut down tweak.

Author: Sam Kleinman

aspiration/tutorial/recover-data-following-unexpected-shutdown.txt

@@ -4,7 +4,7 @@ Recover MongoDB Data following Unexpected Shutdown
 
 .. default-domain:: mongodb
 
-If MongoDB does not shutdown cleanly [#clean-shutdown]_ the on disk
+If MongoDB does not shutdown cleanly [#clean-shutdown]_ the on-disk
 representation of the data files will likely reflect an inconsistent
 state which leads to data corruption.
 
@@ -25,7 +25,7 @@ recover data that may be in an inconsistent state.
 .. [#clean-shutdown] To ensure a clean shut down, use the
    :option:`mongod --shutdown` option, your control script,
    "Control-C" (when running :program:`mongod` in interactive mode,)
-   or ``kill mongod`` or ``kill -2 mongod``.
+   or ``kill $(pidof mongod)`` or ``kill -2 $(pidof mongod)``.
 
 Process
 -------
@@ -37,10 +37,11 @@ When you are aware of a :program:`mongod` instance running without
 journaling that stops unexpectedly you should always run the repair
 operation before starting MongoDB again.
 
-If the ``mongod.lock`` file has data in the data directory specified
-by :setting:`dbpath`, ``/data/db`` by default, then :program:`mongod`
-will refuse to start, and you will find a message that contains the
-following line in your MongoDB log our output:
+If the ``mongod.lock`` file in the data directory specified by
+:setting:`dbpath`, ``/data/db`` by default, is *not* a zero-byte file,
+then :program:`mongod` will refuse to start, and you will find a
+message that contains the following line in your MongoDB log our
+output:
 
 .. code-block:: none