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

Fix some typos in documentation.

This commit is contained in:
Hannes Korte 2014-03-28 17:09:56 +01:00 committed by Simon Willnauer
parent 3338750f14
commit c11293ad78
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/search/request/highlighting.asciidoc
View File

@ -509,7 +509,7 @@ it is just fine not to list the field to which the matches are combined
Technically it is also fine to add fields to `matched_fields` that Technically it is also fine to add fields to `matched_fields` that
don't share the same underlying string as the field to which the matches don't share the same underlying string as the field to which the matches
are combined. The results might not make much sense and if one of the are combined. The results might not make much sense and if one of the
matches is off the end of the text then the whole the query will fail. matches is off the end of the text then the whole query will fail.
[NOTE] [NOTE]
=================================================================== ===================================================================

2
docs/reference/search/request/named-queries-and-filters.asciidoc
View File

@ -53,5 +53,5 @@ query (just so there will be a place to set a name for it), for example:
==== Named queries ==== Named queries
The support for the `_name` option on queries as available from version `0.90.4` and the support on filters is available The support for the `_name` option on queries is available from version `0.90.4` and the support on filters is available
also in versions before `0.90.4`. also in versions before `0.90.4`.

2
docs/reference/search/suggesters.asciidoc
View File

@ -136,7 +136,7 @@ suggestion specific option. The suggest text specified on suggestion
level override the suggest text on the global level. level override the suggest text on the global level.
[float] [float]
=== Other suggest example. === Other suggest example
In the below example we request suggestions for the following suggest In the below example we request suggestions for the following suggest
text: `devloping distibutd saerch engies` on the `title` field with a text: `devloping distibutd saerch engies` on the `title` field with a

4
docs/reference/search/suggesters/phrase-suggest.asciidoc
View File

@ -11,8 +11,8 @@ 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
`phrase` suggester adds additional logic on top of the `term` suggester `phrase` suggester adds additional logic on top of the `term` suggester
to select entire corrected phrases instead of individual tokens weighted to select entire corrected phrases instead of individual tokens weighted
based on `ngram-langugage` models. In practice it this suggester will be based on `ngram-langugage` models. In practice this suggester will be
able to make better decision about which tokens to pick based on able to make better decisions about which tokens to pick based on
co-occurence and frequencies. co-occurence and frequencies.
==== API Example ==== API Example

2
docs/reference/search/suggesters/term-suggest.asciidoc
View File

@ -33,7 +33,7 @@ doesn't take the query into account that is part of request.
Defines how suggestions should be sorted per suggest text Defines how suggestions should be sorted per suggest text
term. Two possible values: term. Two possible values:
+ +
** `score`: Sort by sore first, then document frequency and ** `score`: Sort by score first, then document frequency and
then the term itself. then the term itself.
** `frequency`: Sort by document frequency first, then similarity ** `frequency`: Sort by document frequency first, then similarity
score and then the term itself. score and then the term itself.