X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/dceb1c097c8c24b398f48b482220c358bc7b4db4..11ef729d54ee338a1d569b5a238c2feb84d488ff:/docs/latex/wx/ti18n.tex?ds=inline

diff --git a/docs/latex/wx/ti18n.tex b/docs/latex/wx/ti18n.tex
index a112b1e958..93a0c60d9a 100644
--- a/docs/latex/wx/ti18n.tex
+++ b/docs/latex/wx/ti18n.tex
@@ -9,13 +9,13 @@ facilities for message translation with its
 \helpref{wxLocale}{wxlocale} class and is itself fully translated into several
 languages. Please consult wxWidgets home page for the most up-to-date
 translations - and if you translate it into one of the languages not done
-yet, your translations would be gratefully accepted for inclusion into the
-future versions of the library!
+yet, your translations would be gratefully accepted for inclusion into future
+versions of the library!
 
-The wxWidgets approach to i18n closely follows GNU gettext package. wxWidgets uses the
+The wxWidgets approach to i18n closely follows the GNU gettext package. wxWidgets uses the
 message catalogs which are binary compatible with gettext catalogs and this
 allows to use all of the programs in this package to work with them. But note
-that no additional libraries are needed during the run-time, however, so you
+that no additional libraries are needed during run-time, however, so you
 have only the message catalogs to distribute and nothing else.
 
 During program development you will need the gettext package for
@@ -80,5 +80,5 @@ See also \helpref{Writing non-English applications}{nonenglishoverview}.
 It focuses on handling charsets related problems.
 
 Finally, take a look at the \helpref{i18n sample}{sampleinternat} which shows
-to you how all this looks in practice.
+you how all this looks in practice.