Clarify documentation about headers and libraries

diff --git a/doc/omk-manual.texinfo b/doc/omk-manual.texinfo
index 2faa14a269c2dec1c3569871e0e44884600d99ff..a4568635179a33e4b9c59915c94080359276851b 100644 (file)
--- a/doc/omk-manual.texinfo
+++ b/doc/omk-manual.texinfo
@@ -404,7 +404,7 @@ source @file{test.c}.
 @c FIXME: INCLUDES variable should not be set by rtlinux rules.
 
 @node Libraries, Multiple Directories, Compiling Programs, User's Manual
-@section Libraries
+@section Compiling Libraries
 
 
 With OMK, you can easily create statically or dynamically linked
@@ -448,12 +448,13 @@ by other programs.
 @subsection Header Files
 
 C and C++ libraries are not very useful without header files. OMK
-provides several variables that specify activities on header files.
+provides several variables that controls operations with header files.
 
-During compilation, header files are copied (or linked) from source
-directories to the @file{_compiled} tree
-(see @ref{include-pass}). Libraries and programs are then compiled against
-these copies.
+During compilation, header files are copied (or linked by symbolic
+links) from source directories to the @file{_compiled} tree (see
+@ref{include-pass}). Libraries and programs are then compiled against
+these copies. The following variables control which headers are copied
+and what is their destination file name.
 
 @anchor{include_HEADERS}
 @defvar include_HEADERS