strike paragraph

Author: FGasper

README.md

@@ -261,8 +261,6 @@ In this case, '`failed_docs`' contains all the meta data mismatches, in this cas
 
 The migration-verifier periodically persists its change stream’s resume token so that, in the event of a catastrophic failure (e.g., memory exhaustion), when restarted the verifier will receive any change events that happened while the verifier was down.
 
-**CAVEAT:** This doesn’t work properly during partitionining. If the verifier ends prior to partitioning, you should restart the verification.
-
 # Performance
 
 The migration-verifier optimizes for the case where a migration’s initial sync is completed **and** change events are relatively infrequent. If you start verification before initial sync finishes, or if the source cluster is too busy, the verification may freeze.