-A few things to note about this particular format. The "<tt>-*- C++ -*-</tt>" string on the first line is there to tell Emacs that the source file is a C++ file, not a C file (Emacs assumes .h files are C files by default [Note that tag this is not neccesary in .cpp files]). The name of the file is also on the first line, along with a very short description of the purpose of the file. This is important when printing out code and flipping though lots of pages.<p>
+<p>A few things to note about this particular format. The "<tt>-*- C++
+-*-</tt>" string on the first line is there to tell Emacs that the source file
+is a C++ file, not a C file (Emacs assumes .h files are C files by default [Note
+that tag this is not necessary in .cpp files]). The name of the file is also on
+the first line, along with a very short description of the purpose of the file.
+This is important when printing out code and flipping though lots of pages.</p>
+
+<p>The main body of the description does not have to be very long in most cases.
+Here it's only two lines. If an algorithm is being implemented or something
+tricky is going on, a reference to the paper where it is published should be
+included, as well as any notes or "gotchas" in the code to watch out for.</p>
+
+</li>
+
+<li><h4>Class overviews</h4>
+
+<p>Classes are one fundemental part of a good object oriented design. As such,
+a class definition should have a comment block that explains what the class is
+used for... if it's not obvious. If it's so completely obvious your grandma
+could figure it out, it's probably safe to leave it out. Naming classes
+something sane goes a long ways towards avoiding writing documentation. :)</p>