- minor fixups (no more warnings)

 - the preferred mailing list is internals@ not dev-public@
   (this is a public document)
 - Rather use the 4.1 tree for new development (4.0 is frozen)


BitKeeper/etc/ignore:
  Added Docs/internals.html Docs/internals.pdf Docs/internals.txt Docs/internals_toc.html to the ignore list

1 files changed, 6 insertions, 6 deletions

diff --git a/Docs/internals.texi b/Docs/internals.texi
index 0fa6122865b..a54f5098e5d 100644
--- a/Docs/internals.texi
+++ b/Docs/internals.texi
@@ -76,12 +76,11 @@ This is a manual about @strong{MySQL} internals.
 We use @uref{http://www.bitkeeper.com/, BitKeeper} for source management.
 
 @item
-You should use the @strong{MySQL} 4.0 source for all developments.
+You should use the @strong{MySQL} 4.1 source for all developments.
 
 @item
 If you have any questions about the @strong{MySQL} source, you can post these
-to @email{dev-public@@mysql.com} and we will answer them.  Please
-remember to not use this internal email list in public!
+to @email{internals@@mysql.com} and we will answer them.
 
 @item
 Try to write code in a lot of black boxes that can be reused or use at
@@ -2136,8 +2135,9 @@ record and the next one. The overflow pointer is the location of the rest of
 the record if there are multiple parts.
 @*
 
-For example, here is a dynamic row:@*
-@example(
+For example, here is a dynamic row:
+@*
+@example
 03, 00             start of header
 04                 actual length
 0c                 unused length
@@ -2171,7 +2171,7 @@ format), and /myisam/mi_packrec.c (for packed format).
 
 Note: Internally, MySQL uses a format much like the fixed format 
 which it uses for disk storage. The main differences are:
-@enumerate @bullet
+@enumerate
 @item
 BLOBs have a length and a memory pointer rather than being stored inline.
 @item