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

Fix grammar issues in some docs 

This commit fixes some grammar issues in various docs.

Closes #20751
Closes #20752
Closes #20754
Closes #20755
This commit is contained in:
Anatolii Stepaniuk 2016-10-05 15:54:32 +03:00 committed by Jason Tedor
parent 6da0f0dcc0
commit f895abcf40
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/mapping/types/geo-shape.asciidoc
View File

@ -175,7 +175,7 @@ this into a tree_levels setting of 26.
===== Performance considerations ===== Performance considerations
Elasticsearch uses the paths in the prefix tree as terms in the index Elasticsearch uses the paths in the prefix tree as terms in the index
and in queries. The higher the levels is (and thus the precision), the and in queries. The higher the level is (and thus the precision), the
more terms are generated. Of course, calculating the terms, keeping them in more terms are generated. Of course, calculating the terms, keeping them in
memory, and storing them on disk all have a price. Especially with higher memory, and storing them on disk all have a price. Especially with higher
tree levels, indices can become extremely large even with a modest tree levels, indices can become extremely large even with a modest

2
docs/reference/query-dsl/geo-bounding-box-query.asciidoc
View File

@ -92,7 +92,7 @@ Default is `memory`.
==== Accepted Formats ==== Accepted Formats
In much the same way the geo_point type can accept different In much the same way the geo_point type can accept different
representation of the geo point, the filter can accept it as well: representations of the geo point, the filter can accept it as well:
[float] [float]
===== Lat Lon As Properties ===== Lat Lon As Properties

2
docs/reference/query-dsl/geo-distance-query.asciidoc
View File

@ -69,7 +69,7 @@ GET /my_locations/location/_search
==== Accepted Formats ==== Accepted Formats
In much the same way the `geo_point` type can accept different In much the same way the `geo_point` type can accept different
representation of the geo point, the filter can accept it as well: representations of the geo point, the filter can accept it as well:
[float] [float]
===== Lat Lon As Properties ===== Lat Lon As Properties

2
docs/reference/query-dsl/joining-queries.asciidoc
View File

@ -7,7 +7,7 @@ which are designed to scale horizontally.
<<query-dsl-nested-query,`nested` query>>:: <<query-dsl-nested-query,`nested` query>>::
Documents may contains fields of type <<nested,`nested`>>. These Documents may contain fields of type <<nested,`nested`>>. These
fields are used to index arrays of objects, where each object can be queried fields are used to index arrays of objects, where each object can be queried
(with the `nested` query) as an independent document. (with the `nested` query) as an independent document.