From 39705aa236578bc7795b003db24789a07136998f Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Wed, 23 Apr 2014 21:05:14 +0200 Subject: [PATCH] [DOCS] rewrite -> fuzzy_rewrite in match query Fixed typo --- docs/reference/api-conventions.asciidoc | 2 +- docs/reference/query-dsl/queries/match-query.asciidoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/api-conventions.asciidoc b/docs/reference/api-conventions.asciidoc index 68b6526cfc1..c5d5df7c67a 100644 --- a/docs/reference/api-conventions.asciidoc +++ b/docs/reference/api-conventions.asciidoc @@ -185,7 +185,7 @@ sensitive which means that it depends on the type of the field being queried: ==== Numeric, date and IPv4 fields When querying numeric, date and IPv4 fields, `fuzziness` is interpreted as a -`+/- margin. It behaves like a <> where: +`+/-` margin. It behaves like a <> where: -fuzziness <= field value <= +fuzziness diff --git a/docs/reference/query-dsl/queries/match-query.asciidoc b/docs/reference/query-dsl/queries/match-query.asciidoc index d514768bd2a..44644a6c6a8 100644 --- a/docs/reference/query-dsl/queries/match-query.asciidoc +++ b/docs/reference/query-dsl/queries/match-query.asciidoc @@ -41,7 +41,7 @@ The `prefix_length` and `max_expansions` can be set in this case to control the fuzzy process. If the fuzzy option is set the query will use `constant_score_rewrite` as its <> the `rewrite` parameter allows to control how the query will get +method>> the `fuzzy_rewrite` parameter allows to control how the query will get rewritten. Here is an example when providing additional parameters (note the slight