Skip to content

Commit 671a209

Browse files
Correct errors in min_hash filter documentation
Related to #39671
1 parent be9c37f commit 671a209

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/reference/analysis/tokenfilters/minhash-tokenfilter.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ occurring in a document is low. At the same time, as
3030
internally each shingle is hashed into to 128-bit hash, you should choose
3131
`k` small enough so that all possible
3232
different k-words shingles can be hashed to 128-bit hash with
33-
minimal collision. 5-word shingles typically work well.
33+
minimal collision.
3434

3535
* choosing the right settings for `hash_count`, `bucket_count` and
3636
`hash_set_size` needs some experimentation.
@@ -39,7 +39,7 @@ minimal collision. 5-word shingles typically work well.
3939
will provide a higher guarantee that different tokens are
4040
indexed to different buckets.
4141
** to improve the recall,
42-
you should increase `hash_token` parameter. For example,
42+
you should increase `hash_count` parameter. For example,
4343
setting `hash_count=2`, will make each token to be hashed in
4444
two different ways, thus increasing the number of potential
4545
candidates for search.

0 commit comments

Comments
 (0)