Update i18n.rst for rake to paver transition

docs/en_us/developers/source/i18n.rst

@@ -217,18 +217,17 @@ the strings, or checking the translations into Github, see use cases).
    take a minute or two to complete::
 
     $ cd edx-platform
-    $ rake assets
-    $ rake i18n:extract
+    $ paver i18n_extract
 
 2. Generate dummy strings:  See coverage testing (below) for more details. This
    will create an "Esperanto" translation that is actually over-accented
    English.  Use this to create fake translations::
 
-    $ rake i18n:dummy
+    $ paver i18n_dummy
     
-3. Run the rake i18n:generate command to create machine-readable .mo files::
+3. Run the paver i18n_generate command to create machine-readable .mo files::
  
-    $ rake i18n:generate
+    $ paver i18n_generate
 
 4. Django should be ready to go. The next time you run Studio or LMS, append
    ``?preview-lang=eo`` to the URL to turn on Esperanto as a dark language. The
@@ -259,7 +258,7 @@ and correct specific gaps in compliance.
 
 Use the coverage tool to generate dummy files::
 
-    $ rake i18n:dummy
+    $ paver i18n_dummy
     
 This will create new dummy translations in the Esperanto directory
 (edx-platform/conf/local/eo/LC_MESSAGES).