Skip to content

Commit 3e98069

Browse files
committed
followup to #37284 with additional feedback
1 parent 28069db commit 3e98069

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/reference/docs/concurrency-control.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ operation performed to a document is assigned a sequence number by the primary
1414
shard that coordinates that change. The sequence number is increased with each
1515
operation and thus newer operations are guaranteed to have a higher sequence
1616
number than older operations. Elasticsearch can then use the sequence number of
17-
operations to make sure they never override a newer document version is never
18-
overridden by a change that has a smaller sequence number assigned to it.
17+
operations to make sure a newer document version is never overridden by
18+
a change that has a smaller sequence number assigned to it.
1919

2020
For example, the following indexing command will create a document and assign it
2121
an initial sequence number and primary term:

docs/reference/docs/index_.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -341,13 +341,13 @@ then the operation is executed without any version checks.
341341

342342
The above will succeed since the the supplied version of 2 is higher than
343343
the current document version of 1. If the document was already updated
344-
and it's version was set to 2 or higher, the indexing command will fail
344+
and its version was set to 2 or higher, the indexing command will fail
345345
and result in a conflict (409 http status code).
346346

347347
WARNING: External versioning supports the value 0 as a valid version number.
348348
This allows the version to be in sync with an external versioning system
349349
where version numbers start from zero instead of one. It has the side effect
350-
that documents with version number equal to zero cannot neither be updated
350+
that documents with version number equal to zero can neither be updated
351351
using the <<docs-update-by-query,Update-By-Query API>> nor be deleted
352352
using the <<docs-delete-by-query,Delete By Query API>> as long as their
353353
version number is equal to zero.
@@ -357,7 +357,7 @@ of async indexing operations executed as a result of changes to a source
357357
database, as long as version numbers from the source database are used.
358358
Even the simple case of updating the Elasticsearch index using data from
359359
a database is simplified if external versioning is used, as only the
360-
latest version will be used if the index operations are out of order for
360+
latest version will be used if the index operations arrive out of order for
361361
whatever reason.
362362

363363
[float]

0 commit comments

Comments
 (0)