diff options
| author | Elijah <elijahdjmarshall@users.noreply.github.com> | 2017-01-17 20:59:19 -0500 |
|---|---|---|
| committer | Jason Tedor <jason@tedor.me> | 2017-01-17 21:00:36 -0500 |
| commit | 3b92179e0965b8736482323c5d9080416adf8362 (patch) | |
| tree | 6fdc8b36bb51160687eabad4d780f445a27ff37b /docs/reference/how-to | |
| parent | b56605d68c84714c05f8536a29e99ccdc82f7f63 (diff) | |
Improve wording in recipes docs
This commit improves some of the wording the recipes docs.
Relates #22661
Diffstat (limited to 'docs/reference/how-to')
| -rw-r--r-- | docs/reference/how-to/recipes.asciidoc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/reference/how-to/recipes.asciidoc b/docs/reference/how-to/recipes.asciidoc index 0bb158f88e..4d1a4b67a2 100644 --- a/docs/reference/how-to/recipes.asciidoc +++ b/docs/reference/how-to/recipes.asciidoc @@ -169,9 +169,9 @@ the query need to be matched exactly while other parts should still take stemming into account? Fortunately, the `query_string` and `simple_query_string` queries have a feature -that allows to solve exactly this problem: `quote_field_suffix`. It allows to -tell Elasticsearch that words that appear in between quotes should be redirected -to a different field, see below: +that solve this exact problem: `quote_field_suffix`. This tell Elasticsearch +that the words that appear in between quotes are to be redirected to a different +field, see below: [source,js] -------------------------------------------------- @@ -218,7 +218,7 @@ GET index/_search -------------------------------------------------- // TESTRESPONSE[s/"took": 2,/"took": "$body.took",/] -In that case, since `ski` was in-between quotes, it was searched on the +In the above case, since `ski` was in-between quotes, it was searched on the `body.exact` field due to the `quote_field_suffix` parameter, so only document `1` matched. This allows users to mix exact search with stemmed search as they like. |