Skip to content

Commit 51a0519

Browse files
david-cho-lerat-HL2nik9000
authored andcommitted
Correct some spelling in match-phrase-prefix docs (#24956)
1 parent 20d6f14 commit 51a0519

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/reference/query-dsl/match-phrase-prefix-query.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ GET /_search
1919

2020
It accepts the same parameters as the phrase type. In addition, it also
2121
accepts a `max_expansions` parameter (default `50`) that can control to how
22-
many prefixes the last term will be expanded. It is highly recommended to set
22+
many suffixes the last term will be expanded. It is highly recommended to set
2323
it to an acceptable value to control the execution time of the query. For
2424
example:
2525

@@ -43,7 +43,7 @@ GET /_search
4343
===================================================
4444
4545
The `match_phrase_prefix` query is a poor-man's autocomplete. It is very easy
46-
to use, which let's you get started quickly with _search-as-you-type_ but it's
46+
to use, which lets you get started quickly with _search-as-you-type_ but its
4747
results, which usually are good enough, can sometimes be confusing.
4848
4949
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
5353
adds these terms to the phrase query.
5454
5555
The problem is that the first 50 terms may not include the term `fox` so the
56-
phase `quick brown fox` will not be found. This usually isn't a problem as
56+
phrase `quick brown fox` will not be found. This usually isn't a problem as
5757
the user will continue to type more letters until the word they are looking
5858
for appears.
5959

0 commit comments

Comments
 (0)