rna source files are not needed in POTFILE.in, and small fix on readme

2 files changed, 9 insertions, 29 deletions

diff --git a/po/POTFILES.in b/po/POTFILES.in
index 30c1d91b572..5a4ba6a9cb2 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -192,27 +192,7 @@ source/blender/editors/util/undo.c
 source/blender/editors/uvedit/uvedit_ops.c
 source/blender/editors/uvedit/uvedit_unwrap_ops.c
 
-source/blender/makesrna/intern/rna_ID.c
-source/blender/makesrna/intern/rna_action.c
-source/blender/makesrna/intern/rna_color.c
-source/blender/makesrna/intern/rna_constraint.c
-source/blender/makesrna/intern/rna_curve.c
-source/blender/makesrna/intern/rna_fcurve.c
-source/blender/makesrna/intern/rna_material.c
-source/blender/makesrna/intern/rna_mesh.c
-source/blender/makesrna/intern/rna_modifier.c
-source/blender/makesrna/intern/rna_object.c
-source/blender/makesrna/intern/rna_object_force.c
-source/blender/makesrna/intern/rna_particle.c
-source/blender/makesrna/intern/rna_render.c
-source/blender/makesrna/intern/rna_scene.c
-source/blender/makesrna/intern/rna_space.c
-source/blender/makesrna/intern/rna_texture.c
-source/blender/makesrna/intern/rna_ui_api.c
 source/blender/makesrna/intern/rna_userdef.c
-source/blender/makesrna/intern/rna_wm.c
-source/blender/makesrna/intern/rna_wm_api.c
-source/blender/makesrna/intern/rna_world.c
 
 source/blender/windowmanager/intern/wm_files.c
 source/blender/windowmanager/intern/wm_operators.c
diff --git a/po/README.txt b/po/README.txt
index 76dce7b414c..cadcb7194e8 100644
--- a/po/README.txt
+++ b/po/README.txt
@@ -6,7 +6,7 @@ I'll try briefly explain how translation works and how to update translation fil
 1. How it works
 ---------------
 
-This folder contains source files for translation system. This source files have
+This folder contains source files for translation system. These source files have
 got .po extension and they've got pretty simple syntax:
 
 msgid "some message id"
@@ -16,9 +16,9 @@ This means when string "some message id" is used as operator name, tooltip, menu
 and so it'll be displayed on the screen as "translation for this message".
 Pretty simple.
 
-This source files are pre-compiled into ../relese/bin/.blender/locale/<language>/LC_MESSAGES/blender.mo,
-so they aren't getting compiled every time Blender is compiling to same some time and prevent
-failure on systems which doesn't have needed tools for compiling .po files.
+This source files are pre-compiled into ../release/bin/.blender/locale/<language>/LC_MESSAGES/blender.mo,
+so they aren't getting compiled every time Blender is compiling to save some time and prevent
+failure on systems which don't have needed tools for compiling .po files.
 
 2. How to update translations
 -----------------------------
@@ -32,7 +32,7 @@ msgid "some message id"
 msgstr "translation for this message"
 
 it means translation used to exist for this message, but message was changed, so translation
-also have to be updated (it's easier to make new translation based on previos translation).
+also have to be updated (it's easier to make new translation based on previous translation).
 When translation was updated, remove line with '#, fuzzy' and it'll work.
 
 If there's no message in .po file you want to translate, probably .po file should be updated.
@@ -46,7 +46,7 @@ Use the following steps for this:
 - Run update_po.py script to merge all .po files with blender.pot (so all .po files
   will contain all msgid-s declared in blender.pot) or update_po.py <language> to
   update only needed .po file(s) to save time when you're busy with translation.
-  But before ocmmit all .po files better be updated.
+  But before commit all .po files better be updated.
 
 When you've finished with translation, you should re-compile .po file into .mo file.
 It's also pretty simple: just run update_mo.py script to recompile all languages or
@@ -54,7 +54,7 @@ just update_mo.py <language> to re-compile only needed language(s).
 
 NOTE: msgfmt, msgmerge and xgettext tools should be available in your PATH.
 
-This steps to update template, translation files and compile them can be made in "batch" mode
+These steps to update template, translation files and compile them can be made in "batch" mode
 using GNUMakefile:
 
 make -f GNUMakefile translations
@@ -65,7 +65,7 @@ NOTE: Blender has to be compiled using GNUMakefile first.
 3. Note for Windows users
 -------------------------
 You can find compiled builds of gettext in the lib folder under "binaries\gettext\" for both windows and win64.
-In order to run the scripts you will need to replace the location of the GETTEXT_..._EXeCUTABLE.
+In order to run the scripts you will need to replace the location of the GETTEXT_..._EXECUTABLE.
 
 For example in update_pot.py:
 -GETTEXT_XGETTEXT_EXECUTABLE = "xgettext"
@@ -77,5 +77,5 @@ For example in update_pot.py:
 - check_po.py: this script checks if all messages declared in blender.pot exists in.po files
                and that no extra messages are declared in .po files
 - clean_po.py: this script removes all commented messages which aren't required by .pot file anymore.
-- merge_po.py: this scripts accepts two files as arguments and copies translations from second file
+- merge_po.py: this script accepts two files as arguments and copies translations from second file
                into first file.