Documentation small corrections

doc/arch.doc

@@ -188,7 +188,7 @@ could extract information from the XML output. Possible tools could be:
 <h3>Debugging</h3>
 
 Since doxygen uses a lot of \c flex code it is important to understand
-how \c flex works (for this one should read the man page) 
+how \c flex works (for this one should read the \c man page) 
 and to understand what it is doing when \c flex is parsing some input. 
 Fortunately, when flex is used with the `-d` option it outputs what rules
 matched. This makes it quite easy to follow what is going on for a 
@@ -240,10 +240,10 @@ $now = time;
 utime $now, $now, $file
 \endverbatim
 Another way to get rules matching / debugging information
-from the flex code is setting LEX_FLAGS with cmake.
+from the \c flex code is setting LEX_FLAGS with \c make (`make LEX_FLAGS=-d`).
 
-Note that by running doxygen with `-d lex` you get information about which flex
-codefile is used.
+Note that by running doxygen with `-d lex` you get information about which 
+`flex codefile` is used.
 
 \htmlonly
 Return to the <a href="index.html">index</a>.

doc/grouping.doc

@@ -128,7 +128,7 @@ This is the \ref group_label "link" to this group.
 The priorities of grouping definitions are (from highest to lowest):
 \ref cmdingroup "\\ingroup", \ref cmddefgroup "\\defgroup",
 \ref cmdaddtogroup "\\addtogroup", \ref cmdweakgroup "\\weakgroup".
-The last command is exactly like \ref cmdaddtogroup "\\addtogroup"
+The \ref cmdweakgroup "\\weakgroup" command is exactly like \ref cmdaddtogroup "\\addtogroup"
 with a lower priority. It was added to allow "lazy" grouping
 definitions: you can use commands with a higher priority in your .h
 files to define the hierarchy and \ref cmdweakgroup "\\weakgroup"