2008-03-28 Ivan N. Zlatev <contact@i-nz.net>

[mono.git] / web / documentation

diff --git a/web/documentation b/web/documentation
index 4cb6d0d3c5fa0a2ac0391c71b69b7ecbde15441f..40085e851267d8d531235348427d9044e53fa07f 100644 (file)
--- a/web/documentation
+++ b/web/documentation
@@ -203,7 +203,7 @@
 </pre>
         
                Use this to create lists.  Lists contains &lt;item&gt;
-               elements
+               elements which have to contain &lt;term&gt; containers.
         
 <pre>
 &lt;list type="table"&gt; &lt;/lits&gt;
@@ -250,6 +250,11 @@
         please don't open the Microsoft docs and refer to them for each member
         you document.
 
+       The best way of documenting is to read our source code
+       implementation and explain in your own words what our implementation
+       does, and what the user can do with it.
+
         There's a lot of domain expertise among the class library contributors;
         let's put the same personal stamp on the class library documentation
-        that we have on the class libraries themselves.
\ No newline at end of file
+        that we have on the class libraries themselves.
+