couple of trivial fixes

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/narr/i18n.rst b/docs/narr/i18n.rst
index f97d655ec..aa00673bc 100644
--- a/docs/narr/i18n.rst
+++ b/docs/narr/i18n.rst
@@ -36,7 +36,7 @@ While you write your software, you can insert specialized markup into
 your Python code that makes it possible for the system to translate
 text values into the languages used by your application's users.  This
 markup creates a :term:`translation string`.  A translation string is
-an object that behave mostly like a normal Unicode object, except that
+an object that behaves mostly like a normal Unicode object, except that
 it also carries around extra information related to its job as part of
 the :mod:`repoze.bfg` translation machinery.
 
@@ -104,7 +104,7 @@ translations of the same msgid, in case they conflict.
 The above translation string named a domain of ``form``.  A
 :term:`translator` function will often use the domain to locate the
 right translator file on the filesystem which contains translations
-for a given domain.  In this case, if it were trying to translate to
+for a given domain.  In this case, if it were trying to translate
 our msgid to German, it might try to find a translation from a
 :term:`gettext` file within a :term:`translation directory` like this
 one::
@@ -225,7 +225,7 @@ by creating various kinds of gettext files.
    <http://wiki.pylonshq.com/display/pylonsdocs/Internationalization+and+Localization>`_
    for more information.
 
-GNU gettext use three types of files in the translation framework,
+GNU gettext uses three types of files in the translation framework,
 ``.pot`` files, ``.po`` files and ``.mo`` files.
 
 ``.pot`` (Portable Object Template) files