Index: docs/tutorial01.txt =================================================================== --- docs/tutorial01.txt (revision 5540) +++ docs/tutorial01.txt (working copy) @@ -360,7 +360,7 @@ quotes. The author of this tutorial runs PostgreSQL, so the example output is in PostgreSQL syntax. - * The `sql` command doesn't actually run the SQL in your database - it just + * The ``sql`` command doesn't actually run the SQL in your database - it just prints it to the screen so that you can see what SQL Django thinks is required. If you wanted to, you could copy and paste this SQL into your database prompt. However, as we will see shortly, Django provides an easier way of committing Index: docs/email.txt =================================================================== --- docs/email.txt (revision 5540) +++ docs/email.txt (working copy) @@ -228,7 +228,7 @@ * ``message()`` constructs a ``django.core.mail.SafeMIMEText`` object (a sub-class of Python's ``email.MIMEText.MIMEText`` class) holding the - message to be sent. If you ever need to extend the `EmailMessage` class, + message to be sent. If you ever need to extend the ``EmailMessage`` class, you'll probably want to override this method to put the content you wish into the MIME object. Index: docs/db-api.txt =================================================================== --- docs/db-api.txt (revision 5540) +++ docs/db-api.txt (working copy) @@ -1779,7 +1779,7 @@ you can provide ``get_object_or_404()`` with a manager object instead. For example:: - # Get the author of blog instance `e` with a name of 'Fred' + # Get the author of blog instance ``e`` with a name of 'Fred' a = get_object_or_404(e.authors, name='Fred') # Use a custom manager 'recent_entries' in the search for an Index: docs/release_notes_0.96.txt =================================================================== --- docs/release_notes_0.96.txt (revision 5540) +++ docs/release_notes_0.96.txt (working copy) @@ -28,7 +28,7 @@ Due to a bug in older versions of the ``MySQLdb`` Python module (which Django uses to connect to MySQL databases), Django's MySQL backend now -requires version 1.2.1p2 or higher of `MySQLdb`, and will raise +requires version 1.2.1p2 or higher of ``MySQLdb``, and will raise exceptions if you attempt to use an older version. If you're currently unable to upgrade your copy of ``MySQLdb`` to meet @@ -44,7 +44,7 @@ DATABASE_ENGINE = "mysql_old" However, we strongly encourage MySQL users to upgrade to a more recent -version of `MySQLdb` as soon as possible, The "mysql_old" backend is +version of ``MySQLdb`` as soon as possible, The "mysql_old" backend is provided only to ease this transition, and is considered deprecated; aside from any necessary security fixes, it will not be actively maintained, and it will be removed in a future release of Django. Index: docs/legacy_databases.txt =================================================================== --- docs/legacy_databases.txt (revision 5540) +++ docs/legacy_databases.txt (working copy) @@ -18,7 +18,7 @@ what the name of the database is. Do that by editing these settings in your `settings file`_: - * `DATABASE_NAME` + * `DATABASE_NAME`_ * `DATABASE_ENGINE`_ * `DATABASE_USER`_ * `DATABASE_PASSWORD`_ Index: docs/serialization.txt =================================================================== --- docs/serialization.txt (revision 5540) +++ docs/serialization.txt (working copy) @@ -48,12 +48,12 @@ ~~~~~~~~~~~~~~~~ If you only want a subset of fields to be serialized, you can -specify a `fields` argument to the serializer:: +specify a ``fields`` argument to the serializer:: from django.core import serializers data = serializers.serialize('xml', SomeModel.objects.all(), fields=('name','size')) -In this example, only the `name` and `size` attributes of each model will +In this example, only the ``name`` and ``size`` attributes of each model will be serialized. .. note:: Index: docs/testing.txt =================================================================== --- docs/testing.txt (revision 5540) +++ docs/testing.txt (working copy) @@ -253,8 +253,8 @@ f.close() will result in the evaluation of a POST request on ``/customers/wishes/``, - with a POST dictionary that contains `name`, `attachment` (containing the - file name), and `attachment_file` (containing the file data). Note that you + with a POST dictionary that contains ``name``, ``attachment`` (containing the + file name), and ``attachment_file`` (containing the file data). Note that you need to manually close the file after it has been provided to the POST. ``login(**credentials)`` @@ -660,8 +660,8 @@ tested. This is the same format returned by ``django.db.models.get_apps()`` Verbosity determines the amount of notification and debug information that - will be printed to the console; `0` is no output, `1` is normal output, - and `2` is verbose output. + will be printed to the console; '0' is no output, '1' is normal output, + and '2' is verbose output. This method should return the number of tests that failed. Index: docs/authentication.txt =================================================================== --- docs/authentication.txt (revision 5540) +++ docs/authentication.txt (working copy) @@ -461,7 +461,7 @@ Other built-in views -------------------- -In addition to the `login` view, the authentication system includes a +In addition to the ``login`` view, the authentication system includes a few other useful built-in views: ``django.contrib.auth.views.logout`` Index: docs/django-admin.txt =================================================================== --- docs/django-admin.txt (revision 5540) +++ docs/django-admin.txt (working copy) @@ -513,7 +513,7 @@ Verbosity determines the amount of notification and debug information that will be printed to the console. '0' is no output, '1' is normal output, -and `2` is verbose output. +and '2' is verbose output. --adminmedia ------------