diff --git a/docs/translation.md b/docs/translation.md
index 49545bc7b4b6d2e2eb639c9f3c1aa8f7604b5180..b3f6335f0f3f1d3662ded3977dcce79451ffa951 100644
--- a/docs/translation.md
+++ b/docs/translation.md
@@ -52,8 +52,8 @@ After saving the file, the translation is completed. Return the translation by Z
 Entering each of the applications (/VIPSWeb, /forecasts, /messages), do:
 
 ```bash
-django-admin.py makemessages -l [LANGUAGE]
-django-admin.py makemessages -d djangojs -l [LANGUAGE]
+$ ./manage.py makemessages -l [LANGUAGE]
+$ ./manage.py makemessages -d djangojs -l [LANGUAGE]
 ```
 
 After that, you can edit the language files (see above)
@@ -61,17 +61,17 @@ After that, you can edit the language files (see above)
 PLEASE NOTE: django-admin.py has been creating buggy information for plurals. Please check the header field of your newly created .po file. If the plural-forms header does not start with «nplurals=X;», then something has gone wrong. You can find the correct header here: http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html 
 
 ### Updating translation files 
-If you have added new translation keywords, do this in each of the applications:
+If you have added new translation keywords, do this from the source root:
 
 ```bash
-$ ./manage.py makemessages -a [LANGUAGE]
+$ ./manage.py makemessages -a 
 $ ./manage.py makemessages -d djangojs -a [LANGUAGE]
 ```
 
 Then recompile the translation files (see below)
 
 ### Compiling translation files
-Entering each of the applications (/VIPSWeb, /forecasts, /messages), do:
+From the source root:
 
 ```
 $ ./manage.py compilemessages