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

[DOCS] A few grammar and word use corrections

This commit is contained in:
Karl Meisterheim 2014-03-27 19:27:16 -04:00 committed by Luca Cavanna
parent 08be94b455
commit 6d993bc810
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/search/suggesters/phrase-suggest.asciidoc
View File

@ -5,7 +5,7 @@ NOTE: In order to understand the format of suggestions, please
read the <<search-suggesters>> page first. read the <<search-suggesters>> page first.
The `term` suggester provides a very convenient API to access word The `term` suggester provides a very convenient API to access word
alternatives on token basis within a certain string distance. The API alternatives on a per token basis within a certain string distance. The API
allows accessing each token in the stream individually while allows accessing each token in the stream individually while
suggest-selection is left to the API consumer. Yet, often pre-selected suggest-selection is left to the API consumer. Yet, often pre-selected
suggestions are required in order to present to the end-user. The suggestions are required in order to present to the end-user. The
@ -48,8 +48,8 @@ curl -XPOST 'localhost:9200/_search' -d {
} }
-------------------------------------------------- --------------------------------------------------
The response contains suggested scored by the most likely spell The response contains suggestions scored by the most likely spell
correction first. In this case we got the expected correction correction first. In this case we received the expected correction
`xorr the god jewel` first while the second correction is less `xorr the god jewel` first while the second correction is less
conservative where only one of the errors is corrected. Note, the conservative where only one of the errors is corrected. Note, the
request is executed with `max_errors` set to `0.5` so 50% of the terms request is executed with `max_errors` set to `0.5` so 50% of the terms