Reworked a little bit after communication with Dani.

MAINTENANCE

@@ -108,6 +108,8 @@ Step 0)
   (the latter link seems to be a bit funky, may better use the CVS home page
   as entry point.)
 
+  There are a couple of front-end for CVS, e.g. an Emacs mode and many others.
+
 Step 0a)
   Make sure the stuff you are checkingin at least builds without errors.
 
@@ -118,21 +120,18 @@ Step 1)
 
 Step 2)
   cvs commit
-  BIG FAT WARNING: this commits _all_ changed files. It is probably bette
-  to commit on a file-per-file basis.
+  NOTE: this commits _all_ changed files. It is probably bette
+  to commit on a file-per-file basis:
+
+  cvs commit FILE1 .... FILEN
+  with a selected collection of file you really want to commit.
 
   ALSO: it is required that all commits are properly documented. The comments
   must be written in a way that other people can understand them.
 
-  There are a couple of front-end for CVS, e.g. an Emacs mode, a TCL interface,
-  and even when using CVS from the command-line, it is not necessary to commit
-  everything at once. So maybe better do:
 
-Step 2-preferred)
-  cvs commit FILE1 .... FILEN
-  with a selected collection of file you really want to commit.
+Another possibility (avoiding Step 1) from above) is the following:
 
-Step (1 and 2-preferred)-alternative)
   Check out the "cvs.sh" script:
 
   cvs co admin-utils/cvs.sh