diff options
| author | Tim Graham <timograham@gmail.com> | 2014-11-13 18:01:22 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-11-13 20:10:02 +0100 |
| commit | d5a109f6e6684b2ea8028af5c57f4257872d11aa (patch) | |
| tree | 9d9d6d044b108c9288b9a76d20cc106dcf8833a8 | |
| parent | 098368d82f67715723b5bd4445a8fe92a0ceae98 (diff) | |
Fixed #23802 -- Typos in 1.7 release notes.
| -rw-r--r-- | docs/releases/1.7.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index 000dfeb61d..3be203d229 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -1188,7 +1188,7 @@ query string. For example, the URL portion of a cache key is now generated from ``http://www.example.com/path/to/?key=val`` rather than ``/path/to/?key=val``. The cache keys generated by Django 1.7 will be different from the keys generated by older versions of Django. After upgrading to Django 1.7, the first -request to any previously cached URL will be a cache miss . +request to any previously cached URL will be a cache miss. Passing ``None`` to ``Manager.db_manager()`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -1410,8 +1410,8 @@ Miscellaneous primary keys with value 0. * Shadowing model fields defined in a parent model has been forbidden as this - creates ambiguity in the expected model behavior. In addition, any clashing - fields in the model inheritance hierarchy results in a system check error. + creates ambiguity in the expected model behavior. In addition, clashing + fields in the model inheritance hierarchy result in a system check error. For example, if you use multi-inheritance, you need to define custom primary key fields on parent models, otherwise the default ``id`` fields will clash. See :ref:`model-multiple-inheritance-topic` for details. @@ -1710,8 +1710,8 @@ The ``check()`` method has replaced the old ``validate()`` method. This method is deprecated in favor of a new ``check_field`` method. The functionality required by ``check_field()`` is the same as that provided by ``validate_field()``, but the output format is different. Third-party database -backends needing this functionality should modify their backends to provide an -implementation of ``check_field()``. +backends needing this functionality should provide an implementation of +``check_field()``. Loading ``ssi`` and ``url`` template tags from ``future`` library ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |