You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by jb...@apache.org on 2021/03/05 14:22:50 UTC

[lucene-solr] 02/03: SOLR-15193: Fix wording

This is an automated email from the ASF dual-hosted git repository.

jbernste pushed a commit to branch branch_8x
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git

commit 1f006ff8f33782fe8460aea8c4bac5aad0a64d95
Author: Joel Bernstein <jb...@apache.org>
AuthorDate: Fri Mar 5 09:14:48 2021 -0500

    SOLR-15193: Fix wording
---
 solr/solr-ref-guide/src/graph.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/solr/solr-ref-guide/src/graph.adoc b/solr/solr-ref-guide/src/graph.adoc
index bb3e3d4..73351f7 100644
--- a/solr/solr-ref-guide/src/graph.adoc
+++ b/solr/solr-ref-guide/src/graph.adoc
@@ -283,8 +283,8 @@ relationship between the products in the basket.
 The `maxDocFreq` parameter can be used to limit the "walk" to only include baskets that appear in the index a certain
 number of times. Since each occurrence of a basket ID in the index is a product, limiting the document frequency of the
 basket ID will limit the size of basket. The `maxDocFreq` param is applied per shard. If there is a single
-shard or documents are co-located by basket ID then the `maxDocFreq` will be exact count.
-Otherwise it will return baskets with a max size of numshards*maxDocFreq.
+shard or documents are co-located by basket ID then the `maxDocFreq` will be an exact count.
+Otherwise it will return baskets with a max size of numShards*maxDocFreq.
 
 The example below shows the `maxDocFreq` parameter applied to the `nodes` expression.