X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/99534debc8e4b2daa187638fe3e3d107c72c085d..8958fae362683257f8202b7f56b151b9c5ce5103:/rsync.yo

diff --git a/rsync.yo b/rsync.yo
index 1b2ab0b5..770832df 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -480,9 +480,10 @@ both sides of the connection occurs in addition to the automatic checksum
 verifications that occur during and after a file's transfer, this option
 can be quite slow.
 
-Note that rsync always uses a whole-file checksum to verify that each
-transferred file was reconstructed correctly, irrespective of this or
-any other option's setting.
+Note that rsync always verifies that each em(transferred) file was
+correctly reconstructed on the receiving side using a whole-file checksum,
+but that after-transfer check has nothing to do with this option's
+before-transfer "Does the file need to be updated?" check.
 
 dit(bf(-a, --archive)) This is equivalent to bf(-rlptgoD). It is a quick
 way of saying you want recursion and want to preserve almost