DOCS-386 review edits

Author: Bob Grabar

source/administration/journaling.txt

@@ -8,9 +8,9 @@ MongoDB uses *write ahead logging* to an on-disk :term:`journal` to
 guarantee :doc:`write operation </core/write-operations>` durability
 and to provide crash resiliency. Before applying a change to the data
 files, MongoDB writes the change operation to the journal. If MongoDB
-should terminate or encounter an error before it can write the
-data to disk, MongoDB can re-apply the write operation and maintain a
-consistent state.
+should terminate or encounter an error before it can write the changes
+from the journal to the data files, MongoDB can re-apply the write
+operation and maintain a consistent state.
 
 *Without* a journal, if :program:`mongod` exits unexpectedly, you must assume
 your data is in an inconsistent state, and you must run either

source/core/replication-internals.txt

@@ -260,7 +260,7 @@ In order to remain up-to-date with the current state of the
 entries from other members. Members sync data at two different points:
 
 - "Initial sync" occurs when MongoDB creates new databases on a new or
-  restored member, populating the the member with the replica set's
+  restored member, populating the member with the replica set's
   data. When a new or restored member joins or rejoins a set, the member
   waits to receive heartbeats from other members. By default, the member
   syncs from the *the closest* member of the set that is either the

source/reference/command/replSetSyncFrom.txt

@@ -10,7 +10,7 @@ replSetSyncFrom
 
    :option host: Specifies the name and port number of the replica set member
                  that this member replicates from. Use
-                 the ``[hostname]:[port]`` from.
+                 the ``[hostname]:[port]`` form.
 
    :dbcommand:`replSetSyncFrom` allows you to explicitly configure
    which host the current :program:`mongod` will poll :term:`oplog`
@@ -30,7 +30,7 @@ replSetSyncFrom
 
    If you attempt to replicate from a member that is more than 10 seconds
    behind the current member, :program:`mongod` will return and log a
-   warning, but it *still will* replicate from such members.
+   warning, but it still *will* replicate from the member that is behind.
 
    The command has the following prototype form:
 

source/reference/glossary.txt

@@ -923,3 +923,7 @@ Glossary
 
       - "Replication" occurs continually after initial sync and keeps
         the member updated with changes to the replica set's data.
+
+   initial sync
+      The :term:`replica set` operation that replicates data from an
+      existing replica set member to a new or restored replica set member.