DOCS-437 troubleshooting an oplog error: final edits

Author: Bob Grabar

source/administration/replica-sets.txt

@@ -713,12 +713,11 @@ If you receive the following error:
 Then the value for the ``ts`` field in the last oplog entry might be of
 the wrong data type. The correct data type is Timestamp.
 
-You can check the data type by running the following two queries. If the
+You can check the data type by running the following two queries against the oplog. If the
 data type is correct, the queries return the same document; if
 incorrect, they return different documents.
 
-First run a query to return the last document in the oplog, no matter
-its data type:
+First run a query to return the last document in the oplog:
 
 .. code-block:: javascript
 
@@ -732,13 +731,16 @@ for type ``17``, which is the Timestamp data type.
 
    db.oplog.rs.find({ts:{$type:17}}).sort({$natural:-1}).limit(1)
 
+If the queries don't return the same document, then the last document in
+the oplog has the wrong data type in the ``ts`` field.
+
 .. example::
 
    As an example, if the first query returns this as the last oplog entry:
 
    .. code-block:: javascript
 
-      { "h" : NumberLong("8191276672478122996"), "ns" : "", "o" : { "msg" : "Reconfig set", "version" : 4 }, "op" : "n", "ts" : true }
+      { "ts" : {t: 1347982456000, i: 1}, "h" : NumberLong("8191276672478122996"), "op" : "n", "ns" : "", "o" : { "msg" : "Reconfig set", "version" : 4 } }
 
    And the second query returns this as the last entry where ``ts`` is a Timestamp:
 
@@ -755,4 +757,4 @@ time to pull the oplog into memory:
 
 .. code-block:: javascript
 
-   db.oplog.rs.update({ts:{t:1234567891000,i:1234}}, {$set:{ts:new Timestamp(1234567891000, 1234)}})
+   db.oplog.rs.update({ts:{t:1347982456000,i:1}}, {$set:{ts:new Timestamp(1347982456000, 1)}})