Fixed typos introduced in r16430 and r16431. Thanks, magopian.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16433 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jannis Leidel 2011-06-18 08:48:25 +00:00
parent 65d8657f7f
commit 1dfa567a23
2 changed files with 2 additions and 2 deletions

View File

@ -1512,7 +1512,7 @@ If ``value`` is ``Tom & Jerry``, the output will be ``Tom & Jerry``.
However, ampersands used in named entities and numeric character references However, ampersands used in named entities and numeric character references
will not be replaced. For example, if ``value`` is ``Café``, the output will not be replaced. For example, if ``value`` is ``Café``, the output
will *not* be ``Caf&eacute&`` but remain ``Café``. This means that will *not* be ``Café`` but remain ``Café``. This means that
in some edge cases, such as acronyms followed by semicolons, this filter will in some edge cases, such as acronyms followed by semicolons, this filter will
not replace ampersands that need replacing. For example, if ``value`` is not replace ampersands that need replacing. For example, if ``value`` is
``Contact the R&D;``, the output will remain unchanged because ``&D;`` ``Contact the R&D;``, the output will remain unchanged because ``&D;``

View File

@ -442,7 +442,7 @@ If you manually render fields in the template, you can render
<li>{{ form.title }}</li> <li>{{ form.title }}</li>
{% if formset.can_delete %} {% if formset.can_delete %}
<li>{{ form.DELETE }}</li> <li>{{ form.DELETE }}</li>
{% enif %} {% endif %}
</ul> </ul>
{% endfor %} {% endfor %}
</form> </form>