Fix docs typos (#50365)

Fixes a few typos in the docs.

Signed-off-by: Xiang Dai 764524258@qq.com

docs/painless/painless-guide/painless-datetime.asciidoc

@@ -293,7 +293,7 @@ if (timestamp1 > timestamp2) {
 }
 ----
 +
-* Equality comparision of two complex datetimes
+* Equality comparison of two complex datetimes
 +
 [source,Painless]
 ----
@@ -307,7 +307,7 @@ if (zdt1.equals(zdt2)) {
 }
 ----
 +
-* Less than comparision of two complex datetimes
+* Less than comparison of two complex datetimes
 +
 [source,Painless]
 ----
@@ -321,7 +321,7 @@ if (zdt1.isBefore(zdt2)) {
 }
 ----
 +
-* Greater than comparision of two complex datetimes
+* Greater than comparison of two complex datetimes
 +
 [source,Painless]
 ----
@@ -611,7 +611,7 @@ per document, so each time the script is run a different `now` is returned. The
 second is scripts are often run in a distributed fashion without a way to
 appropriately synchronize `now`. Instead, pass in a user-defined parameter with
 either a string datetime or numeric datetime for `now`. A numeric datetime is
-preferred as there is no need to parse it for comparision.
+preferred as there is no need to parse it for comparison.
 
 ===== Datetime Now Examples
 

docs/plugins/discovery-ec2.asciidoc

@@ -290,7 +290,7 @@ available on AWS-based infrastructure from http://www.elastic.co/cloud.
 ===== Storage
 
 EC2 instances offer a number of different kinds of storage. Please be aware of
-the folowing when selecting the storage for your cluster:
+the following when selecting the storage for your cluster:
 
 * http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html[Instance
 Store] is recommended for {es} clusters as it offers excellent performance and

docs/plugins/mapper-annotated-text.asciidoc

@@ -137,7 +137,7 @@ GET my_index/_search
 inject the single token value `Beck` at the same position as `beck` in the token stream.
 <2> Note annotations can inject multiple tokens at the same position - here we inject both
 the very specific value `Jeff Beck` and the broader term `Guitarist`. This enables
-broader positional queries e.g. finding mentions of a `Guitarist` near to `strat`.
+broader positional queries e.g. finding mentions of a `Guitarist` near to `start`.
 <3> A benefit of searching with these carefully defined annotation tokens is that a query for 
 `Beck` will not match document 2 that contains the tokens `jeff`, `beck` and `Jeff Beck`
 

docs/reference/analysis/analyzers/lang-analyzer.asciidoc

@@ -388,7 +388,7 @@ PUT /catalan_example
         },
         "catalan_keywords": {
           "type":       "keyword_marker",
-          "keywords":   ["exemple"] <2>
+          "keywords":   ["example"] <2>
         },
         "catalan_stemmer": {
           "type":       "stemmer",
@@ -798,7 +798,7 @@ PUT /french_example
         },
         "french_keywords": {
           "type":       "keyword_marker",
-          "keywords":   ["Exemple"] <2>
+          "keywords":   ["Example"] <2>
         },
         "french_stemmer": {
           "type":       "stemmer",

docs/reference/docs/delete-by-query.asciidoc

@@ -74,7 +74,7 @@ and all failed requests are returned in the response. Any delete requests that
 completed successfully still stick, they are not rolled back. 
 
 You can opt to count version conflicts instead of halting and returning by 
-setting `conflicts` to `proceeed`. 
+setting `conflicts` to `proceed`. 
 
 ===== Refreshing shards
 

docs/reference/docs/get.asciidoc

@@ -206,7 +206,7 @@ The explicit routing, if set.
 '_source'::
 If `found` is `true`, contains the document data formatted in JSON.
 Excluded if the `_source` parameter is set to `false` or the `stored_fields`
-paramter is set to `true`.
+parameter is set to `true`.
 
 '_fields'::
 If the `stored_fields` parameter is set to `true` and `found` is

docs/reference/docs/update-by-query.asciidoc

@@ -59,7 +59,7 @@ When the versions match, the document is updated and the version number is incre
 If a document changes between the time that the snapshot is taken and 
 the update operation is processed, it results in a version conflict and the operation fails. 
 You can opt to count version conflicts instead of halting and returning by 
-setting `conflicts` to `proceeed`. 
+setting `conflicts` to `proceed`. 
 
 NOTE: Documents with a version equal to 0 cannot be updated using update by
 query because `internal` versioning does not support 0 as a valid

docs/reference/ilm/apis/slm-api.asciidoc

@@ -300,7 +300,7 @@ The API returns the following response:
 }
 --------------------------------------------------
 // TESTRESPONSE[s/"modified_date": "2019-04-23T01:30:00.000Z"/"modified_date": $body.daily-snapshots.modified_date/ s/"modified_date_millis": 1556048137314/"modified_date_millis": $body.daily-snapshots.modified_date_millis/ s/"next_execution": "2019-04-24T01:30:00.000Z"/"next_execution": $body.daily-snapshots.next_execution/ s/"next_execution_millis": 1556048160000/"next_execution_millis": $body.daily-snapshots.next_execution_millis/]
-<1> The version of the snapshot policy, only the latest verison is stored and incremented when the policy is updated
+<1> The version of the snapshot policy, only the latest version is stored and incremented when the policy is updated
 <2> The last time this policy was modified.
 <3> The next time this policy will be executed.
 

docs/reference/ilm/getting-started-slm.asciidoc

@@ -137,7 +137,7 @@ While snapshots taken by SLM policies can be viewed through the standard snapsho
 API, SLM also keeps track of policy successes and failures in ways that are a bit
 easier to use to make sure the policy is working.  Once a policy has executed at
 least once, when you view the policy using the <<slm-api-get,Get Policy API>>, 
-some metadata will be returned indicating whether the snapshot was sucessfully 
+some metadata will be returned indicating whether the snapshot was successfully 
 initiated or not.
 
 Instead of waiting for our policy to run, let's tell SLM to take a snapshot
@@ -219,7 +219,7 @@ field - it's included above only as an example. You should, however, see a
 `last_success` field and a snapshot name. If you do, you've successfully taken
 your first snapshot using SLM!
 
-While only the most recent sucess and failure are available through the Get Policy 
+While only the most recent success and failure are available through the Get Policy 
 API, all policy executions are recorded to a history index, which may be queried
 by searching the index pattern `.slm-history*`.
 

docs/reference/mapping/types/shape.asciidoc

@@ -61,7 +61,7 @@ and reject the whole document.
 Like `geo_shape`, the `shape` field type is indexed by decomposing geometries into
 a triangular mesh and indexing each triangle as a 7 dimension point in a BKD tree.
 The coordinates provided to the indexer are single precision floating point values so
-the field guarantess the same accuracy provided by the java virtual machine (typically
+the field guarantees the same accuracy provided by the java virtual machine (typically
 `1E-38`). For polygons/multi-polygons the performance of the tessellator primarily
 depends on the number of vertices that define the geometry.
 

docs/reference/query-dsl/exists-query.asciidoc

@@ -33,7 +33,7 @@ GET /_search
 `field`::
 (Required, string) Name of the field you wish to search.
 +
-While a field is deemed non-existant if the JSON value is `null` or `[]`, these
+While a field is deemed non-existent if the JSON value is `null` or `[]`, these
 values will indicate the field does exist:
 +
 * Empty strings, such as `""` or `"-"`

docs/reference/search/validate.asciidoc

@@ -53,7 +53,7 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
 
 `explain`::
   (Optional, boolean) If `true`, the response returns detailed information if an 
-  error has occured. Defautls to `false`.
+  error has occurred. Defaults to `false`.
 
 include::{docdir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
 

docs/reference/setup/install/deb.asciidoc

@@ -240,7 +240,7 @@ locations for a Debian-based system:
 
 | jdk
   | The bundled Java Development Kit used to run Elasticsearch. Can
-    be overriden by setting the `JAVA_HOME` environment variable
+    be overridden by setting the `JAVA_HOME` environment variable
     in `/etc/default/elasticsearch`.
   | /usr/share/elasticsearch/jdk
  d|

docs/reference/setup/install/rpm.asciidoc

@@ -233,7 +233,7 @@ locations for an RPM-based system:
 
 | jdk
   | The bundled Java Development Kit used to run Elasticsearch. Can
-    be overriden by setting the `JAVA_HOME` environment variable
+    be overridden by setting the `JAVA_HOME` environment variable
     in `/etc/sysconfig/elasticsearch`.
   | /usr/share/elasticsearch/jdk
  d|

docs/reference/sql/language/syntax/lexic/index.asciidoc

@@ -148,7 +148,7 @@ s|Description
 
 Most operators in {es-sql} have the same precedence and are left-associative. As this is done at parsing time, parenthesis need to be used to enforce a different precedence.
 
-The following table indicates the supported operators and their precendence (highest to lowest);
+The following table indicates the supported operators and their precedence (highest to lowest);
 
 [cols="^2m,^,^3"]
 
@@ -176,7 +176,7 @@ s|Description
 
 |+ -
 |left
-|addition, substraction
+|addition, subtraction
 
 |BETWEEN IN LIKE
 |