Clarification regarding commits to public bk tree.

Changelog fixups.

Docs/manual.texi

@@ -6922,7 +6922,7 @@ system-specific section of this manual.
 
 @cindex development source tree
 @cindex BitKeeper tree
-@cindex cvs tree
+@cindex CVS tree
 
 @strong{Caution}: You should read this section only if you are interested
 in helping us test our new code. If you just want to get MySQL up
@@ -7023,6 +7023,15 @@ a description.
 @code{BitKeeper} has a nice help utility that you can access via
 @code{bk helptool}.
 
+@item
+Please note that any commits (@code{bk ci} or @code{bk citool}) will
+trigger the posting of a message with the changeset to our internals
+mailing list, as well as the usual openlogging.org submission with
+just the changeset comments.
+Generally, you wouldn't need to use commit (since the public tree will
+not allow @code{bk push}), but rather use the @code{bk diffs} method
+described previously.
+
 @end enumerate
 
 
@@ -50149,8 +50158,9 @@ each individual 4.0.x release.
 @item
 Fixed bug in query cache after temporary table creation.
 @item
-Added --count=N (-c) to mysqladmin, to be used with -i (--sleep). When used,
-the program will only make N iterations. Useful in scripts.
+Added @code{--count=N} (@code{-c}) to @code{mysqladmin}, to make the
+program do only N iterations. To be used with @code{--sleep} (@code{-i}).
+Useful in scripts.
 @item
 Fixed bug in multi-table @code{UPDATE}: when updating a table,
 @code{do_select()} became confused about reading records from a cache.