From dcec89be90821487473113d1ec4101fe76284336 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Tue, 16 Apr 2024 10:52:56 -0700 Subject: [PATCH] Wording tweak (#656). --- docs/how-to/deal-with-very-large-backups.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/how-to/deal-with-very-large-backups.md b/docs/how-to/deal-with-very-large-backups.md index 9dea9dd..11a964f 100644 --- a/docs/how-to/deal-with-very-large-backups.md +++ b/docs/how-to/deal-with-very-large-backups.md @@ -149,12 +149,11 @@ fail.) The `data_sample_percentage` is the percentage of total files in the source directories to randomly sample and compare to their corresponding files in the latest backup archive. A higher value allows a more accurate check—and a -slower one. The comparison is performed by hashing the selected files in each -of the source paths and counting hashes that don't match the latest archive. -For instance, if you have 1,000 source files and your sample percentage is 1%, -then only 10 source files will be compared against the latest archive. These -sampled files are selected randomly each time, so in effect the spot check is -probabilistic. +slower one. The comparison is performed by hashing the selected source files +and counting hashes that don't match the latest archive. For instance, if you +have 1,000 source files and your sample percentage is 1%, then only 10 source +files will be compared against the latest archive. These sampled files are +selected randomly each time, so in effect the spot check is probabilistic. The `data_tolerance_percentage` is the percentage of total files in the source directories that can fail a spot check data comparison without failing the