X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Mainpage.dox;h=98afe2b575cf5940f42d45af74c74b78a5338424;hb=a3d3979b7daaf22ea63ca356edbfa8047dff7b78;hp=96779a96eaee8a734b365369ce153820884a48fb;hpb=04dd5d565dc0a5888f8d26bbcb12e9d325d6a4e5;p=senf.git

diff --git a/Mainpage.dox b/Mainpage.dox
index 96779a9..98afe2b 100644
--- a/Mainpage.dox
+++ b/Mainpage.dox
@@ -44,7 +44,7 @@
     want to contribute, read the docs and \e please adhere to the \ref conventions.
 
     \see \ref usage\n
-         \ref example
+         <a href="../../Examples/doc/html/index.html">Examples</a>
 */
 
 /** \page usage Using the SENF framework
@@ -53,7 +53,7 @@
     oriented and template based. For compatibility reasons, the libraries are therefore built
     together with every project making use of the framework.
 
-    When starting a new Projekt based on the SENF framework, it is advisable, to make use of the
+    When starting a new project based on the SENF framework, it is advisable, to make use of the
     SENFSCons build environment and use SVN to manage the code repository. This is the
     configuration, described in this documentation.
 
@@ -64,7 +64,7 @@
 
     \section Preliminaries
 
-    Before starting the devlopment, make sure to fulfill the following requirements:
+    Before starting the development, make sure to fulfill the following requirements:
 
     \li GNU g++, version at least 3.4
     \li The Boost libraries (http://www.boost.org)
@@ -76,6 +76,7 @@
     \li The \c dia diagram editor (http://www.gnome.org/projects/dia/)
     \li HTML \c tidy (http://tidy.sourceforge.net/)
     \li The \c xsltproc XSLT processor (http://xmlsoft.org/XSLT/xsltproc2.html)
+    \li The \c graphviz library (http://www.graphviz.org)
 
 
     The library is only tested with gcc-3.4 and 4.0 on Linux. On other POSIX platforms with a BSD
@@ -145,7 +146,7 @@
 
     \section libPackets libPackets: Network packet manipulation
 
-    This libarary provides a very flexible infrastructure to parse, create and otherwise manipulate
+    This library provides a very flexible infrastructure to parse, create and otherwise manipulate
     packetized network data. Included is a library of several protocol parsers covering the basic
     IPv4 and IPv6 network protocols down to the Ethernet layer.
 
@@ -207,7 +208,7 @@
 
     You now have to decide, which modules you want to use. Every module resides in it's own
     subdirectory in the SENF repository. Instead of directly checking out the code, we will use \c
-    svn:externals. This will instruct \c svn to auutomatically check out the needed directories from
+    svn:externals. This will instruct \c svn to automatically check out the needed directories from
     the BerliOS SENF repository. Change to the 'Foo' directory and type
 
     <pre>
@@ -216,7 +217,7 @@
 
     The default editor (probably VI) will be started with the current value of the svn:externals
     property (which will probably be empty). Now add all the modules you want plus \c senfscons and
-    possibly \c doclib (if you want to build the documentation). You will almost certainly neeed the
+    possibly \c doclib (if you want to build the documentation). You will almost certainly need the
     \c Utils module, since all other modules depend on it.
 
     For example, if you want to use the \c Scheduler and \c Socket module, the file will look like
@@ -240,7 +241,7 @@
 
     To set up the build environment, copy the <tt>senfscons/SConstruct.template</tt> to
     <tt>SConstruct</tt> in the project root. The default setup of this file is to build all
-    subdirectories (using the \c SConscript files of the subdirectories). You can add additonal
+    subdirectories (using the \c SConscript files of the subdirectories). You can add additional
     global targets and configuration parameters here.
 
     If you want to use a non-default compiler or the boost library is not installed in the system
@@ -264,7 +265,7 @@
     $ scons
     </pre>
 
-    If you have not changed the \c SConstruct file, this will build all modules you have importet
+    If you have not changed the \c SConstruct file, this will build all modules you have imported
     into your project. To build and execute the unit tests, use
 
     <pre>
@@ -278,9 +279,9 @@
     </pre>
 
     \see <a href="../../senfscons/doc/html/index.html">SENFSCons reference</a> \n
-         <a class="ext" href="http://www.scons.org/documentation.php">SCons documentation</a> \n
-         <a class="ext" href="http://svnbook.red-bean.com">Subversion online book</a> \n
-         <a class="ext" href="http://subversion.tigris.org">Subversion Homepage</a>
+         <a href="http://www.scons.org/documentation.php">SCons documentation</a> \n
+         <a href="http://svnbook.red-bean.com">Subversion online book</a> \n
+         <a href="http://subversion.tigris.org">Subversion Homepage</a>
  */
 
 /** \page overview Introduction to the framework
@@ -323,14 +324,14 @@
 
     The simplest way to get started is: copy the Sniffer application and start to modify it.
 
-    \see \ref example \n
+    \see <a href="../../Examples/doc/html/index.html">Examples</a> \n
          \ref components \n
          \ref svnsetup \n
          \ref build
 
     \section conventions Coding Conventions
     
-    Here we have laid down the coding conventions used throughout the SENF framework. Please adhere
+    Here we have laid down the coding conventions used throughout the SENF framework. Please ad here
     to these conventions when changing or adding code. If you use emacs, you can use the C++ IDE for
     emacs from http://g0dil.de which greatly simplifies following these conventions.
 
@@ -363,13 +364,13 @@
     <tr><td>\c .cci</td><td>C++ implementation of inline non-template functions and
     members</td></tr>
     
-    <tr><td>\c .cti</td><td>C++ implementation of inline template fuanctions and members</td></tr>
+    <tr><td>\c .cti</td><td>C++ implementation of inline template functions and members</td></tr>
 
     <tr><td>\c .mpp</td><td>Special include file used for external iteration by the
     Boost.Preprocessor library</td></tr> </table>
 
     \par Rationale:
-        There are two part's to this: First, separating the implementation of inlines and tempaltes
+        There are two part's to this: First, separating the implementation of inlines and templates
         out of the header file makes the header file much easier to read. This is important, since
         the header file will be used as a reference by the developers.
     \par