Skip to content

Commit

Permalink
Fixed a couple of typos in the 1.5 (and beta) release notes.
Browse files Browse the repository at this point in the history
Backport of [7cea123] from master.
  • Loading branch information
jacobian committed Nov 27, 2012
1 parent 28120a9 commit 212214e
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/releases/1.5-beta-1.txt
Expand Up @@ -78,7 +78,7 @@ can simply remove that line under Django 1.5
Python compatibility
====================

Django 1.5 requires Python 2.6.5 or above, though we **highly recommended**
Django 1.5 requires Python 2.6.5 or above, though we **highly recommend**
Python 2.7.3 or above. Support for Python 2.5 and below as been dropped.

This change should affect only a small number of Django users, as most
Expand All @@ -99,7 +99,7 @@ Python 3 support
Django 1.5 introduces support for Python 3 - specifically, Python
3.2 and above. This comes in the form of a **single** codebase; you don't
need to install a different version of Django on Python 3. This means that
you can write application targeted for just Python 2, just Python 3, or single
you can write applications targeted for just Python 2, just Python 3, or single
applications that support both platforms.

However, we're labeling this support "experimental" for now: although it's
Expand Down
2 changes: 1 addition & 1 deletion docs/releases/1.5.txt
Expand Up @@ -88,7 +88,7 @@ Python 3 support
Django 1.5 introduces support for Python 3 - specifically, Python
3.2 and above. This comes in the form of a **single** codebase; you don't
need to install a different version of Django on Python 3. This means that
you can write application targeted for just Python 2, just Python 3, or single
you can write applications targeted for just Python 2, just Python 3, or single
applications that support both platforms.

However, we're labeling this support "experimental" for now: although it's
Expand Down

0 comments on commit 212214e

Please sign in to comment.