docs: fix Sphinx warnings

Author: blueyed

docs/changelog.rst

@@ -130,7 +130,7 @@ Compatibility
   database access was prevented on the cursor level. To be safer and prevent
   more cases, it is now prevented at the connection level. If you previously
   had tests which interacted with the databases without a database cursor, you
-  will need to mark them with the :func:`pytest.mark.django_db` marker or
+  will need to mark them with the ``pytest.mark.django_db`` marker or
   request the ``db`` fixture.
 
 * The previously undocumented internal fixtures ``_django_db_setup``,

docs/database.rst

@@ -246,7 +246,7 @@ django_db_blocker
 
 .. warning::
     It does not manage transactions and changes made to the database will not
-    be automatically restored. Using the :func:`pytest.mark.django_db` marker
+    be automatically restored. Using the ``pytest.mark.django_db`` marker
     or :fixture:`db` fixture, which wraps database changes in a transaction and
     restores the state is generally the thing you want in tests. This marker
     can be used when you are trying to influence the way the database is

docs/helpers.rst

@@ -207,7 +207,7 @@ is configured to be in the containing Django project.
 
 This fixture will ensure the Django database is set up.  Only
 required for fixtures that want to use the database themselves.  A
-test function should normally use the :py:func:`~pytest.mark.django_db`
+test function should normally use the ``pytest.mark.django_db``
 mark to signal it needs the database.
 
 ``transactional_db``
@@ -216,7 +216,7 @@ mark to signal it needs the database.
 This fixture can be used to request access to the database including
 transaction support.  This is only required for fixtures which need
 database access themselves.  A test function would normally use the
-:py:func:`~pytest.mark.django_db` mark to signal it needs the database.
+``pytest.mark.django_db`` mark to signal it needs the database.
 
 ``live_server``
 ~~~~~~~~~~~~~~~

docs/managing_python_path.rst

@@ -25,7 +25,7 @@ first file is found.
 
 If you have a custom project setup, have none or multiple ``manage.py`` files
 in your project, the automatic detection may not be correct. See
-:ref:`managing_the_python_path_explicilty` for more details on how to configure
+:ref:`managing_the_python_path_explicitly` for more details on how to configure
 your environment in that case.
 
 .. _managing_the_python_path_explicitly: