README.md in flnews_post_proc-1.53 vs README.md in flnews_post_proc-1.54

@@ -5,16 +5,16 @@
 
 **IMPORTANT**  
 Please give priority to the documentation which is delivered with the gem  
 file, as the markdown syntax plays tricks, sometimes, and I may not be  
 quick enough to correct this file. This applies especially to the section   
-[_Configuration_](#CONFIGURATION), below.
+[_Configuration_](#CONFIGURATION), below.  
 
-The gem-file contains different formats of the man-page in English and French.
-See section [_Source Code_](Source-Code), below, for instructions to access
-these texts.  Or see the same files [on the
-Web](https://www.uplawski.eu/div/flnews/).
+The gem-file contains different formats of the man-page in English and French. 
+See section [_Source Code_](Source-Code), below, for instructions to access 
+these texts.  Or see the same files [on the  
+Web](https://www.uplawski.eu/div/flnews/). 
 
 SYNOPSIS
 =======================
 
 An article is piped-in to the post-processor. This is normally done  
@@ -154,9 +154,14 @@
 
 * Variables describing values originally set by flnews, which should be used or  
   replaced. The important elements are usually matched in a capture group.  
 
 * Variables defining the new or altered content.  
+
+*ATTENTION*: Most problems that occurred with recent versions of
+*flnews_post_proc* were caused by inadequate option values and very often ill
+chosen or mal formatted regular expressions. PSE double check your
+configuration, if the program does not seem to work normally.
 
 **FUP_NAME**   
 A Regular Expression, describing the string which contains the name of  
 previous poster who is the author of a quoted post.  This string is  
 recognized in the original article and may be used with the fitting element