X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Scheduler%2FConsole%2FMainpage.dox;h=3a378e2ab6192345fabde57eb0411a2df35ed02e;hb=f52075dad8b8291570fa2c61ef9b5ec0a04d1e5e;hp=1314b5d537e4fc195e1a51b2a5e22e9d4500ef26;hpb=e2d104a5f998f474c3f0afcc3a5dc04f620c49c7;p=senf.git

diff --git a/Scheduler/Console/Mainpage.dox b/Scheduler/Console/Mainpage.dox
index 1314b5d..3a378e2 100644
--- a/Scheduler/Console/Mainpage.dox
+++ b/Scheduler/Console/Mainpage.dox
@@ -119,26 +119,25 @@
 
 
     \section intro_usage Using the Console: Configuration files, Network console
+    \seechapter \ref console_access
 
     There are several ways to access the node tree:
     \li By parsing configuration files
     \li By parsing command line parameters
     \li By providing interactive or non-interactive network console access
 
-    \see console_access
-
 
     \section intro_nodes The node tree
+    \seechapter \ref node_tree
 
     The basic idea is, that the console/config library manages a directory structure of parameters
     and auxiliary commands. Parameters are just commands which set a parameter value so everything
     is either a directory entry (senf::console::DirectoryNode) or a command
     (senf::console::CommandNode).
     
-    \see \ref node_tree
-
 
     \section intro_commands Implementing console/config commands
+    \seechapter \ref console_commands
 
     The console/config language does not define, how arguments are passed to the commands, it just
     tokenizes the input and passes the tokens to the commands which then handle the
@@ -150,8 +149,6 @@
     which will be called with an already parsed integer value (or throw a
     senf::console::SyntaxErrorException if the conversion fails). This will be the most often used
     command.
-
-    \see \ref console_commands
  */
 
 /** \defgroup console_access Accessing the Console/Config tree