diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index 8474d9e..8dc05c0 100644
|
a
|
b
|
Save these changes and start a new Python interactive shell by running
|
| 703 | 703 | |
| 704 | 704 | For more information on model relations, see :doc:`Accessing related objects |
| 705 | 705 | </ref/models/relations>`. For more on how to use double underscores to perform |
| 706 | | field lookups via the API, see `Field lookups`__. For full details on the |
| | 706 | field lookups via the API, see :ref:`Field lookups <field-lookups-intro>`. For full details on the |
| 707 | 707 | database API, see our :doc:`Database API reference </topics/db/queries>`. |
| 708 | 708 | |
| 709 | | __ http://docs.djangoproject.com/en/1.2/topics/db/queries/#field-lookups |
| 710 | | |
| 711 | 709 | When you're comfortable with the API, read :doc:`part 2 of this tutorial |
| 712 | 710 | </intro/tutorial02>` to get Django's automatic admin working. |
diff --git a/docs/releases/1.0.1.txt b/docs/releases/1.0.1.txt
index 780dc53..37142a2 100644
|
a
|
b
|
Welcome to Django 1.0.1!
|
| 6 | 6 | |
| 7 | 7 | This is the first "bugfix" release in the Django 1.0 series, improving |
| 8 | 8 | the stability and performance of the Django 1.0 codebase. As such, |
| 9 | | Django 1.0.1 contains no new features (and, pursuant to `our |
| 10 | | compatibility policy`_, maintains backwards compatibility with Django |
| | 9 | Django 1.0.1 contains no new features (and, pursuant to :doc:`our |
| | 10 | compatibility policy </misc/api-stability/>`, maintains backwards |
| | 11 | compatibility with Django |
| 11 | 12 | 1.0), but does contain a number of fixes and other |
| 12 | 13 | improvements. Django 1.0.1 is a recommended upgrade for any |
| 13 | 14 | development or deployment currently using or targeting Django 1.0. |
| … |
… |
highlights:
|
| 46 | 47 | |
| 47 | 48 | * A fix to the application of autoescaping for literal strings passed |
| 48 | 49 | to the ``join`` template filter. Previously, literal strings passed |
| 49 | | to ``join`` were automatically escaped, contrary to `the documented |
| 50 | | behavior for autoescaping and literal strings`_. Literal strings |
| | 50 | to ``join`` were automatically escaped, contrary to :ref:`the |
| | 51 | documented behavior for autoescaping and literal strings |
| | 52 | <string-literals-and-automatic-escaping>`. Literal strings |
| 51 | 53 | passed to ``join`` are no longer automatically escaped, meaning you |
| 52 | 54 | must now manually escape them; this is an incompatibility if you |
| 53 | 55 | were relying on this bug, but not if you were relying on escaping |
| … |
… |
highlights:
|
| 60 | 62 | documentation, including both corrections to existing documents and |
| 61 | 63 | expanded and new documentation. |
| 62 | 64 | |
| 63 | | .. _our compatibility policy: http://docs.djangoproject.com/en/dev/misc/api-stability/ |
| 64 | 65 | .. _the Subversion log of the 1.0.X branch: http://code.djangoproject.com/log/django/branches/releases/1.0.X |
| 65 | | .. _the documented behavior for autoescaping and literal strings: http://docs.djangoproject.com/en/dev/topics/templates/#string-literals-and-automatic-escaping |
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index f907c23..65b2d59 100644
|
a
|
b
|
whatever you want. For example::
|
| 324 | 324 | should work; all are optional. |
| 325 | 325 | |
| 326 | 326 | For details on accessing backwards-related objects, see the |
| 327 | | `Following relationships backward example`_. |
| | 327 | :ref:`Following relationships backward example <backwards-related-objects>`. |
| 328 | 328 | |
| 329 | 329 | For sample code, see the `Many-to-one relationship model tests`_. |
| 330 | 330 | |
| 331 | | .. _Following relationships backward example: http://docs.djangoproject.com/en/dev/topics/db/queries/#backwards-related-objects |
| 332 | 331 | .. _Many-to-one relationship model tests: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one |
| 333 | 332 | |
| 334 | 333 | Many-to-many relationships |
diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 719fc67..17e5d69 100644
|
a
|
b
|
to any variable that needs escaping. When auto-escaping is on, there's no
|
| 556 | 556 | danger of the :tfilter:`escape` filter *double-escaping* data -- the |
| 557 | 557 | :tfilter:`escape` filter does not affect auto-escaped variables. |
| 558 | 558 | |
| | 559 | .. _string-literals-and-automatic-escaping: |
| | 560 | |
| 559 | 561 | String literals and automatic escaping |
| 560 | 562 | -------------------------------------- |
| 561 | 563 | |