--- a/README4TRANSLATORS	Sun May 26 22:20:33 2019 +0200
+++ b/README4TRANSLATORS	Sun May 26 22:21:56 2019 +0200
@@ -4,10 +4,10 @@
 
 To translate a file, you can use a dedicated tool as the excellent gtranslator:
 
-- use the template .po file (e.g. sat.po) and name it to your translated language (e.g. fr.po for french); you can preferably generate a new template directly from the source with the following command (eventually adapted, the following command use zsh's globbing syntax), launched from root sat dir after having emptied the build directory:
+- use the template .pot file (e.g. sat.pot) and name it to your translated language (e.g. fr.po for french); you can preferably generate a new template directly from the source with the following command (eventually adapted, the following command use zsh's globbing syntax), launched from root sat dir after having emptied the build directory:
 > xgettext -L python -d sat --keyword=D_ -p i18n  **/*(.py|.tac|primitivus)(.) **/jp(.)
 
-- then to start a new translation, copy i18n/sat.po to your language file, e.g. cd i18n; cp sat.po fr.po
+- then to start a new translation, copy i18n/sat.pot to your language file, e.g. cd i18n; cp sat.pot fr.po
 
 - use the choosed tool (a simple text editor can be sufficient) to edit the file: e.g. gtranslator fr.po
 
@@ -16,7 +16,7 @@
 > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo
 
 - if you have already a translation, and want to update it (new translations to do, some sentences have changed), you can use the following commands:
-> msgmerge fr.po sat.po > fr2.po
+> msgmerge fr.po sat.pot > fr2.po
 and if everything is allright
 > mv fr2.po fr.po
 

--- a/doc/jp/blog.rst	Sun May 26 22:20:33 2019 +0200
+++ b/doc/jp/blog.rst	Sun May 26 22:21:56 2019 +0200
@@ -30,7 +30,7 @@
 get
 ===
 
-get command retrieves one or move blog post from specified location (by default the
+get command retrieves one or more blog post(s) from specified location (by default the
 personal blog of the profile).
 
 output can be customised to only retrieve some keys, or to use a specific template.
@@ -191,7 +191,7 @@
 open your browser when edition starts, and the later is the command to use when a
 modification is saved. In both cases you may use ``{url}`` to set the location of local HTML file.
 
-This can be use to activate automatic refreshing of the page.
+This can be used to activate automatic refreshing of the page.
 
 For **Konqueror**, you can use its D-Bus API to do refreshing. Ensure that ``qdbus`` is
 installed on your system, and enter the following lines in your ``sat.conf``:
@@ -229,14 +229,14 @@
    [jp]
    syntax_ext_dict = {"markdown": "markdown"}
 
-the first ``markdown`` is the name of the syntax (could an other syntax like ``xhtml``),
+the first ``markdown`` is the name of the syntax (could be an other syntax like ``xhtml``),
 while the second if the file extension.
 
 preview
 =======
 
 This command will show the specified file in browser, and refresh it when changes are
-detected. Configuration is the same as for `edit preview <edit_preview_>`_. This is can be
+detected. Configuration is the same as for `edit preview <edit_preview_>`_. This can be
 used if you have already started an edition with ``jp blog edit`` but forgot to use the ``-P, --preview`` arguments.
 
 example: