bk commit - mysqldoc tree (jon:1.2668)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2668 05/03/08 13:33:10 jon@stripped +1 -0
  Cluster: Configuration: Fixed typo.
  (Fixes Bug #8993.)

  Docs/manual.texi
    1.2491 05/03/08 13:33:07 jon@stripped +4 -4
    Cluster: Configuration: Fixed typo.
    (Fixes Bug #8993.)

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.2490/Docs/manual.texi	2005-03-08 10:34:58 +10:00
+++ 1.2491/Docs/manual.texi	2005-03-08 13:33:07 +10:00
@@ -10576,7 +10576,7 @@
 @itemize @bullet
 
 @item
-As of MySQL 5.0.3, trailing spaces no longer are removed from values stored 
+As of MySQL 5.0.3, trailing spaces no longer are removed from values stored
 in @code{VARCHAR} and @code{VARBINARY} columns.  The maximum length for
 @code{VARCHAR} or @code{VARBINARY} now is 65,535 characters or bytes,
 respectively.
@@ -71278,7 +71278,7 @@
 In order to avoid unnecessary allocation of resources, the server is configured
 by default with the NDB storage engine disabled. To enable NDB, you will need to
 modify the server's @file{my.cnf} configuration file, or start it with the
-@option{--ndb-cluster} option.
+@option{--ndbcluster} option.
 
 Since the MySQL server is a part of the cluster, it will also need to know how
 to access an MGM node in order to obtain the cluster configuration data. The
@@ -97970,11 +97970,11 @@
 @item
 Hostname matching didn't work if a netmask was specified for table-specific
 privileges. (Bug #3309)
-@item 
+@item
 Binary data stored in @code{BLOB} or @code{BINARY} columns would be
 erroneously dumped if @command{mysqldump} was invoked with
 @code{--hex-blob} and @code{--skip-extended-insert} arguments. This
-happened if data contained characters larger then 0x7F (Bug #8830). 
+happened if data contained characters larger then 0x7F (Bug #8830).
 @item
 Corruption of @code{MyISAM} table indexes could occur with @code{TRUNCATE
 TABLE} if the table had already been opened. For example, this was possible