DOCS-391: fixing errors and tweaks

Author: Sam Kleinman

source/core/indexes.txt

@@ -32,7 +32,8 @@ indexes:
 - When the index covers queries, the database returns results more
   quickly than queries that have to scan many individual documents. An
   index "covers" a query if the keys of the index stores all the data
-  that the query must return.
+  that the query must return. See :ref:`indexes-covered-queries` for
+  more information.
 
 - Using queries with good index coverage will reduce the number of full
   documents that MongoDB needs to store in memory, thus maximizing database
@@ -60,7 +61,7 @@ introduction to their use.
 .. index:: _id index
 .. index:: _id
 .. index:: index; _id
-.. index:: index types; primary
+.. index:: index types; primary key
 .. _index-type-primary:
 
 _id
@@ -103,7 +104,7 @@ is a 12-byte unique identifiers suitable for use as the value of an
 Secondary Indexes
 ~~~~~~~~~~~~~~~~~
 
-All indexes other than the index on the ``_id`` field are
+All indexes in MongoDB are
 :term:`secondary indexes <secondary index>`. You can create indexes on
 any field within any document or sub-document. Additionally, you can
 create compound indexes with multiple fields, so that a single query

source/reference/glossary.txt

@@ -271,22 +271,17 @@ Glossary
       prevent other processes from writing or reading.
 
    index
-      A data structure that optimizes queries.
-
-      .. seealso:: The :wiki:`Indexes` wiki page.
-
-      .. STUB :doc:`/core/indexing`
+      A data structure that optimizes queries. See
+      :doc:`/core/indexes` for more information.
 
    secondary index
-      An index on any field that isn't the "primary key" for a
-      collection. In MongoDB the "primary key" is the ``_id`` field.
+      A database :term:`index` that improves query performance by
+      minimizing the amount of work that the query engine must perform
+      to fulfill a query.
 
    compound index
-      An :term:`index` consisting of two or more keys.
-
-      .. seealso:: The :wiki:`Indexes` wiki page.
-
-      .. STUB :doc:`/core/indexing`
+      An :term:`index` consisting of two or more keys. See
+      :doc:`/core/indexes` for more information.
 
    btree
       A data structure used by most database management systems

source/release-notes/1.8.txt

@@ -238,15 +238,15 @@ aggregation
 Sparse and Covered Indexes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-:ref:`Sparse Indexes <sparse-index>` are indexes that only include
+:ref:`Sparse Indexes <index-type-sparse>` are indexes that only include
 documents that contain the fields specified in the index. Documents
 missing the field will not appear in the index at all. This can
-significantly reduce index size for attributes that are contained in a
+significantly reduce index size for indexes of fields that contain only a
 subset of documents within a :term:`collection`.
 
-:ref:`Covered Indexes <use-covered-queries>` enable queries to be
-answered entirely from the index when the query only requests fields
-that are contained in the index.
+:ref:`Covered Indexes <covered-queries>` enable MongoDB to answer
+queries entirely from the index when the query only selects fields
+that the index contains. 
 
 Incremental MapReduce Support
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -318,14 +318,14 @@ Additional Changes and Enhancements
 - :program:`mongos` routes ``slaveOk`` queries to :term:`secondaries
   <secondary>` in :term:`replica sets <replica set>`.
 
-- New :dbcommand:`mapReduce` output options
+- New :dbcommand:`mapReduce` output options. 
 
-- :ref:`sparse-index`.
+- :ref:`index-type-sparse`.
 
 1.7.3
 `````
 
-- Initial :ref:`covered index <use-covered-queries>` support
+- Initial :ref:`covered index <covered-queries>` support.
 
 - Distinct can use data from indexes when possible.
 
@@ -338,7 +338,7 @@ Additional Changes and Enhancements
 1.7.2
 `````
 
-- :operator:`$rename` operator allows renaming of attributes in a document.
+- :operator:`$rename` operator allows renaming of fields in a document.
 
 - :method:`db.eval()` not to block.