diff --git a/docs/usage/performance.rst b/docs/usage/performance.rst
--- a/docs/usage/performance.rst
+++ b/docs/usage/performance.rst
@@ -1,15 +1,15 @@
 .. _performance:
 
 ================================
-Optimizing RhodeCode Performance
+Optimizing Kallithea Performance
 ================================
 
-When serving large amount of big repositories RhodeCode can start
+When serving large amount of big repositories Kallithea can start
 performing slower than expected. Because of demanding nature of handling large
 amount of data from version control systems here are some tips how to get
 the best performance.
 
-* RhodeCode will perform better on machines with faster disks (SSD/SAN). It's
+* Kallithea will perform better on machines with faster disks (SSD/SAN). It's
   more important to have faster disk than faster CPU.
 
 * Slowness on initial page can be easily fixed by grouping repositories, and/or
@@ -17,7 +17,7 @@ the best performance.
   option and vcs_full_cache setting in .ini file
 
 
-Follow these few steps to improve performance of RhodeCode system.
+Follow these few steps to improve performance of Kallithea system.
 
 
 1. Increase cache
@@ -30,7 +30,7 @@ Follow these few steps to improve perfor
     few hundreds of repositories on main page can sometimes make the system
     to behave slow when cache expires for all of them. Increasing `expire`
     option to day (86400) or a week (604800) will improve general response
-    times for the main page. RhodeCode has an intelligent cache expiration
+    times for the main page. Kallithea has an intelligent cache expiration
     system and it will expire cache for repositories that had been changed.
 
 2. Switch from sqlite to postgres or mysql
@@ -40,10 +40,10 @@ Follow these few steps to improve perfor
     setup. Switching to mysql or postgres will result in a immediate
     performance increase.
 
-3. Scale RhodeCode horizontally
+3. Scale Kallithea horizontally
 
     Scaling horizontally can give huge performance increase when dealing with
-    large traffic (large amount of users, CI servers etc). RhodeCode can be
+    large traffic (large amount of users, CI servers etc). Kallithea can be
     scaled horizontally on one (recommended) or multiple machines. In order
     to scale horizontally you need to do the following:
 
@@ -53,7 +53,7 @@ Follow these few steps to improve perfor
       dir contains template caches, sessions, whoosh index and it's used for
       tasks locking (so it's safe across multiple instances). Set the
       `cache_dir`, `index_dir`, `beaker.cache.data_dir`, `beaker.cache.lock_dir`
-      variables in each .ini file to shared location across RhodeCode instances
+      variables in each .ini file to shared location across Kallithea instances
     - if celery is used each instance should run separate celery instance, but
       the message broken should be common to all of them (ex one rabbitmq
       shared server)