diff --git a/source/core/read-operations.txt b/source/core/read-operations.txt
index 76f1f7b4484..c784636cea1 100644
--- a/source/core/read-operations.txt
+++ b/source/core/read-operations.txt
@@ -572,8 +572,8 @@ To create a new query plan, the query optimizer:
 
 1. runs the query against several candidate indexes in parallel.
 
-#. The query optimizer records the matches in a common results buffer
-   or buffers:
+#. records the matches in a common results buffer
+   or buffers.
 
    - If the candidate plans include only :term:`ordered query plans
      <ordered query plan>`, there is a single common results buffer.
@@ -916,13 +916,13 @@ For more information on the aggregation framework see
 Additionally, MongoDB provides a number of simple data aggregation
 operations for more basic data aggregation operations:
 
-- :method:`count() <cursor.count()>`
+- :method:`~cursor.count()`
 
-- :dbcommand:`distinct() <distinct>`
+- :method:`~db.collection.distinct()`
 
-- :method:`group()`
+- :method:`~db.collection.group()`
 
-- :dbcommand:`mapReduce() <mapReduce>` (See also
+- :method:`~db.collection.mapReduce()` (See also
   :doc:`/applications/map-reduce`.)
 
 .. index:: read operation; architecture
@@ -939,7 +939,7 @@ Read Operations From Sharded Clusters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 :term:`Sharded clusters <sharded cluster>` allow you to partition a
-data set among a cluster of program:`mongod` in a way that is nearly
+data set among a cluster of :program:`mongod` in a way that is nearly
 transparent to the application. See the :doc:`/sharding` section of
 this manual for additional information about these deployments.
 
diff --git a/source/core/write-operations.txt b/source/core/write-operations.txt
index fc85008c1b4..8d8dacfd37b 100644
--- a/source/core/write-operations.txt
+++ b/source/core/write-operations.txt
@@ -463,7 +463,7 @@ can cause the secondary's state to fall behind that of the primary. Secondaries
 that are significantly behind the primary present problems for normal
 operation of the replica set, particularly :ref:`failover
 <replica-set-failover-administration>` in the form of :ref:`rollbacks
-<replica-set-rollback>` as well as general :ref:`re2ad consistency
+<replica-set-rollback>` as well as general :ref:`read consistency
 <replica-set-consistency>`.
 
 To help avoid this issue, you can customize the :ref:`write concern