summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2007-05-14 02:21:28 +0000
committerAdrian Holovaty <adrian@holovaty.com>2007-05-14 02:21:28 +0000
commitedc014b255946b5965ccebe03ae8ac3b1c7c6323 (patch)
tree79f6dc48359ed6d597f38535cc870d60a8c6e65d /docs
parent3d86329f822f07b5208d61bb39fc3ee70b53814b (diff)
Another word tightening and clarification in docs/newforms.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5217 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/newforms.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/newforms.txt b/docs/newforms.txt
index ec3fab00a7..5ae6aaba85 100644
--- a/docs/newforms.txt
+++ b/docs/newforms.txt
@@ -10,9 +10,9 @@ Migration plan
==============
``django.newforms`` is new in Django's 0.96 release, but, as it won't be new
-forever, we plan to rename the ``django.newforms`` package to ``django.forms``
-in the future. The current ``django.forms`` package will be available as
-``django.oldforms``.
+forever, we plan to rename it to ``django.forms`` in the future. The current
+``django.forms`` package will be available as ``django.oldforms`` until Django
+1.0, when we plan to remove it for good.
That has direct repercussions on the forward compatibility of your code. Please
read the following migration plan and code accordingly: