Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

Commit 27f2916

Browse files
committed
active voice
1 parent 6c93032 commit 27f2916

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

source/faq.txt

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,11 @@ Can I perform reads or writes to my destination cluster while ``mongosync`` is s
2828

2929
``mongosync`` combines and reorders writes from the source to destination during
3030
synchronization, and temporarily modifies various collection characteristics.
31-
As a result, the destination is not guaranteed to match the source, including a
32-
stale version of the source, at any point in time when the sync is running. To
33-
safely accept traffic to the destination cluster, wait for the migration to
34-
:ref:`c2c-api-commit`. To learn more, see :ref:`mongosync-considerations`.
31+
As a result, ``mongosync`` can't guarantee that the destination matches the
32+
source, including a stale version of the source, at any point in time when the
33+
sync is running. To safely accept traffic to the destination cluster, wait for
34+
the migration to :ref:`c2c-api-commit`. To learn more, see
35+
:ref:`mongosync-considerations`.
3536

3637
Performing writes to your destination cluster during synchronization results in
3738
undefined behavior. ``mongosync`` blocks writes on the destination cluster by

0 commit comments

Comments
 (0)