DOCS-330 final round of comments on the indexing documents

Author: Sam Kleinman

draft/administration/indexes.txt

@@ -261,7 +261,7 @@ Consideration
 ~~~~~~~~~~~~~
 
 :ref:`Background index creation operations
-<index-creation-background>` became *foreground* indexing operations
+<index-creation-background>` become *foreground* indexing operations
 on :term:`secondary` members of replica sets. These foreground
 operations will block all replication on the secondaries, and don't
 allow any reads. As a result in most cases use the following procedure
@@ -282,7 +282,7 @@ Procedure
    :option:`--replSet <mongod --replSet>` option. Allow replication
    to catch up on this member.
 
-#. Replete this operation on all of the remaining secondaries.
+#. Repeat this operation on all of the remaining secondaries.
 
 #. Run :func:`rs.stepDown()` on the :term:`primary` member of the
    set, and then repeat this procedure on the former primary.
@@ -296,11 +296,9 @@ Procedure
 
 .. note::
 
-   This procedure *does* block indexing on one member of the
-   replica set at a time. However, the foreground indexing
-   operation is more efficient than the background index operation,
-   and will only affect one secondary at a time rather than *all*
-   secondaries at the same time.
+   This procedure *does* take one member out of the replica set at a
+   time. However, this procedure will only affect one member of the
+   set at a time rather than *all* secondaries at the same time.
 
 .. [#different-port] By running the :program:`mongod` on a different
    port, you ensure that the other members of the replica set and all
@@ -357,7 +355,7 @@ Monitoring and Controlling Index Building
    completion of DOCS-162
 
 To see the status of the indexing processes, you can use the
-:func:`db.currentOP()` method in the :program:`mongo` shell. The value
+:func:`db.currentOp()` method in the :program:`mongo` shell. The value
 of the ``query`` field and the ``msg`` field will indicate if the
 operation is an index build. The ``msg`` field also indicates the
 percent of the build that is complete.

draft/applications/indexes.txt

@@ -118,7 +118,7 @@ results. For example:
       db.collection.find( { a:5, b:3, c:{ $lt:2 }, d:{ $gt:4 } } ).sort( { c:1 } )
 
    However, the following query operations would not be able to sort
-   data using the index:
+   the results using the index:
 
    .. code-block:: javascript
 

draft/core/indexes.txt

@@ -410,11 +410,11 @@ construction:
    members of the set. All indexing operations on secondaries block
    replication.
 
-   To rebuild large indexes on secondaries the best approach is to
+   To build large indexes on secondaries the best approach is to
    restart one secondary at a time in "standalone" mode and build the
-   index. When the index is rebuilt, restart as a member of the
+   index. After building the index, restart as a member of the
    replica set, allow it to catch up with the other members of the
-   set, and then rebuild the index on the next secondary. When all the
+   set, and then build the index on the next secondary. When all the
    secondaries have the new index, step down the primary, restart it
    as a standalone, and build the index on the former primary.
 
@@ -563,9 +563,12 @@ when the query must filter along another dimension.
    miles of a given point *and* have a type field value of "museum," a
    haystack index would be provide the best support for these queries.
 
-Haystack indices allow you to tune your bucket size to the
+Haystack indexes allow you to tune your bucket size to the
 distribution of your data, so that in general you search only very
-small regions of 2d space for a particular kind of document.
+small regions of 2d space for a particular kind of document. These
+indexes are not suited for finding the closest documents to a
+particular location, when the closest documents are far away compared
+to bucket size.
 
 Index Limitations
 -----------------

source/includes/note-build-indexes-on-replica-sets.rst

@@ -1,4 +1,4 @@
 .. note::
 
-   To rebuild indexes for a :term:`replica set` see
+   To build or rebuild indexes for a :term:`replica set` see
    :ref:`index-rebuilding-replica-sets`.