minor changes to the bodystructure parser

[squirrelmail.git] / UPGRADE

diff --git a/UPGRADE b/UPGRADE
index 079d59e74a52764f1568ac7dece469fca1fd1518..8c266bbf0894fe53cf615a5748f7ebcb3b37f255 100644 (file)
--- a/UPGRADE
+++ b/UPGRADE
@@ -66,7 +66,7 @@ the config file.
 
 C.  Copy plugins
 
-Like SquirrelMail, plugins are fequently updated for improvements, as well
+Like SquirrelMail, plugins are frequently updated for improvements, as well
 as to make them compatible with new SquirrelMail releases.  It is suggested
 that you download a new plugins archive at the same time you download your
 SquirrelMail install, and that you install your plugins fresh (it's easy,
@@ -82,7 +82,7 @@ plugins.
 D.  Copy themes
 
 If you've created or modified themes, you should copy just those to the new
-SquirrelMail themes direcory.  To just copy them all over to the new
+SquirrelMail themes directory.  To just copy them all over to the new
 SquirrelMail installation, you can run one command.
 
   $ cp squirrelmail-1.0.6.bak/themes/* squirrelmail-1.2.0/themes/
@@ -111,15 +111,10 @@ Run config/conf.pl to see the new configuration options available with the
 new version, as well as to verify that all of your old options are set
 properly.
 
-When you have migrated plugins from your old install to your new
-install, or even use any plugins at all, you *must* run conf.pl and do
-the following:
+Always save your options, also if you haven't changed anything.
+This will ensure that any problems with conf.pl that might have been solved
+are effective to your installation.
 
-A.  Select "8" (Plugins)
-B.  Select "A" (Sanitize all plugins for use with Squirrelmail 1.2)
-
-This will make sure the plugins work more efficiently (and will
-release you from any "cannot redeclare" error messages).
 
 6.  DONE!
 =========