Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed a few formatting errors and typos, courtesy of the proofreaders…

… in #django-dev.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8038 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit cee642bcb88b21c67174fb99aacec1ff1982d21d 1 parent 2ba74ae
Malcolm Tredinnick authored

Showing 1 changed file with 12 additions and 12 deletions. Show diff stats Hide diff stats

  1. 24  docs/release_notes_1.0_alpha.txt
24  docs/release_notes_1.0_alpha.txt
@@ -30,7 +30,7 @@ Refactored admin application (newforms-admin)
30 30
     ``django.newforms``, and now available as simply ``django.forms``)
31 31
     and redesigned with extensibility and customization in mind. Full
32 32
     documentation for the admin application is available online in the
33  
-    official Django documentation::
  33
+    official Django documentation:
34 34
     
35 35
          http://www.djangoproject.com/documentation/admin/
36 36
 
@@ -38,10 +38,10 @@ Improved Unicode handling
38 38
     Django's internals have been refactored to use Unicode throughout;
39 39
     this drastically simplifies the task of dealing with
40 40
     non-Western-European content and data in Django. Additionally,
41  
-    utility functions have been provided to eash interoperability with
  41
+    utility functions have been provided to each interoperability with
42 42
     third-party libraries and systems which may or may not handle
43 43
     Unicode gracefully. Details are available in Django's
44  
-    Unicode-handling documentation::
  44
+    Unicode-handling documentation:
45 45
     
46 46
          http://www.djangoproject.com/documentation/unicode/
47 47
 
@@ -55,7 +55,7 @@ An improved Django ORM
55 55
     took place in the ORM's internals. A guide to the changes,
56 56
     including backwards-incompatible modifications and mentions of new
57 57
     features opened up by this refactoring, is available on the Django
58  
-    wiki::
  58
+    wiki:
59 59
     
60 60
          http://code.djangoproject.com/wiki/QuerysetRefactorBranch
61 61
 
@@ -66,12 +66,12 @@ Automatic escaping of template variables
66 66
     and allows both variables and larger template constructs to be
67 67
     marked as safe (requiring no escaping) or unsafe (requiring
68 68
     escaping). A full guide to this feature is in the documentation
69  
-    for the Django template system::
  69
+    for the Django template system:
70 70
     
71 71
         http://www.djangoproject.com/documentation/templates/#automatic-html-escaping
72 72
 
73 73
 There are many more new features, many bugfixes and many enhancements
74  
-to existing features from previous releases; the ``newforms` library,
  74
+to existing features from previous releases; the ``newforms`` library,
75 75
 for example, has undergone massive improvements including several
76 76
 useful add-ons in ``django.contrib`` which complement and build on
77 77
 Django's form-handling capabilities, and Django's file-uploading
@@ -84,7 +84,7 @@ fleshed out and APIs have been finalized for the 1.0 release. A
84 84
 complete guide to these changes will be available as part of the final
85 85
 Django 1.0 release, and a comprehensive list of backwards-incompatible
86 86
 changes is also available on the Django wiki for those who want to
87  
-begin developing and testing their upgrade process::
  87
+begin developing and testing their upgrade process:
88 88
     
89 89
     http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
90 90
 
@@ -123,7 +123,7 @@ followed soon after by Django 1.0. The timeline is projected to be:
123 123
 
124 124
 Of course, like any estimated timeline this is subject to change as
125 125
 requirements dictate; the latest information will always be available
126  
-on the Django project wiki::
  126
+on the Django project wiki:
127 127
 
128 128
     http://code.djangoproject.com/wiki/VersionOneRoadmap
129 129
 
@@ -137,23 +137,23 @@ production use, you can help the Django team by trying out the alpha
137 137
 codebase in a safe test environment and reporting any bugs or issues
138 138
 you encounter. The Django ticket tracker is the central place to
139 139
 search for open issues and open new issues if no existing ticket
140  
-corresponds to a problem you're running into::
  140
+corresponds to a problem you're running into:
141 141
 
142 142
     http://code.djangoproject.com/timeline
143 143
 
144 144
 Additionally, discussion of Django development, including progress
145 145
 toward the 1.0 release, takes place daily on the django-developers
146  
-mailing list::
  146
+mailing list:
147 147
 
148 148
     http://groups.google.com/group/django-developers
149 149
 
150 150
 And in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If
151 151
 you're interested in helping out with Django's development, feel free
152 152
 to join the discussions there. Django's online documentation also
153  
-includes pointers on how to contribute to Django::
  153
+includes pointers on how to contribute to Django:
154 154
 
155 155
     http://www.djangoproject.com/documentation/contributing/
156 156
 
157 157
 Contributions on any level -- from developing code to writing
158 158
 documentation to simply triaging tickets and helping to test proposed
159  
-bugifxes -- are always welcome and always appreciated.
  159
+bugfixes -- are always welcome and always appreciated.

0 notes on commit cee642b

Please sign in to comment.
Something went wrong with that request. Please try again.