Fix grammar issues in some docs

This commit fixes some grammar issues in various docs.

Closes #20751
Closes #20752
Closes #20754
Closes #20755

docs/reference/mapping/types/geo-shape.asciidoc

@@ -175,7 +175,7 @@ this into a tree_levels setting of 26.
 ===== Performance considerations
 
 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
 memory, and storing them on disk all have a price. Especially with higher
 tree levels, indices can become extremely large even with a modest

docs/reference/query-dsl/geo-bounding-box-query.asciidoc

@@ -92,7 +92,7 @@ Default is `memory`.
 ==== Accepted Formats
 
 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]
 ===== Lat Lon As Properties

docs/reference/query-dsl/geo-distance-query.asciidoc

@@ -69,7 +69,7 @@ GET /my_locations/location/_search
 ==== Accepted Formats
 
 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]
 ===== Lat Lon As Properties

docs/reference/query-dsl/joining-queries.asciidoc

@@ -7,7 +7,7 @@ which are designed to scale horizontally.
 
 <<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
 (with the `nested` query) as an independent document.