Documentation markup fixes.

Author: pelme

docs/database.rst

@@ -9,8 +9,8 @@ minimum which is a best practice since next-to-no business logic
 should be requiring the database.  Moreover it makes it very clear
 what code uses the database and catches any mistakes.
 
-Enabling database access
-------------------------
+Enabling database access in tests
+---------------------------------
 
 You can use `py.test marks <http://pytest.org/latest/mark.html>`_ to
 tell ``pytest-django`` your test needs database access::

docs/helpers.rst

@@ -13,46 +13,46 @@ on what marks are and for notes on using_ them.
 .. _using: http://pytest.org/latest/example/markers.html#marking-whole-classes-or-modules
 
 
-``pytest.mark.django_db`` - request database access
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. py:function:: pytest.mark.django_db([transaction=False])
-
-   This is used to mark a test function as requiring the database. It
-   will ensure the database is setup correctly for the test. Each test
-   will run in its own transaction which will be rolled back at the end
-   of the test. This behavior is the same as Django's standard
-   `django.test.TestCase`_ class.
-
-   In order for a test to have access to the database it must either
-   be marked using the ``django_db`` mark or request one of the ``db``
-   or ``transactional_db`` fixtures.  Otherwise the test will fail
-   when trying to access the database.
-
-   :type transaction: bool
-   :param transaction:
-     The ``transaction`` argument will allow the test to use real transactions.
-     With ``transaction=False`` (the default when not specified), transaction
-     operations are noops during the test. This is the same behavior that
-     `django.test.TestCase`_
-     uses. When ``transaction=True``, the behavior will be the same as
-     `django.test.TransactionTestCase`_
-
-   .. note::
-
-      If you want access to the Django database *inside a fixture*
-      this marker will not help even if the function requesting your
-      fixture has this marker applied.  To access the database in a
-      fixture, the fixture itself will have to request the ``db`` or
-      ``transactional_db`` fixture.  See below for a description of
-      them.
-
-   .. note:: Automatic usage with ``django.test.TestCase``.
-
-     Test classes that subclass `django.test.TestCase`_ will have access to
-     the database always to make them compatible with existing Django tests.
-     Test classes that subclass Python's ``unittest.TestCase`` need to have the
-     marker applied in order to access the database.
+``pytest.mark.django_db(transaction=False)`` - request database access
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. :py:function:: pytest.mark.django_db:
+
+This is used to mark a test function as requiring the database. It
+will ensure the database is setup correctly for the test. Each test
+will run in its own transaction which will be rolled back at the end
+of the test. This behavior is the same as Django's standard
+`django.test.TestCase`_ class.
+
+In order for a test to have access to the database it must either
+be marked using the ``django_db`` mark or request one of the ``db``
+or ``transactional_db`` fixtures.  Otherwise the test will fail
+when trying to access the database.
+
+:type transaction: bool
+:param transaction:
+ The ``transaction`` argument will allow the test to use real transactions.
+ With ``transaction=False`` (the default when not specified), transaction
+ operations are noops during the test. This is the same behavior that
+ `django.test.TestCase`_
+ uses. When ``transaction=True``, the behavior will be the same as
+ `django.test.TransactionTestCase`_
+
+.. note::
+
+  If you want access to the Django database *inside a fixture*
+  this marker will not help even if the function requesting your
+  fixture has this marker applied.  To access the database in a
+  fixture, the fixture itself will have to request the ``db`` or
+  ``transactional_db`` fixture.  See below for a description of
+  them.
+
+.. note:: Automatic usage with ``django.test.TestCase``.
+
+ Test classes that subclass `django.test.TestCase`_ will have access to
+ the database always to make them compatible with existing Django tests.
+ Test classes that subclass Python's ``unittest.TestCase`` need to have the
+ marker applied in order to access the database.
 
 .. _django.test.TestCase: https://docs.djangoproject.com/en/dev/topics/testing/overview/#testcase
 .. _django.test.TransactionTestCase: https://docs.djangoproject.com/en/dev/topics/testing/overview/#transactiontestcase
@@ -178,6 +178,8 @@ The field name used for the username on the user model.
 ``db``
 ~~~~~~~
 
+.. fixture:: db
+
 This fixture will ensure the Django database is set up.  This only
 required for fixtures which want to use the database themselves.  A
 test function should normally use the :py:func:`~pytest.mark.django_db`