Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/reference/query-dsl/match-phrase-prefix-query.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand All @@ -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
Expand All @@ -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.

Expand Down