summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CHANGES4
-rw-r--r--docs/api/dates.rst2
-rw-r--r--docs/dev.rst4
-rw-r--r--docs/messages.rst2
4 files changed, 6 insertions, 6 deletions
diff --git a/CHANGES b/CHANGES
index c2dcfe6..8de00b0 100644
--- a/CHANGES
+++ b/CHANGES
@@ -51,7 +51,7 @@ Bugfixes
* General: localedata directory is now locale-data (#109) (2d1882e)
* General: odict: Fix pop method (0a9e97e)
* General: Removed uses of datetime.date class from *.dat files (#174) (94f6830)
-* Messages: Fix plural selection for chinese (531f666)
+* Messages: Fix plural selection for Chinese (531f666)
* Messages: Fix typo and add semicolon in plural_forms (5784501)
* Messages: Flatten NullTranslations.files into a list (ad11101)
* Times: FixedOffsetTimezone: fix display of negative offsets (d816803)
@@ -275,7 +275,7 @@ Version 0.9.6
Version 0.9.5
-------------
-(relased on April 6th 2010)
+(released on April 6th 2010)
- Fixed the case where messages containing square brackets would break with
an unpack error.
diff --git a/docs/api/dates.rst b/docs/api/dates.rst
index 67ada41..0fa9f1f 100644
--- a/docs/api/dates.rst
+++ b/docs/api/dates.rst
@@ -4,7 +4,7 @@ Date and Time
.. module:: babel.dates
The date and time functionality provided by Babel lets you format standard
-Python `datetime`, `date` and `time` objects and and work with timezones.
+Python `datetime`, `date` and `time` objects and work with timezones.
Date and Time Formatting
------------------------
diff --git a/docs/dev.rst b/docs/dev.rst
index b1fde57..afc8b12 100644
--- a/docs/dev.rst
+++ b/docs/dev.rst
@@ -2,7 +2,7 @@ Babel Development
=================
Babel as a library has a long history that goes back to the Trac project.
-Since then it has evolved into a independently developed project that
+Since then it has evolved into an independently developed project that
implements data access for the CLDR project.
This document tries to explain as best as possible the general rules of
@@ -39,7 +39,7 @@ While PyPy does not currently support 3.3, it does support traditional
unicode literals which simplifies the entire situation tremendously.
Documentation must build on Python 2, Python 3 support for the
-documentation is an optional goal. Code examples in the docs preferrably
+documentation is an optional goal. Code examples in the docs preferably
are written in a style that makes them work on both 2.x and 3.x with
preference to the former.
diff --git a/docs/messages.rst b/docs/messages.rst
index 7c02ccf..6814425 100644
--- a/docs/messages.rst
+++ b/docs/messages.rst
@@ -41,7 +41,7 @@ The general procedure for building message catalogs looks something like this:
code base and write them to a POT (PO Template) file.
* make a copy of the POT file for a specific locale (for example, "en_US")
and start translating the messages
- * use a tool such as ``msgfmt`` to compile the locale PO file into an binary
+ * use a tool such as ``msgfmt`` to compile the locale PO file into a binary
MO file
* later, when code changes make it necessary to update the translations, you
regenerate the POT file and merge the changes into the various