Browse Source

[DOCS] fix a couple of typos (#33356)

Nikolay Vasiliev 7 years ago
parent
commit
d9f394b099

+ 1 - 1
docs/reference/rollup/rollup-search-limitations.asciidoc

@@ -107,7 +107,7 @@ It's recommended to just configure a single job with the smallest granularity th
 as needed.
 
 That said, if multiple jobs are present in a single rollup index with varying intervals, the search endpoint will identify and use the job(s)
-with the largest interval to satisfy the search reques.
+with the largest interval to satisfy the search request.
 
 [float]
 === Limited querying components

+ 1 - 1
docs/reference/setup/setup-xclient.asciidoc

@@ -11,7 +11,7 @@ cluster where {xpack} is installed, then you must download and configure the
 
 . Add the {xpack} transport JAR file to your *CLASSPATH*. You can download the {xpack}
 distribution and extract the JAR file manually or you can get it from the
-https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/{version}/x-pack-transport-{version}.jar[Elasticsearc Maven repository].
+https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/{version}/x-pack-transport-{version}.jar[Elasticsearch Maven repository].
 As with any dependency, you will also need its transitive dependencies. Refer to the
 https://artifacts.elastic.co/maven/org/elasticsearch/client/x-pack-transport/{version}/x-pack-transport-{version}.pom[X-Pack POM file
 for your version] when downloading for offline usage.

+ 2 - 2
docs/reference/upgrade/set-paths-tip.asciidoc

@@ -2,7 +2,7 @@
 ================================================
 
 When you extract the zip or tarball packages, the `elasticsearch-n.n.n`
-directory contains the Elasticsearh `config`, `data`, `logs` and
+directory contains the Elasticsearch `config`, `data`, `logs` and
 `plugins` directories.
 
 We recommend moving these directories out of the Elasticsearch directory
@@ -15,4 +15,4 @@ The <<deb,Debian>> and <<rpm,RPM>> packages place these directories in the
 appropriate place for each operating system. In production, we recommend
 installing using the deb or rpm package.
 
-================================================
+================================================