diff --git a/ChangeLog b/ChangeLog
index bed38cb0..28354efa 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -17754,3 +17754,5 @@
 	switches in rddbmgr(8).
 	* Refactored handling of character set and collation attributes
 	in rddbmgr(8) to treat them as immutable parts of the DB schema.
+2018-10-09 Fred Gleason <fredg@paravelsystems.com>
+	* Removed the 'UPDATING CHARACTER SET' section from 'UPGRADING'.
diff --git a/UPGRADING b/UPGRADING
index 01b92bb4..1c46b983 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -72,46 +72,3 @@ The parameters passed to the RLMPadDataSent() callback in RLMs have changed;
 private plug-ins written for RD 1.x will need to be modified to work with the
 new API.  (All plug-ins supplied with the Rivendell sources have already been
 modified appropriately.)
-
-9) DATABASE CHARACTER SET CONVERSION
-Databases generated using Rivendell v1.x or v2.x used the 'latin1' character
-set. Such databases must be converted to use the 'utf8mb4' character set
-before they can be properly utilized by Rivendell 3.x. To perform this
-conversion, proceed as follows:
-
-BEFORE UPDATING
----------------
-A) Make a full and complete backup of the database, using either rdadmin(1)
-or the MySQL mysqldump(1) utility. Don't skip this!
-
-B) Use the rddbcheck(8) tool to verify the consistency of the database.
-Be sure to fix any problems found *before* upgrading the Rivendell binaries!
-
-AFTER UPDATING
---------------
-C) Check the '[mySQL]' section of '/etc/rd.conf' and verify that the
-following parameters are set:
-
-[mySQL]
-Charset=utf8mb4
-Collation=utf8mb4_general_ci
-
-(There will likely be additional parameters present in the '[mySQL]'
-section; these can be left unchanged).
-
-D) Update the DB schema using the rddbmgr(8) command:
-
-   rddbmgr --modify
-
-If all goes well, the command should exit without printing anything.
-
-E) Convert the DB character set using the rddbmgr(8) command:
-
-   rddbmgr --check --yes
-
-You should see a list of DB tables generated as each one is converted. 
-
-At this point, you should be ready to start the Rivendell service, by doing:
-
-   systemctl restart rivendell
-