diff --git a/snapraid.1 b/snapraid.1
index 4c667a96..c941e4f4 100644
--- a/snapraid.1
+++ b/snapraid.1
@@ -772,7 +772,7 @@ Scrubs the array, checking for silent or input/output errors in data
 and parity disks.
 .PP
 For each command invocation, the 12% of the array is checked, but
-nothing that it\'s more recent than 10 days.
+nothing that was already scrubbed in the last 10 days.
 This means that scrubbing once a week, every bit of data is checked
 at least one time every two months.
 .PP
@@ -780,9 +780,21 @@ You can use the \-p, \-\-percentage option to specify a different amount,
 and the \-o, \-\-older\-than option to specify a different age in days.
 You can have a full scrub with \[dq]\-p 100 \-o 0\[dq].
 .PP
-The just synched blocks are scrubbed first, then are scrubbed the blocks
-with the oldest scrub time.
-To get some stats of the scrub times, you can use the \[dq]status\[dq] command.
+When the selected amout doesn\'t allow a full scrub, the blocks
+priority is:
+* The blocks already marked as bad, to verify their status.
+* The new sycnched blocks never scrubbed, to verify if their
+.PP
+.RS 4
+parity data was written correctly.
+.RE
+.PD 0
+.IP \(bu
+All the reimainig blocks, but starting from the oldest ones
+ensuring an optimal check.
+.PD
+.PP
+To get the details of the scrub status use the \[dq]status\[dq] command.
 .PP
 For any silent or input/output error found the corresponding blocks
 are marked as bad in the \[dq]content\[dq] file.
@@ -791,8 +803,8 @@ After the fix, at the next scrub they will be rechecked, and if found
 corrected, the bad mark will be removed.
 To scrub only the bad blocks, you can use the \[dq]scrub \-p 0\[dq] command.
 .PP
-It\'s recommended to run \[dq]scrub\[dq] on a synced array, to avoid to have
-reported error caused by unsynced data. These errors are recognized
+It\'s recommended to run \[dq]scrub\[dq] only on a synced array, to avoid to
+have reported error caused by unsynced data. These errors are recognized
 as not being silent errors, and the blocks are not marked as bad,
 but such errors are reported in the output of the command.
 .PP
diff --git a/snapraid.d b/snapraid.d
index b517279b..0006a8ff 100644
--- a/snapraid.d
+++ b/snapraid.d
@@ -481,7 +481,7 @@ Commands
 	and parity disks.
 
 	For each command invocation, the 12% of the array is checked, but
-	nothing that it's more recent than 10 days.
+	nothing that was already scrubbed in the last 10 days.
 	This means that scrubbing once a week, every bit of data is checked
 	at least one time every two months.
 
@@ -489,9 +489,15 @@ Commands
 	and the -o, --older-than option to specify a different age in days.
 	You can have a full scrub with "-p 100 -o 0".
 
-	The just synched blocks never scrubbed, are scrubbed first, then are
-	scrubbed the blocks with the oldest scrub time.
-	To get some stats of the scrub times, you can use the "status" command.
+	When the selected amout doesn't allow a full scrub, the blocks
+	priority is:
+	* The blocks already marked as bad, to verify their status.
+	* The new sycnched blocks never scrubbed, to verify if their
+		parity data was written correctly.
+	* All the reimainig blocks, but starting from the oldest ones
+		ensuring an optimal check.
+
+	To get the details of the scrub status use the "status" command.
 
 	For any silent or input/output error found the corresponding blocks
 	are marked as bad in the "content" file.
diff --git a/snapraid.txt b/snapraid.txt
index 70045689..6dcfee1c 100644
--- a/snapraid.txt
+++ b/snapraid.txt
@@ -519,7 +519,7 @@ Scrubs the array, checking for silent or input/output errors in data
 and parity disks.
 
 For each command invocation, the 12% of the array is checked, but
-nothing that it's more recent than 10 days.
+nothing that was already scrubbed in the last 10 days.
 This means that scrubbing once a week, every bit of data is checked
 at least one time every two months.
 
@@ -527,9 +527,15 @@ You can use the -p, --percentage option to specify a different amount,
 and the -o, --older-than option to specify a different age in days.
 You can have a full scrub with "-p 100 -o 0".
 
-The just synched blocks are scrubbed first, then are scrubbed the blocks
-with the oldest scrub time.
-To get some stats of the scrub times, you can use the "status" command.
+When the selected amout doesn't allow a full scrub, the blocks
+priority is:
+* The blocks already marked as bad, to verify their status.
+* The new sycnched blocks never scrubbed, to verify if their
+    parity data was written correctly.
+* All the reimainig blocks, but starting from the oldest ones
+  ensuring an optimal check.
+
+To get the details of the scrub status use the "status" command.
 
 For any silent or input/output error found the corresponding blocks
 are marked as bad in the "content" file.
@@ -538,8 +544,8 @@ After the fix, at the next scrub they will be rechecked, and if found
 corrected, the bad mark will be removed.
 To scrub only the bad blocks, you can use the "scrub -p 0" command.
 
-It's recommended to run "scrub" on a synced array, to avoid to have
-reported error caused by unsynced data. These errors are recognized
+It's recommended to run "scrub" only on a synced array, to avoid to
+have reported error caused by unsynced data. These errors are recognized
 as not being silent errors, and the blocks are not marked as bad,
 but such errors are reported in the output of the command.