From: tho Date: Fri, 2 Mar 2007 09:38:24 +0000 (+0000) Subject: typo fix X-Git-Url: http://g0dil.de/git?a=commitdiff_plain;h=feb1c2dc16c0b087adf9d4839bd6ea578e29e55a;p=senf.git typo fix git-svn-id: https://svn.berlios.de/svnroot/repos/senf/trunk@212 270642c3-0616-0410-b53a-bc976706d245 --- diff --git a/Mainpage.dox b/Mainpage.dox index 96779a9..6c0920e 100644 --- a/Mainpage.dox +++ b/Mainpage.dox @@ -330,7 +330,7 @@ \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. @@ -369,7 +369,7 @@ Boost.Preprocessor library \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