diff options
| author | Adam Johnson <me@adamj.eu> | 2020-03-31 09:37:38 +0100 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2020-04-01 15:15:21 +0200 |
| commit | 0342d47e7a8571242a570b91dea3c137436740d4 (patch) | |
| tree | ba498b92af4257836298bd28d5be9ec6458799ae /docs/internals | |
| parent | c9437596fe54fb5cf0330ee5a96e260903a2d683 (diff) | |
[3.0.x] Prevented (and corrected) single backtick usage in docs.
Backport of 1cdfe8d91215eefaa18c398069dd9c6879a9511d from master.
Diffstat (limited to 'docs/internals')
4 files changed, 5 insertions, 5 deletions
diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt index c807dba079..dbadb4cb0a 100644 --- a/docs/internals/contributing/new-contributors.txt +++ b/docs/internals/contributing/new-contributors.txt @@ -146,7 +146,7 @@ FAQ (except the Django fellow), and sometimes folks just don't have time. The best thing to do is to send a gentle reminder to the |django-developers| mailing list asking for review on the ticket, or to bring it up in the - `#django-dev` IRC channel. + ``#django-dev`` IRC channel. 2. **I'm sure my ticket is absolutely 100% perfect, can I mark it as RFC myself?** diff --git a/docs/internals/contributing/writing-code/javascript.txt b/docs/internals/contributing/writing-code/javascript.txt index bcb83d18bc..b8ff4de210 100644 --- a/docs/internals/contributing/writing-code/javascript.txt +++ b/docs/internals/contributing/writing-code/javascript.txt @@ -131,8 +131,8 @@ Testing from the command line To run the tests from the command line, you need to have `Node.js`_ installed. -After installing `Node.js`, install the JavaScript test dependencies by running -the following from the root of your Django checkout: +After installing ``Node.js``, install the JavaScript test dependencies by +running the following from the root of your Django checkout: .. console:: diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index e9668793a3..efc862dc76 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -124,7 +124,7 @@ Running the JavaScript tests Django includes a set of :ref:`JavaScript unit tests <javascript-tests>` for functions in certain contrib apps. The JavaScript tests aren't run by default -using ``tox`` because they require `Node.js` to be installed and aren't +using ``tox`` because they require ``Node.js`` to be installed and aren't necessary for the majority of patches. To run the JavaScript tests using ``tox``: diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 00264ab2fa..cc40dfe9db 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -379,7 +379,7 @@ Now you're ready to actually put the release out there. To do this: message body should include the vulnerability details, for example, the announcement blog post text. Include a link to the announcement blog post. -#. Add a link to the blog post in the topic of the `#django` IRC channel: +#. Add a link to the blog post in the topic of the ``#django`` IRC channel: ``/msg chanserv TOPIC #django new topic goes here``. Post-release |