Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Fix typos in docs #88226

Merged
merged 1 commit into from
Jul 5, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -736,7 +736,7 @@ GET /_search

NOTE: The `after_key` is *usually* the key to the last bucket returned in
the response, but that isn't guaranteed. Always use the returned `after_key` instead
of derriving it from the buckets.
of deriving it from the buckets.

==== Early termination

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,4 +32,4 @@ mounted indices>> exclusively.
are nodes with the `data_warm` role. If there are no nodes in the warm tier,
but there are nodes with the `data_hot` role, the index is allocated to
the hot tier.
Used in conjuction with <<data-tier-allocation,data tiers>>.
Used in conjunction with <<data-tier-allocation,data tiers>>.
2 changes: 1 addition & 1 deletion docs/reference/sql/concepts.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ In practice this means that while in SQL one can potentially have multiple catal

|`cluster`
|`cluster` (federated)
|Traditionally in SQL, _cluster_ refers to a single RDMBS instance which contains a number of ++catalog++s or ++database++s (see above). The same word can be reused inside {es} as well however its semantic clarified a bit.
|Traditionally in SQL, _cluster_ refers to a single RDBMS instance which contains a number of ++catalog++s or ++database++s (see above). The same word can be reused inside {es} as well however its semantic clarified a bit.

While RDBMS tend to have only one running instance, on a single machine (_not_ distributed), {es} goes the opposite way and by default, is distributed and multi-instance.

Expand Down
4 changes: 2 additions & 2 deletions docs/reference/sql/endpoints/odbc/configuration.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -290,7 +290,7 @@ Should the driver follow HTTP redirects of the requests to the server?
+
* Use local timezone
+
This setting controlls the timezone of:
This setting controls the timezone of:
+
** the context in which the query will execute (especially relevant for functions dealing with timestamp components);

Expand All @@ -302,7 +302,7 @@ timezone.
* Auto-escape PVAs
+
The pattern-value arguments make use of `_` and `%` as special characters to
build patern matching values. Some applications however use these chars as
build pattern matching values. Some applications however use these chars as
regular ones, which can lead to {es-sql} returning more data than the app
intended. With the auto escaping, the driver will inspect the arguments and
will escape these special characters if not already done by the application.
Expand Down