Bug #1018 documentation buglets
Submitted: 9 Aug 2003 15:02 Modified: 10 Aug 2003 19:18
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:4.0.14 OS:Linux (GNU/Linux)
Assigned to: Arjen Lentz CPU Architecture:Any
Triage: D4 (Minor)

[9 Aug 2003 15:02] [ name withheld ]
Description:
In reading through the mysql manual, I found a number of minor bugs, which I thought I'd report for your consideration.  (The manual in general is wonderful, thank you so much.)

    Before MySQL Server Version 3.23, all numeric types where treated
where -> were

    The second number (`21') is the release level. Normally there are two to
    choose from. One is the release/stable branch (currently `23') and the
    other is the development branch (currently `4.0').

No longer current info.

    Verify that you can restart the server.
    ...
    shell> BINDIR/safe_mysqld --log &
Do you really want to recommend --log in this case?  It seems as if you
are recommending it for normal use.  I'm a new mysql user, but from
later chapters I gather --log-bin might be the more usual thing for
production use.

    mysql> quit
Perhaps use @kbd for user input in examples.  That's what that Texinfo
command is for.

    can change the password for others users.
others -> other

    we want the give the user
we want to give the user

    Even that the repair in myisamchk is quite secure
that -> though

    updated by the another program
delete `the'

    the perticular table type
perticular -> particular
    mysqlcheck should be used when the mysqld server is running, where as
where as -> whereas

    To be able to work good with other programs
good -> well

    actually the 52 second week of 1999.
52 second -> 52nd

    CAST(expr AS CHAR threats expression to be a string with the default
    character set.
threats -> treats (I guess).

    traverse a database in a manner that is not easy (in some case impossible)
case -> cases

    transactional and not transactional tables
not  -> non-

    As MySQL does it with special algorithm
... with a special ...

    swap two tables names
tables -> tables'

    using transactions safe tables
transactions safe -> transaction-safe

    should be resonable stable.
resonable -> reasonably

How to repeat:
Look at manual text :).
[10 Aug 2003 19:18] Arjen Lentz
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Thanks for your feedback, most of your suggestions were incorporated into the manual. But quite a few issue no longer existed.
Judging by your reference to "4.0 development version", you have probably been looking at a fairly old version of the manual (old than a year!).
Do check out the latest one online (www.mysql.com/doc) or one of the downloadable versions (www.mysql.com/documentation).