From 08e5f1dcf6529090caffe7c3a817a05cfd3885d1 Mon Sep 17 00:00:00 2001 From: Levi Thomason Date: Tue, 5 Dec 2017 10:48:13 -0800 Subject: [PATCH] docs(indexes): fix grammatical error --- source/applications/indexes.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/applications/indexes.txt b/source/applications/indexes.txt index b8d5e27c565..f7d90cc9451 100644 --- a/source/applications/indexes.txt +++ b/source/applications/indexes.txt @@ -20,7 +20,7 @@ understanding of your application's queries. Before you build indexes, map out the types of queries you will run so that you can build indexes that reference those fields. Indexes come with a performance cost, but are more than worth the cost for frequent queries on large -data set. Consider the relative frequency of each query in the +data sets. Consider the relative frequency of each query in the application and whether the query justifies an index. The best overall strategy for designing indexes is to profile a