diff --git a/DOCUMENTS/UPGRADE.txt b/DOCUMENTS/UPGRADE.txt
index 0707b8f1..5a817f5d 100644
--- a/DOCUMENTS/UPGRADE.txt
+++ b/DOCUMENTS/UPGRADE.txt
@@ -57,6 +57,13 @@ to have change the permissions for Postfix Admin.
 
 (the last command assumes your Apache is running with group "www")
 
+Since version 2.4 we use smarty templates. That means the templates_c directory
+needs to be writeable for your webserver.
+
+  $ chown -R www-data templates_c/
+
+(if your Apache runs as user "www-data")
+
 
 4. Configure
 ------------
@@ -66,8 +73,8 @@ relevant to your setup.
 Comparing config.inc.php with your previous using "diff" might save you some
 time.
 
-You can use a config.local.php file to contain your local settings - these will override any 
-defined in config.inc.php
+You can use a config.local.php file to contain your local settings. These will override any 
+defined in config.inc.php - and save some time when upgrading to a new version of PostfixAdmin ;-)
 
 5. Run setup.php
 ----------------------------------------
@@ -75,6 +82,7 @@ defined in config.inc.php
 Access setup.php through a web browser.
 
 It will attempt to upgrade your database, and also allow you to create a superadmin user.
+(In case the database upgrade fails, you can run setup.php?debug=1 to see the last executed query.)
 
 From version 2.3, you need to specify a setup_password in config.inc.php - 
 setup.php should guide you through this process. If you do not have a setup_password, type one
@@ -89,6 +97,12 @@ If you update from 2.1 or older, also create a superadmin account using setup.ph
 Note that admin/ has been merged into the main directory. Login with the
 superadmin account to setup domains and domain admins.
 
+5. Upgrade your postfix config
+------------------------------
+
+Since version 2.3, PostfixAdmin supports alias domains ($CONF['alias_domain']).
+If you want to use them, you have to add some queries to your postfix config -
+see POSTFIX_CONF for details.
 
 
 6. Done
diff --git a/INSTALL.TXT b/INSTALL.TXT
index a0ce2a4d..3329fea6 100644
--- a/INSTALL.TXT
+++ b/INSTALL.TXT
@@ -15,15 +15,23 @@ REQUIRED!!
 
 READ THIS FIRST!
 ----------------
-When this is an upgrade from Postfix Admin 1.5.4 please read DOCUMENTS/UPGRADE.TXT!!
+When this is an upgrade from a previous version of Postfix Admin, please read 
+DOCUMENTS/UPGRADE.TXT also!
 
 If you need to setup Postfix to be able to handle Virtual Domains and Virtual
-Users check out :
+Users check out:
 
-  - http://high5.net/howto/ 
+  - the PostfixAdmin documentation in the DOCUMENTS/ directory
+  - our wiki at http://sourceforge.net/apps/mediawiki/postfixadmin/
+
+There are also lots of HOWTOs around the web. Be warned that many of them 
+(even those listed below) may be outdated or incomplete. 
+Please stick to the PostfixAdmin documentation, and use those HOWTOs only if
+you need some additional information that is missing in the PostfixAdmin 
+DOCUMENTS/ folder.
   - http://codepoets.co.uk/postfixadmin-postgresql-courier-squirrelmail-debian-etch-howto-tutorial (Debian+Courier+PostgreSQL+Postfix+Postfixadmin)
   - http://bliki.rimuhosting.com/space/knowledgebase/linux/mail/postfixadmin+on+debian+sarge (Postfix+MySQL+Postfixadmin+Dovecot)
-  - http://gentoo-wiki.com/HOWTO_Setup_a_Virtual_Postfix/Courier_Mail_System_with_PostfixAdmin (Postfix+MySQL+Postfixadmin+Courier)
+  - http://en.gentoo-wiki.com/wiki/Virtual_mail_server_using_Postfix,_Courier_and_PostfixAdmin (Postfix+MySQL+Postfixadmin+Courier)
 
 
 1. Unarchive new Postfix Admin
@@ -61,7 +69,7 @@ For PostgreSQL:
 3. Configure PostfixAdmin so it can find the database
 -----------------------------------------------------
 
-Edit the config.inc.php file.
+Edit the config.inc.php file - or - create config.local.php and add your settings there.
 
 The most important settings are those for your database server.
 
@@ -74,9 +82,12 @@ to
 $CONF['configured'] = true;
 
 
-PostfixAdmin does not require write access to any files. You can therefore 
-leave the files owned as root (or a.n.other user); as long as the web server 
-user (e.g. www-data) can read them, it will be fine.
+PostfixAdmin does not require write access to any files except the tempates_c 
+directory (smarty cache). You can therefore leave the files owned as root (or
+another user); as long as the web server user (e.g. www-data) can read them, it
+will be fine.
+For templates_c/, allow write access (only) for the web server user (e. g. www-data).
+The easiest way to do this is   chown -R www-data templates_c
 
 The next 'step', is optional. Only do it, if other non-trusted users have access 
 to your user: