From 90524d7ad258130605ff56d8760ce563bcfee769 Mon Sep 17 00:00:00 2001 From: Adrien Grand Date: Wed, 18 Sep 2013 12:33:49 +0200 Subject: [PATCH] Fix formatting of the documentation. Remaining '@'s have been replaced with '`'s. --- .../analysis/tokenfilters/stemmer-tokenfilter.asciidoc | 2 +- docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc | 2 +- docs/reference/mapping/types/core-types.asciidoc | 2 +- docs/reference/mapping/types/geo-shape-type.asciidoc | 2 +- .../query-dsl/queries/custom-filters-score-query.asciidoc | 2 +- docs/reference/search/uri-request.asciidoc | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc b/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc index 6e4afce987c..6526f378476 100644 --- a/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc +++ b/docs/reference/analysis/tokenfilters/stemmer-tokenfilter.asciidoc @@ -2,7 +2,7 @@ === Stemmer Token Filter A filter that stems words (similar to `snowball`, but with more -options). The `language`/@name@ parameter controls the stemmer with the +options). The `language`/`name` parameter controls the stemmer with the following available values: http://lucene.apache.org/core/4_3_0/analyzers-common/index.html?org%2Fapache%2Flucene%2Fanalysis%2Far%2FArabicStemmer.html[arabic], diff --git a/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc b/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc index 790335902fe..ef684df3220 100644 --- a/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc +++ b/docs/reference/analysis/tokenizers/edgengram-tokenizer.asciidoc @@ -64,7 +64,7 @@ of these classes. |`[]` (Keep all characters) [float] ==== `side` deprecated -There used to be a @side@ parameter up to `0.90.1` but it is now deprecated. In +There used to be a `side` parameter up to `0.90.1` but it is now deprecated. In order to emulate the behavior of `"side" : "BACK"` a <> should be used together with the <>. The diff --git a/docs/reference/mapping/types/core-types.asciidoc b/docs/reference/mapping/types/core-types.asciidoc index a49ee5dfa9d..6ceb7ab2d05 100644 --- a/docs/reference/mapping/types/core-types.asciidoc +++ b/docs/reference/mapping/types/core-types.asciidoc @@ -3,7 +3,7 @@ Each JSON field can be mapped to a specific core type. JSON itself already provides us with some typing, with its support for `string`, -`integer`/@long@, `float`/@double@, `boolean`, and `null`. +`integer`/`long`, `float`/`double`, `boolean`, and `null`. The following sample tweet JSON document will be used to explain the core types: diff --git a/docs/reference/mapping/types/geo-shape-type.asciidoc b/docs/reference/mapping/types/geo-shape-type.asciidoc index 2ceb425006e..5ec48f340b2 100644 --- a/docs/reference/mapping/types/geo-shape-type.asciidoc +++ b/docs/reference/mapping/types/geo-shape-type.asciidoc @@ -38,7 +38,7 @@ specifies the desired precision and Elasticsearch will calculate the best tree_levels value to honor this precision. The value should be a number followed by an optional distance unit. Valid distance units include: `in`, `inch`, `yd`, `yard`, `mi`, `miles`, `km`, `kilometers`, -`m`,@meters@ (default), `cm`,@centimeters@, `mm`, `millimeters`. +`m`,`meters` (default), `cm`,`centimeters`, `mm`, `millimeters`. |`tree_levels` |Maximum number of layers to be used by the PrefixTree. This can be used to control the precision of shape representations and diff --git a/docs/reference/query-dsl/queries/custom-filters-score-query.asciidoc b/docs/reference/query-dsl/queries/custom-filters-score-query.asciidoc index 8761e760905..d17ba4ec9f4 100644 --- a/docs/reference/query-dsl/queries/custom-filters-score-query.asciidoc +++ b/docs/reference/query-dsl/queries/custom-filters-score-query.asciidoc @@ -39,7 +39,7 @@ performance, and boosting / script is considerably simpler. A `score_mode` can be defined to control how multiple matching filters control the score. By default, it is set to `first` which means the first matching filter will control the score of the result. It can also -be set to `min`/@max@/@total@/@avg@/@multiply@ which will aggregate the +be set to `min`/`max`/`total`/`avg`/`multiply` which will aggregate the result from all matching filters based on the aggregation type. [float] diff --git a/docs/reference/search/uri-request.asciidoc b/docs/reference/search/uri-request.asciidoc index 1ad2e911d2b..51c108ea238 100644 --- a/docs/reference/search/uri-request.asciidoc +++ b/docs/reference/search/uri-request.asciidoc @@ -68,7 +68,7 @@ not), comma delimited. Defaults to the internal `_source` field. Not specifying any value will cause no fields to return. |`sort` |Sorting to perform. Can either be in the form of `fieldName`, or -`fieldName:asc`/@fieldName:desc@. The fieldName can either be an actual +`fieldName:asc`/`fieldName:desc`. The fieldName can either be an actual field within the document, or the special `_score` name to indicate sorting based on scores. There can be several `sort` parameters (order is important).