@@ -341,13 +341,13 @@ then the operation is executed without any version checks.
341341
342342The above will succeed since the the supplied version of 2 is higher than
343343the 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
345345and result in a conflict (409 http status code).
346346
347347WARNING: External versioning supports the value 0 as a valid version number.
348348This allows the version to be in sync with an external versioning system
349349where 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
351351using the <<docs-update-by-query,Update-By-Query API>> nor be deleted
352352using the <<docs-delete-by-query,Delete By Query API>> as long as their
353353version number is equal to zero.
@@ -357,7 +357,7 @@ of async indexing operations executed as a result of changes to a source
357357database, as long as version numbers from the source database are used.
358358Even the simple case of updating the Elasticsearch index using data from
359359a 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
361361whatever reason.
362362
363363[float]
0 commit comments