honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Correct some spelling in match-phrase-prefix docs (#24956)

This commit is contained in:
David Cho-Lerat 2017-05-30 15:01:13 +02:00 committed by Nik Everett
parent efcbfb7c32
commit c939bcb7f5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/query-dsl/match-phrase-prefix-query.asciidoc
View File

@ -19,7 +19,7 @@ GET /_search
It accepts the same parameters as the phrase type. In addition, it also
accepts a `max_expansions` parameter (default `50`) that can control to how
many prefixes the last term will be expanded. It is highly recommended to set
many suffixes the last term will be expanded. It is highly recommended to set
it to an acceptable value to control the execution time of the query. For
example:
@ -43,7 +43,7 @@ GET /_search
===================================================
The `match_phrase_prefix` query is a poor-man's autocomplete. It is very easy
to use, which let's you get started quickly with _search-as-you-type_ but it's
to use, which lets you get started quickly with _search-as-you-type_ but its
results, which usually are good enough, can sometimes be confusing.
Consider the query string `quick brown f`. This query works by creating a
@ -53,7 +53,7 @@ dictionary to find the first 50 terms that begin with `f`, and
adds these terms to the phrase query.
The problem is that the first 50 terms may not include the term `fox` so the
phase `quick brown fox` will not be found. This usually isn't a problem as
phrase `quick brown fox` will not be found. This usually isn't a problem as
the user will continue to type more letters until the word they are looking
for appears.