--- a/docs/setup.rst	Fri Feb 08 19:08:52 2013 +0100
+++ b/docs/setup.rst	Fri Feb 08 19:24:07 2013 +0100
@@ -689,8 +689,8 @@
    into above configuration
 
 .. note::
-   RhodeCode cannot be runned in multiprocess mode in apache, make sure
-   you don't specify `processes=num` directive in the config
+   Running RhodeCode in multiprocess mode in apache is not supported,
+   make sure you don't specify `processes=num` directive in the config
 
 
 Example wsgi dispatch script::

--- a/docs/upgrade.rst	Fri Feb 08 19:08:52 2013 +0100
+++ b/docs/upgrade.rst	Fri Feb 08 19:24:07 2013 +0100
@@ -75,6 +75,14 @@
 and will always recheck the settings of the application, if there are no new
 options that need to be set.
 
+
+.. note::
+   DB schema upgrade library has some limitations and can sometimes fail if you try to
+   upgrade from older major releases. In such case simply run upgrades sequentially, eg.
+   upgrading from 1.2.X to 1.5.X should be done like that: 1.2.X. > 1.3.X > 1.4.X > 1.5.X
+   You can always specify what version of RhodeCode you want to install for example in pip
+   `pip install RhodeCode==1.3.6`
+
 You may find it helpful to clear out your log file so that new errors are
 readily apparent::
 

--- a/docs/usage/general.rst	Fri Feb 08 19:08:52 2013 +0100
+++ b/docs/usage/general.rst	Fri Feb 08 19:24:07 2013 +0100
@@ -13,7 +13,15 @@
 not possible to push,clone or access repository. It's worth a notice that,
 even if someone will be given administrative access to RhodeCode and will
 delete a repository You can easy restore such action by restoring `rm__<date>`
-from the repository name, and internal repository storage (.hg/.git)
+from the repository name, and internal repository storage (.hg/.git). There
+is also a special command for cleaning such archived repos::
+
+    paster cleanup-repos --older-than=30d production.ini
+
+This command will scan for archived repositories that are older than 30d,
+display them and ask if you want to delete them (there's a --dont-ask flag also)
+If you host big amount of repositories with forks that are constantly deleted
+it's recommended that you run such command via crontab.
 
 Follow current branch in file view
 ----------------------------------
@@ -31,7 +39,7 @@
 only show the range between the first and last checkbox (no cherry pick).
 Clicking more than one checkbox will activate a link in top saying
 `Show selected changes <from-rev> -> <to-rev>` clicking this will bring
-compare view
+compare view. In this view also it's possible to switch to combined compare.
 
 Compare view is also available from the journal on pushes having more than
 one changeset