Rword

Author: DaveCTurner

deploy-manage/tools/snapshot-and-restore/s3-repository.md

@@ -381,7 +381,7 @@ Instances residing in a public subnet in an AWS VPC will connect to S3 via the V
 
 AWS S3 supports [replication of objects](https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html), both within a single region and across regions. However, this replication is not compatible with {{es}} snapshots.
 
-The objects that {{es}} writes to the repository refer to other objects in the repository. {{es}} writes objects in a very specific order to ensure that each object only refers to objects which already exist. Likewise, {{es}} only deletes an object from the repository after it becomes unreferenced by all other objects. AWS S3 replication will apply operations to the replica repository in a different order from the order in which {{es}} applies them to the primary repository. This will mean that some objects in replica repositories refer to objects that do not exist. This is an invalid state. It may not be possible to recover any data from a repository in such a state.
+The objects that {{es}} writes to the repository refer to other objects in the repository. {{es}} writes objects in a very specific order to ensure that each object only refers to objects which already exist. Likewise, {{es}} only deletes an object from the repository after it becomes unreferenced by all other objects. AWS S3 replication will apply operations to the replica repository in a different order from the order in which {{es}} applies them to the primary repository. This will mean that some objects in replica repositories may refer to other objects which do not exist. This is an invalid state. It may not be possible to recover any data from a repository in such a state.
 
 To replicate a repository's contents elsewhere, follow the [repository backup](/deploy-manage/tools/snapshot-and-restore/self-managed.md#snapshots-repository-backup) process.