mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00
Code Issues 32 Releases Wiki Activity

Changed some words to use inline markup.

Browse Source
This commit is contained in:
David Smith
2022-03-10 09:18:31 +00:00
committed by GitHub
parent b1005c0e40
commit 67b5f506a6
21 changed files with 43 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/contributing/writing-code/javascript.txt
View File

@@ -78,7 +78,7 @@ Django's JavaScript tests use `QUnit`_. Here is an example test module:
});
Please consult the QUnit documentation for information on the types of
Please consult the ``QUnit`` documentation for information on the types of
`assertions supported by QUnit <https://api.qunitjs.com/assert/>`_.
Running tests

5
docs/internals/contributing/writing-code/unit-tests.txt
View File

@@ -107,8 +107,9 @@ The remainder of this documentation shows commands for running tests without
``tox``, however, any option passed to ``runtests.py`` can also be passed to
``tox`` by prefixing the argument list with ``--``, as above.
Tox also respects the :envvar:`DJANGO_SETTINGS_MODULE` environment variable, if
set. For example, the following is equivalent to the command above:
``Tox`` also respects the :envvar:`DJANGO_SETTINGS_MODULE` environment
variable, if set. For example, the following is equivalent to the command
above:
.. code-block:: console

12
docs/internals/howto-release-django.txt
View File

@@ -121,9 +121,9 @@ any time leading up to the actual release:
$ python scripts/manage_translations.py fetch
and then commit the changed/added files (both .po and .mo). Sometimes there
are validation errors which need to be debugged, so avoid doing this task
immediately before a release is needed.
and then commit the changed/added files (both ``.po`` and ``.mo``).
Sometimes there are validation errors which need to be debugged, so avoid
doing this task immediately before a release is needed.
#. :ref:`Update the django-admin manual page <django-admin-manpage>`::
@@ -345,9 +345,9 @@ Now you're ready to actually put the release out there. To do this:
$ twine upload -s dist/*
#. Go to the `Add release page in the admin`__, enter the new release number
exactly as it appears in the name of the tarball (Django-<version>.tar.gz).
So for example enter "1.5.1" or "1.4c2", etc. If the release is part of
an LTS branch, mark it so.
exactly as it appears in the name of the tarball
(``Django-<version>.tar.gz``). So for example enter "1.5.1" or "1.4c2", etc.
If the release is part of an LTS branch, mark it so.
__ https://www.djangoproject.com/admin/releases/release/add/