@@ 39,25 39,25 @@ And generally everything else you can do
 
 ## adding a new language
 
-Adding new languages requires adding the relevant extensions to 
-the configure.ac and Makefile.am templates.
-
 For a language named LANGUAGE, create the directory templates/LANGUAGE
 including files that use _TEMPLATE_AUTHOR_ for the user name and
 _TEMPLATE_PROJ_ for the project name.
 
+Add needed extensions to the configure.ac and Makefile.am templates.
+You can build upon the generic files in templates/ (i.e. configure.ac)
+by creating *.head and *.tail files (i.e. configure.ac.tail,
+Makefile.am.head, Makefile.am.tail). These will then be used as begin
+(head) or end (tail) of the generated files.
+
+To replace files, create them in your LANGUAGE directory without .head
+or .tail suffix.
+
 Files and folders named _TEMPLATE_PROJ_* will be renamed to the
 project name. For example with a project named foo,
 `_TEMPLATE_PROJ_.py` will be renamed `foo.py`
 
-You can build upon the generic files in templates/ (i.e. configure.ac)
-by creating *.head and *.tail files (i.e. configure.ac.tail,
-Makefile.am.head, Makefile.am.tail). These will then be used as begin
-(head) or end (tail) of the generated files.
-
-For complex file structures, you might have to adjust conf.in to
-create the appropriate file structure. Look for `test x"${PROJLANG}"`
-to find the place to edit.
+For complex file structures, you might have to adjust conf.in.
+Look for `test x"${PROJLANG}"` to find the place to edit.
 
 For inspiration, look into template/bash since that includes some
 necessary tricks to access data paths with autotools under bash.