Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed broken links + spell check in 1.5 release notes.

  • Loading branch information...
commit 48be78cf088e6fca87d1e4da7c527e17305f9fe2 1 parent 1d6b7f3
Tim Graham authored October 25, 2012

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

  1. 28  docs/releases/1.5.txt
28  docs/releases/1.5.txt
@@ -26,7 +26,7 @@ yourself. This could be a simple extension to the existing ``User`` model -- for
26 26
 example, you could add a Twitter or Facebook ID field -- or you could completely
27 27
 replace the ``User`` with one totally customized for your site.
28 28
 
29  
-Django 1.5 is also the first release with `Python 3 support`_! We're labling
  29
+Django 1.5 is also the first release with `Python 3 support`_! We're labeling
30 30
 this support "experimental" because we don't yet consider it production-ready,
31 31
 but everything's in place for you to start porting your apps to Python 3.
32 32
 Our next release, Django 1.6, will support Python 3 without reservations.
@@ -36,8 +36,8 @@ Other notable new features in Django 1.5 include:
36 36
 * `Support for saving a subset of model's fields`_ -
37 37
   :meth:`Model.save() <django.db.models.Model.save()>` now accepts an
38 38
   ``update_fields`` argument, letting you specify which fields are
39  
-  written back to the databse when you call ``save()``. This can help
40  
-  in high-concurrancy operations, and can improve performance.
  39
+  written back to the database when you call ``save()``. This can help
  40
+  in high-concurrency operations, and can improve performance.
41 41
 
42 42
 * Better `support for streaming responses <#explicit-streaming-responses>`_ via
43 43
   the new  :class:`~django.http.StreamingHttpResponse` response class.
@@ -92,17 +92,17 @@ you can write application targeted for just Python 2, just Python 3, or single
92 92
 applications that support both platforms.
93 93
 
94 94
 However, we're labeling this support "experimental" for now: although it's
95  
-receved extensive testing via our automated test suite, it's recieved very
  95
+received extensive testing via our automated test suite, it's received very
96 96
 little real-world testing. We've done our best to eliminate bugs, but we can't
97 97
 be sure we covered all possible uses of Django. Further, Django's more than a
98 98
 web framework; it's an ecosystem of pluggable components. At this point, very
99  
-few third-party applications have been ported to Python 3, so it's unliukely
100  
-that a real-world application will have all its dependecies satisfied under
  99
+few third-party applications have been ported to Python 3, so it's unlikely
  100
+that a real-world application will have all its dependencies satisfied under
101 101
 Python 3.
102 102
 
103 103
 Thus, we're recommending that Django 1.5 not be used in production under Python
104  
-3. Instead, use this oportunity to begin :doc:`porting applications to Python 3
105  
-<topics/python>`. If you're an author of a pluggable component, we encourage you
  104
+3. Instead, use this opportunity to begin :doc:`porting applications to Python 3
  105
+</topics/python3>`. If you're an author of a pluggable component, we encourage you
106 106
 to start porting now.
107 107
 
108 108
 We plan to offer first-class, production-ready support for Python 3 in our next
@@ -194,7 +194,7 @@ Retrieval of ``ContentType`` instances associated with proxy models
194 194
 The methods :meth:`ContentTypeManager.get_for_model() <django.contrib.contenttypes.models.ContentTypeManager.get_for_model()>`
195 195
 and :meth:`ContentTypeManager.get_for_models() <django.contrib.contenttypes.models.ContentTypeManager.get_for_models()>`
196 196
 have a new keyword argument – respectively ``for_concrete_model`` and ``for_concrete_models``.
197  
-By passing ``False`` using this argument it is now possible to retreive the
  197
+By passing ``False`` using this argument it is now possible to retrieve the
198 198
 :class:`ContentType <django.contrib.contenttypes.models.ContentType>`
199 199
 associated with proxy models.
200 200
 
@@ -484,8 +484,8 @@ In order to be able to run unit tests in any order and to make sure they are
484 484
 always isolated from each other, :class:`~django.test.TransactionTestCase` will
485 485
 now reset the database *after* each test run instead.
486 486
 
487  
-No more implict DB sequences reset
488  
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  487
+No more implicit DB sequences reset
  488
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
489 489
 
490 490
 :class:`~django.test.TransactionTestCase` tests used to reset primary key
491 491
 sequences automatically together with the database flushing actions described
@@ -543,7 +543,7 @@ Miscellaneous
543 543
   available at :func:`django.utils.html.remove_tags`.
544 544
 
545 545
 * Uploaded files are no longer created as executable by default. If you need
546  
-  them to be executeable change :setting:`FILE_UPLOAD_PERMISSIONS` to your
  546
+  them to be executable change :setting:`FILE_UPLOAD_PERMISSIONS` to your
547 547
   needs. The new default value is `0666` (octal) and the current umask value
548 548
   is first masked out.
549 549
 
@@ -580,8 +580,8 @@ Streaming behavior of :class:`HttpResponse`
580 580
 
581 581
 Django 1.5 deprecates the ability to stream a response by passing an iterator
582 582
 to :class:`~django.http.HttpResponse`. If you rely on this behavior, switch to
583  
-:class:`~django.http.StreamingHttpResponse`. See :ref:`explicit-streaming-
584  
-responses` above.
  583
+:class:`~django.http.StreamingHttpResponse`. See
  584
+:ref:`explicit-streaming-responses` above.
585 585
 
586 586
 In Django 1.7 and above, the iterator will be consumed immediately by
587 587
 :class:`~django.http.HttpResponse`.

0 notes on commit 48be78c

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