diff --git a/source/applications/geospatial-indexes.txt b/source/applications/geospatial-indexes.txt
index 8f9563c09be..61cf6781e9a 100644
--- a/source/applications/geospatial-indexes.txt
+++ b/source/applications/geospatial-indexes.txt
@@ -409,7 +409,7 @@ command. You must specify both the coordinate and other field to
 
 .. code-block:: javascript
 
-   db.runCommand( { geoSearch: <haystack index>,
+   db.runCommand( { geoSearch: <collection>,
                     search: { <field>: <value> } } )
 
 For example, to return all documents with the value ``restaurants`` in
diff --git a/source/core/data-modeling.txt b/source/core/data-modeling.txt
index d9aee7e34bf..e7f21b1ac25 100644
--- a/source/core/data-modeling.txt
+++ b/source/core/data-modeling.txt
@@ -18,7 +18,7 @@ that:
   of data.
 
 Each document only needs to contain relevant fields to the entity or
-object that the document represents. In practice, *most documents in a
+object that the document represents. In practice, *most* documents in a
 collection share a similar structure. Schema flexibility means that
 you can model your documents in MongoDB so that they can closely
 resemble and reflect application-level objects.
diff --git a/source/core/geospatial-indexes.txt b/source/core/geospatial-indexes.txt
index 735923a83e1..0fe0cada508 100644
--- a/source/core/geospatial-indexes.txt
+++ b/source/core/geospatial-indexes.txt
@@ -205,16 +205,16 @@ following prototype:
 
    .. code-block:: javascript
 
-      { _id : 100, { long : 126.9, lat : 35.2 }, type : "restaurant"}
-      { _id : 200, { long : 127.5, lat : 36.1 }, type : "restaurant"}
-      { _id : 300, { long : 128.0, lat : 36.7 }, type : "national park"}
+      { _id : 100, pos: { long : 126.9, lat : 35.2 }, type : "restaurant"}
+      { _id : 200, pos: { long : 127.5, lat : 36.1 }, type : "restaurant"}
+      { _id : 300, pos: { long : 128.0, lat : 36.7 }, type : "national park"}
 
    The following operations creates a haystack index with buckets that
    store keys within 1 unit of longitude or latitude.
 
    .. code-block:: javascript
 
-      db.mydb.ensureIndex( { pos : "geoHaystack", type : 1 }, { bucketSize : 1 } )
+      db.mycoll.ensureIndex( { pos : "geoHaystack", type : 1 }, { bucketSize : 1 } )
 
    Therefore, this index stores the document with an ``_id`` field
    that has the value ``200`` in two
@@ -223,7 +223,7 @@ following prototype:
    1. in a bucket that includes the document  where the ``_id`` field
       has a value of ``100``, and
 
-   2. in a buckt that includes the document where the ``_id`` field
+   2. in a bucket that includes the document where the ``_id`` field
       has a value of ``300``.
 
 To query using a haystack index you use the :dbcommand:`geoSearch`
diff --git a/source/tutorial/model-embedded-one-to-one-relationships-between-documents.txt b/source/tutorial/model-embedded-one-to-one-relationships-between-documents.txt
index fe70fd5457e..c93b5ccb8f1 100644
--- a/source/tutorial/model-embedded-one-to-one-relationships-between-documents.txt
+++ b/source/tutorial/model-embedded-one-to-one-relationships-between-documents.txt
@@ -4,7 +4,7 @@
 Model Embedded One-to-One Relationships Between Documents
 =========================================================
 
-.. default-domain::
+.. default-domain:: mongodb
 
 Overview
 --------