Skip to content

Commit a01b1f3

Browse files
[DOCS] Fix missing punctuation in agg docs (#59822) (#59982)
Co-authored-by: Howard <[email protected]>
1 parent 815032f commit a01b1f3

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -274,7 +274,7 @@ Cell dimensions vary with latitude and so the table is for the worst-case scenar
274274

275275
Aggregating on <<geo-shape>> fields works just as it does for points, except that a single
276276
shape can be counted for in multiple tiles. A shape will contribute to the count of matching values
277-
if any part of its shape intersects with that tile. Below is an image that demonstrates this
277+
if any part of its shape intersects with that tile. Below is an image that demonstrates this:
278278

279279

280280
image:images/spatial/geoshape_grid.png[]

docs/reference/aggregations/bucket/geotilegrid-aggregation.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ POST /museums/_search?size=0
225225

226226
Aggregating on <<geo-shape>> fields works just as it does for points, except that a single
227227
shape can be counted for in multiple tiles. A shape will contribute to the count of matching values
228-
if any part of its shape intersects with that tile. Below is an image that demonstrates this
228+
if any part of its shape intersects with that tile. Below is an image that demonstrates this:
229229

230230

231231
image:images/spatial/geoshape_grid.png[]

docs/reference/aggregations/metrics/geobounds-aggregation.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,10 +49,10 @@ POST /museums/_search?size=0
4949
}
5050
--------------------------------------------------
5151

52-
<1> The `geo_bounds` aggregation specifies the field to use to obtain the bounds
53-
<2> `wrap_longitude` is an optional parameter which specifies whether the bounding box should be allowed to overlap the international date line. The default value is `true`
52+
<1> The `geo_bounds` aggregation specifies the field to use to obtain the bounds.
53+
<2> `wrap_longitude` is an optional parameter which specifies whether the bounding box should be allowed to overlap the international date line. The default value is `true`.
5454

55-
The above aggregation demonstrates how one would compute the bounding box of the location field for all documents with a business type of shop
55+
The above aggregation demonstrates how one would compute the bounding box of the location field for all documents with a business type of shop.
5656

5757
The response for the above aggregation:
5858

docs/reference/aggregations/metrics/geocentroid-aggregation.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ POST /museums/_search?size=0
4646

4747
<1> The `geo_centroid` aggregation specifies the field to use for computing the centroid. (NOTE: field must be a <<geo-point>> type)
4848

49-
The above aggregation demonstrates how one would compute the centroid of the location field for all documents with a crime type of burglary
49+
The above aggregation demonstrates how one would compute the centroid of the location field for all documents with a crime type of burglary.
5050

5151
The response for the above aggregation:
5252

0 commit comments

Comments
 (0)