Browse files

Added changes missing from previous commit.

  • Loading branch information...
1 parent e16c48e commit e12aad2d57f76f8acbc369feb257cea342cc30c8 @aaugustin aaugustin committed Mar 24, 2013
Showing with 4 additions and 4 deletions.
  1. +4 −4 docs/releases/1.6.txt
@@ -298,13 +298,13 @@ connections.
When a :class:`~django.db.models.BooleanField` doesn't have an explicit
:attr:`~django.db.models.Field.default`, the implicit default value is
``None``. In previous version of Django, it was ``False``, but that didn't
-represent accurantely the lack of a value.
+represent accurately the lack of a value.
Code that relies on the default value being ``False`` may raise an exception
when saving new model instances to the database, because ``None`` isn't an
acceptable value for a :class:`~django.db.models.BooleanField`. You should
-either specify ``default=False`` explicitly on the field definition, or ensure
-the field is set to ``True`` or ``False`` before saving the object.
+either specify ``default=False`` in the field definition, or ensure the field
+is set to ``True`` or ``False`` before saving the object.
Translations and comments in templates
@@ -328,7 +328,7 @@ specified using ``{#`` / ``#}`` is now stricter. All translator comments not
located at the end of their respective lines in a template are ignored and a
warning is generated by :djadmin:`makemessages` when it finds them. E.g.:
- .. code-block:: html+django
+.. code-block:: html+django
{# Translators: This is ignored #}{% trans "Translate me" %}
{{ title }}{# Translators: Extracted and associated with 'Welcome' below #}

0 comments on commit e12aad2

Please sign in to comment.