X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fdocumentation;h=40085e851267d8d531235348427d9044e53fa07f;hb=bba3fd5d13cead49cb0b33e6f0d36d3543c578cd;hp=56721cd777761e57a1e750adcdbd56e27dbc113d;hpb=a405284d0e5aec16214808620549d79f4bf5302b;p=mono.git

diff --git a/web/documentation b/web/documentation
index 56721cd7777..40085e85126 100644
--- a/web/documentation
+++ b/web/documentation
@@ -25,7 +25,11 @@
 	 	  libraries as well as the class libraries produced by
 		  the project).
 
-		* Tutorials on Mono and the specifics of running it. 
+		* Tutorials on Mono and the specifics of running it
+		  (The <a href="http://www.monohispano.org">Mono
+		  Hispano</a> team has produced lots of <a
+		  href="http://www.monohispano.org/tutoriales.php">tutorials
+		  in spanish</a>
 
 		* A guide to Mono as compared to the Microsoft.NET
 		  Framework SDK
@@ -199,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;
@@ -246,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.
+