Docs: clarify SYNC_WARN_THRESHOLD as the self-service solution for recurring threshold warnings

Author: auanasgheps

README.md

@@ -35,7 +35,7 @@ Contributions are welcome!
 - After some preliminary checks, the script will execute `snapraid diff` to figure out if parity info is out of date, which means checking for changes since the last execution. During this step, the script will ensure drives are fine by reading parity and content files. 
 - One of the following will happen:     
     - If parity info is out of sync **and** the number of deleted or changed files exceed the threshold you have configured it **stops**. You may want to take a look to the output log.
-    - If parity info is out of sync **and** the number of deleted or changed files exceed the threshold, you can still **force a sync** after a number of warnings. It's useful If you often get a false alarm but you're confident enough. This is called "Sync with threshold warnings"
+    - If parity info is out of sync **and** the number of deleted or changed files exceed the threshold, you can still **force a sync** after a number of warnings. It's useful If you often get a false alarm but you're confident enough. This is called "Sync with threshold warnings" (configure with `SYNC_WARN_THRESHOLD` in `script-config.conf`).
     	- Instead of forcing a sync based on the number of deleted files, you may consider the `ADD_DEL_THRESHOLD` feature, by allowing a sync that would otherwise violate the delete threshold, if the ratio of added to deleted files is greater than the value set. 
     - If parity info is out of sync **but** the number of deleted or changed files did not exceed the threshold, it **executes a sync** to update the parity info.
 - When the parity info is in sync, either because nothing has changed or after a successfully sync, it runs the `snapraid scrub` command to validate the integrity of the data, both the files and the parity info. If sync was cancelled or other issues were found, scrub will not be run. 

script-config.conf

@@ -145,10 +145,12 @@ IGNORE_PATTERN=()
 ADD_DEL_THRESHOLD=0
 
 # Set number of warnings before forcing a sync, or force the sync every time
-# ignoring thresholds (Forced Sync). This option comes in handy when you cannot be 
-# bothered to manually start a sync job when DEL_THRESHOLD or UP_THRESHOLD are 
-# breached due to false alarm. 
-# Set to 0 to ALWAYS force a sync (Forced Sync, ignoring the thresholds above) 
+# ignoring thresholds (Forced Sync). This option comes in handy when you cannot be
+# bothered to manually start a sync job when DEL_THRESHOLD or UP_THRESHOLD are
+# breached due to false alarm.
+# Example: set to 3 to automatically force a sync after 3 consecutive threshold
+# warnings. This avoids having to SSH in and run --force-sync manually each time.
+# Set to 0 to ALWAYS force a sync (Forced Sync, ignoring the thresholds above)
 # Set to -1 to NEVER force a sync, the default behaviour (need to manual sync if
 # thresholds are breached).
 SYNC_WARN_THRESHOLD=-1