From 7999680fe09ebe1f8595b1af134d5ecf8fe0676f Mon Sep 17 00:00:00 2001 From: kstirman Date: Thu, 20 Jun 2013 08:49:54 -0300 Subject: [PATCH] Update optimize-query-performance-with-indexes-and-projections.txt --- ...ptimize-query-performance-with-indexes-and-projections.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/tutorial/optimize-query-performance-with-indexes-and-projections.txt b/source/tutorial/optimize-query-performance-with-indexes-and-projections.txt index e44144e4e3d..80a7d7e2f55 100644 --- a/source/tutorial/optimize-query-performance-with-indexes-and-projections.txt +++ b/source/tutorial/optimize-query-performance-with-indexes-and-projections.txt @@ -10,8 +10,8 @@ Create Indexes to Support Queries For commonly issued queries, create :doc:`indexes `. If a query searches multiple fields, create a :ref:`compound index `. Scanning an index is much faster than scanning a -collection. The indexes structures are smaller than the documents -reference, and store references in order. +collection. The index structures are smaller than the documents they +reference, and these references are stored in order. .. example:: If you have a ``posts`` collection containing blog posts, and if you regularly issue a query that sorts on the ``author_name``