[Rt-commit] rt branch, 4.0/reword-upgrading-mysql, updated. rt-4.0.2rc1-13-gbcb1b5c

[Thomas Sibley]

The branch, 4.0/reword-upgrading-mysql has been updated
       via  bcb1b5c23a95101050b52d67bd4af35492406a3d (commit)
      from  744935a9f5f2a1f975770c55e2bece91359fd616 (commit)

Summary of changes:
 docs/UPGRADING.mysql |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

- Log -----------------------------------------------------------------
commit bcb1b5c23a95101050b52d67bd4af35492406a3d
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Fri Aug 12 10:33:07 2011 -0400

    Minor grammar nit: add a definite article

diff --git a/docs/UPGRADING.mysql b/docs/UPGRADING.mysql
index f65cabc..27cdd8e 100644
--- a/docs/UPGRADING.mysql
+++ b/docs/UPGRADING.mysql
@@ -18,7 +18,7 @@ will manifest as multiple login requests, corrupted binary attachments,
 and corrupted image custom fields, among others.  In order to resolve
 this issue, the upgrade process will need to modify the schema.
 
- 1) If you are moving database and/or upgrading MySQL
+ 1) If you are moving the database and/or upgrading MySQL
    1a) Dump the database; with MySQL 4.1 and greater be sure to pass
        the mysqldump command the --default-character-set=binary option.
        This is necessary because the data was originally encoded in

-----------------------------------------------------------------------