diff --git a/HISTORY b/HISTORY
index 0dda1d91..2d659f3e 100644
--- a/HISTORY
+++ b/HISTORY
@@ -7,6 +7,10 @@ SnapRAID HISTORY
    "sync" commands without it.
  * When saving the content file keep a copy of the previos one adding
    the ".backup" extension.
+ * Added a new -F, --force-full option that forces a full sync reusing
+   the hash data present in the content file.
+   This may be useful when using an old content file like the backup
+   one.
  * Auto exclude the lock file.
  * Don't prints the 'UUID set' message anymore because it's the normal
    condition for empty disks.
diff --git a/snapraid.1 b/snapraid.1
index ce8fd7af..18d34ef9 100644
--- a/snapraid.1
+++ b/snapraid.1
@@ -836,12 +836,11 @@ This option can be used only with the \[dq]sync\[dq] command.
 .B \-F, \-\-force\-full
 In the \[dq]sync\[dq] command, forces a full rebuild of the parity.
 This option can be used when you reverted back to an old content
-file, because you have lost the most recent one, and you still have
-the parity data.
+file, like the backup one, and you still have the parity data.
 Instead of recomputing the parity from scratch, this allows
 to reuse the hashes present in the content file to validate data,
-and to maintain data protection using the old content file and the
-parity data you have.
+and to maintain data protection during the \[dq]sync\[dq] process using
+the old content file and the parity data you have.
 This option can be used only with the \[dq]sync\[dq] command.
 .TP
 .B \-l, \-\-log FILE
diff --git a/snapraid.d b/snapraid.d
index 77ac2904..b9c4e804 100644
--- a/snapraid.d
+++ b/snapraid.d
@@ -599,12 +599,11 @@ Options
 	-F, --force-full
 		In the "sync" command, forces a full rebuild of the parity.
 		This option can be used when you reverted back to an old content
-		file, because you have lost the most recent one, and you still have
-		the parity data.
+		file, like the backup one, and you still have the parity data.
 		Instead of recomputing the parity from scratch, this allows
 		to reuse the hashes present in the content file to validate data,
-		and to maintain data protection using the old content file and the
-		parity data you have.
+		and to maintain data protection during the "sync" process using
+		the old content file and the parity data you have.
 		This option can be used only with the "sync" command.
 
 	-l, --log FILE
diff --git a/snapraid.txt b/snapraid.txt
index 4f846050..efddfe21 100644
--- a/snapraid.txt
+++ b/snapraid.txt
@@ -644,12 +644,11 @@ SnapRAID provides the following options:
     -F, --force-full
         In the "sync" command, forces a full rebuild of the parity.
         This option can be used when you reverted back to an old content
-        file, because you have lost the most recent one, and you still have
-        the parity data.
+        file, like the backup one, and you still have the parity data.
         Instead of recomputing the parity from scratch, this allows
         to reuse the hashes present in the content file to validate data,
-        and to maintain data protection using the old content file and the
-        parity data you have.
+        and to maintain data protection during the "sync" process using
+        the old content file and the parity data you have.
         This option can be used only with the "sync" command.
 
     -l, --log FILE