1.1 --- a/doc/graph_io.dox	Thu Jun 30 16:13:30 2005 +0000
     1.2 +++ b/doc/graph_io.dox	Fri Jul 01 10:33:27 2005 +0000
     1.3 @@ -206,12 +206,13 @@
     1.4  reader.run();
     1.5  \endcode
     1.6  
     1.7 -\section types The background of Reading and Writing
     1.8 -The \c GraphReader should know how to read a Value from the given map.
     1.9 +\section types Background of Reading and Writing
    1.10 +To read a map (on the nodes or edges)
    1.11 +the \c GraphReader should know how to read a Value from the given map.
    1.12  By the default implementation the input operator reads a value from
    1.13  the stream and the type of the readed value is the value type of the given map.
    1.14  When the reader should skip a value in the stream, because you do not
    1.15 -want to store it in map, the reader skips a character sequence without 
    1.16 +want to store it in a map, the reader skips a character sequence without 
    1.17  whitespace. 
    1.18  
    1.19  If you want to change the functionality of the reader, you can use
    1.20 @@ -229,7 +230,7 @@
    1.21  };
    1.22  \endcode
    1.23  
    1.24 -By example, the \c "strings" nodemap contains strings and you do not need
    1.25 +For example, the \c "strings" nodemap contains strings and you do not need
    1.26  the value of the string just the length. Then you can implement own Reader
    1.27  struct.
    1.28  
    1.29 @@ -253,7 +254,7 @@
    1.30  should provide an inner template class Reader for each type, and an 
    1.31  DefaultReader for skipping a value.
    1.32  
    1.33 -The specialization of the writing should be very similar to the reading.
    1.34 +The specialization of  writing should be very similar to that of reading.
    1.35  
    1.36  \author Balazs Dezso
    1.37  */