From bd83177c702359a14165b7058572710459b7d7eb Mon Sep 17 00:00:00 2001 From: James Bennett Date: Fri, 12 Nov 2010 16:35:40 +0000 Subject: [PATCH] Correct a typo in [14541]. git-svn-id: http://code.djangoproject.com/svn/django/trunk@14542 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.3-alpha-1.txt | 2 +- docs/releases/1.3.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/releases/1.3-alpha-1.txt b/docs/releases/1.3-alpha-1.txt index f5d9610475..596d1c7c2b 100644 --- a/docs/releases/1.3-alpha-1.txt +++ b/docs/releases/1.3-alpha-1.txt @@ -183,7 +183,7 @@ Due to the sensitive nature of passwords, however, Django 1.3 takes this step automatically; the default value of ``render_value`` is now ``False``, and developers who want the password value returned to the browser on a submission with errors (the previous behavior) must now -explicitly indicate this. For ezmple:: +explicitly indicate this. For example:: class LoginForm(forms.Form): username = forms.CharField(max_length=100) diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt index a292205ed6..b5c0035931 100644 --- a/docs/releases/1.3.txt +++ b/docs/releases/1.3.txt @@ -174,7 +174,7 @@ Due to the sensitive nature of passwords, however, Django 1.3 takes this step automatically; the default value of ``render_value`` is now ``False``, and developers who want the password value returned to the browser on a submission with errors (the previous behavior) must now -explicitly indicate this. For ezmple:: +explicitly indicate this. For example:: class LoginForm(forms.Form): username = forms.CharField(max_length=100)