summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorRamil Yanbulatov <rayman1104@gmail.com>2022-06-30 15:08:49 +0300
committerCarlton Gibson <carlton.gibson@noumenal.es>2022-08-09 14:44:51 +0200
commitc6290bae9da94234091673fa57ea20411325a9e8 (patch)
treea3aafea2b59d053aaaf44d0f23fa6db29c1c2e88 /docs/howto
parentf3a06b06b59b3d24d5c2c14a34a8051879203c45 (diff)
Fixed #33842 -- Used :source: role for links to repo files on GitHub.
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/custom-model-fields.txt4
-rw-r--r--docs/howto/custom-template-tags.txt4
-rw-r--r--docs/howto/deployment/wsgi/modwsgi.txt2
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt
index 5f563d920b..fed4b57c32 100644
--- a/docs/howto/custom-model-fields.txt
+++ b/docs/howto/custom-model-fields.txt
@@ -724,7 +724,7 @@ serialization formats. Here are a couple of tips to make things go more
smoothly:
#. Look at the existing Django fields (in
- :file:`django/db/models/fields/__init__.py`) for inspiration. Try to find
+ :source:`django/db/models/fields/__init__.py`) for inspiration. Try to find
a field that's similar to what you want and extend it a little bit,
instead of creating an entirely new field from scratch.
@@ -761,7 +761,7 @@ In addition to the above details, there are a few guidelines which can greatly
improve the efficiency and readability of the field's code.
#. The source for Django's own ``ImageField`` (in
- ``django/db/models/fields/files.py``) is a great example of how to
+ :source:`django/db/models/fields/files.py`) is a great example of how to
subclass ``FileField`` to support a particular type of file, as it
incorporates all of the techniques described above.
diff --git a/docs/howto/custom-template-tags.txt b/docs/howto/custom-template-tags.txt
index 30ef76d208..50c79cc0e9 100644
--- a/docs/howto/custom-template-tags.txt
+++ b/docs/howto/custom-template-tags.txt
@@ -1153,5 +1153,5 @@ The only new concept here is the ``self.nodelist.render(context)`` in
``UpperNode.render()``.
For more examples of complex rendering, see the source code of
-:ttag:`{% for %}<for>` in ``django/template/defaulttags.py`` and
-:ttag:`{% if %}<if>` in ``django/template/smartif.py``.
+:ttag:`{% for %}<for>` in :source:`django/template/defaulttags.py` and
+:ttag:`{% if %}<if>` in :source:`django/template/smartif.py`.
diff --git a/docs/howto/deployment/wsgi/modwsgi.txt b/docs/howto/deployment/wsgi/modwsgi.txt
index aba4178e7e..c2a2d3d1bd 100644
--- a/docs/howto/deployment/wsgi/modwsgi.txt
+++ b/docs/howto/deployment/wsgi/modwsgi.txt
@@ -197,7 +197,7 @@ admin app (and any other installed apps). This is however not the case when you
use any other server arrangement. You're responsible for setting up Apache, or
whichever web server you're using, to serve the admin files.
-The admin files live in (:file:`django/contrib/admin/static/admin`) of the
+The admin files live in (:source:`django/contrib/admin/static/admin`) of the
Django distribution.
We **strongly** recommend using :mod:`django.contrib.staticfiles` to handle the