From c11293ad78a77ece0ae5eddb5e4d0a460a13c8e9 Mon Sep 17 00:00:00 2001 From: Hannes Korte Date: Fri, 28 Mar 2014 17:09:56 +0100 Subject: [PATCH] Fix some typos in documentation. --- docs/reference/search/request/highlighting.asciidoc | 2 +- .../search/request/named-queries-and-filters.asciidoc | 2 +- docs/reference/search/suggesters.asciidoc | 2 +- docs/reference/search/suggesters/phrase-suggest.asciidoc | 4 ++-- docs/reference/search/suggesters/term-suggest.asciidoc | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/search/request/highlighting.asciidoc b/docs/reference/search/request/highlighting.asciidoc index 00de5bc5e75..11a233d973c 100644 --- a/docs/reference/search/request/highlighting.asciidoc +++ b/docs/reference/search/request/highlighting.asciidoc @@ -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 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 -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] =================================================================== diff --git a/docs/reference/search/request/named-queries-and-filters.asciidoc b/docs/reference/search/request/named-queries-and-filters.asciidoc index c28baec7158..d088f8af3ca 100644 --- a/docs/reference/search/request/named-queries-and-filters.asciidoc +++ b/docs/reference/search/request/named-queries-and-filters.asciidoc @@ -53,5 +53,5 @@ query (just so there will be a place to set a name for it), for example: ==== 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`. diff --git a/docs/reference/search/suggesters.asciidoc b/docs/reference/search/suggesters.asciidoc index 92997249db6..3273b7015b5 100644 --- a/docs/reference/search/suggesters.asciidoc +++ b/docs/reference/search/suggesters.asciidoc @@ -136,7 +136,7 @@ suggestion specific option. The suggest text specified on suggestion level override the suggest text on the global level. [float] -=== Other suggest example. +=== Other suggest example In the below example we request suggestions for the following suggest text: `devloping distibutd saerch engies` on the `title` field with a diff --git a/docs/reference/search/suggesters/phrase-suggest.asciidoc b/docs/reference/search/suggesters/phrase-suggest.asciidoc index 8b763fb9578..bea4262537e 100644 --- a/docs/reference/search/suggesters/phrase-suggest.asciidoc +++ b/docs/reference/search/suggesters/phrase-suggest.asciidoc @@ -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 `phrase` suggester adds additional logic on top of the `term` suggester to select entire corrected phrases instead of individual tokens weighted -based on `ngram-langugage` models. In practice it this suggester will be -able to make better decision about which tokens to pick based on +based on `ngram-langugage` models. In practice this suggester will be +able to make better decisions about which tokens to pick based on co-occurence and frequencies. ==== API Example diff --git a/docs/reference/search/suggesters/term-suggest.asciidoc b/docs/reference/search/suggesters/term-suggest.asciidoc index f6331c1ffc9..08639d7f9c9 100644 --- a/docs/reference/search/suggesters/term-suggest.asciidoc +++ b/docs/reference/search/suggesters/term-suggest.asciidoc @@ -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 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. ** `frequency`: Sort by document frequency first, then similarity score and then the term itself.