diff --git a/How-to-fix-the-error-invalid-or-negative-modification-date.md b/How-to-fix-the-error-invalid-or-negative-modification-date.md
index 7235f2b..e370404 100644
--- a/How-to-fix-the-error-invalid-or-negative-modification-date.md
+++ b/How-to-fix-the-error-invalid-or-negative-modification-date.md
@@ -9,7 +9,7 @@ The bug was introduced in the **Desktop client 3.4.0**. Currently, all known iss
 
 
 ### ⚠️ Before you proceed
-  1. Note that recovering the exact modification time requires restoring backups which may be impractical if the files have been modified already.
+  1. Note that recovering the exact modification time requires restoring backups which may be impractical if the files have been modified already. These scripts therefor only fix the lack of a valid date and time (which breaks syncing) by setting a fixed, valid date and time. Syncing will happen again, but the original, correct date and time are lost. In most situations, this is sufficient.
   2. You do not need to put the server in maintenance mode.
   3. You do not need to make a backup of your database, however backups are always recommended as a regular practice.
   4. Make sure to be running the [latest desktop client](https://github.com/nextcloud/desktop/releases).