Author: mcbrown
Date: 2007-10-15 19:24:16 +0200 (Mon, 15 Oct 2007)
New Revision: 8099
Log:
Fixing some typos
Modified:
trunk/refman-5.1/dba-core.xml
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-10-15 17:08:54 UTC (rev 8098)
+++ trunk/refman-5.1/dba-core.xml 2007-10-15 17:24:16 UTC (rev 8099)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1773 bytes
@@ -24999,7 +24999,7 @@
has not changed since the previous full backup. After we have
made the initial full backup, it is more efficient to make
incremental backups. They are smaller and take less time to
- produce. The tradeoff is that, at recovery time, you cannot
+ produce. The trade off is that, at recovery time, you cannot
restore your data just by reloading the full backup. You must
also process the incremental backups to recover the
incremental changes.
@@ -28032,7 +28032,7 @@
<para>
If you replace the system's
<filename>/etc/localtime</filename> timezone file with a
- verion that uses rules differing from those in effect at
+ version that uses rules differing from those in effect at
<command>mysqld</command> startup, you should restart
<command>mysqld</command> so that it uses the updated rules.
Otherwise, <command>mysqld</command> might not notice when
@@ -29250,7 +29250,7 @@
The format of the events recorded in the binary log is dependent
on the binary logging format. Three format types are supported,
row-based logging, statement-based logging and mixed-base
- logging. The binry logging format used deoends on the MySQL
+ logging. The binary logging format used depends on the MySQL
version. For more information on logging formats, see
<xref linkend="binary-log-formats"/>.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8099 - trunk/refman-5.1 | mcbrown | 15 Oct |