Skip to content

Commit ff1039e

Browse files
dmeissdanielmitterdorfer
authored andcommitted
Edits to text in Multi Get API doc (#39082)
1 parent efbde5d commit ff1039e

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/reference/docs/multi-get.asciidoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[[docs-multi-get]]
22
== Multi Get API
33

4-
Multi GET API allows to get multiple documents based on an index, type
4+
Multi Get API allows to get multiple documents based on an index, type,
55
(optional) and id (and possibly routing). The response includes a `docs` array
66
with all the fetched documents in order corresponding to the original multi-get
77
request (if there was a failure for a specific get, an object containing this
@@ -89,7 +89,7 @@ GET /test/_doc/_mget
8989
By default, the `_source` field will be returned for every document (if stored).
9090
Similar to the <<get-source-filtering,get>> API, you can retrieve only parts of
9191
the `_source` (or not at all) by using the `_source` parameter. You can also use
92-
the url parameters `_source`,`_source_includes` & `_source_excludes` to specify defaults,
92+
the url parameters `_source`, `_source_includes`, and `_source_excludes` to specify defaults,
9393
which will be used when there are no per-document instructions.
9494

9595
For example:
@@ -181,7 +181,7 @@ GET /test/_doc/_mget?stored_fields=field1,field2
181181
[[mget-routing]]
182182
=== Routing
183183

184-
You can also specify routing value as a parameter:
184+
You can also specify a routing value as a parameter:
185185

186186
[source,js]
187187
--------------------------------------------------
@@ -204,11 +204,11 @@ GET /_mget?routing=key1
204204
--------------------------------------------------
205205
// CONSOLE
206206

207-
In this example, document `test/_doc/2` will be fetch from shard corresponding to routing key `key1` but
208-
document `test/_doc/1` will be fetch from shard corresponding to routing key `key2`.
207+
In this example, document `test/_doc/2` will be fetched from the shard corresponding to routing key `key1` but
208+
document `test/_doc/1` will be fetched from the shard corresponding to routing key `key2`.
209209

210210
[float]
211211
[[mget-security]]
212212
=== Security
213213

214-
See <<url-access-control>>
214+
See <<url-access-control>>.

0 commit comments

Comments
 (0)