[5.1.x] Used :pypi: role in docs where appropriate.

Backport of 304d25667433a59409e334a93acaaa9201840508 from main.

4 files changed, 7 insertions, 12 deletions

diff --git a/docs/topics/db/optimization.txt b/docs/topics/db/optimization.txt
index dd252121e2..6b2733643f 100644
--- a/docs/topics/db/optimization.txt
+++ b/docs/topics/db/optimization.txt
@@ -14,7 +14,7 @@ As general programming practice, this goes without saying. Find out :ref:`what
 queries you are doing and what they are costing you <faq-see-raw-sql-queries>`.
 Use :meth:`.QuerySet.explain` to understand how specific ``QuerySet``\s are
 executed by your database. You may also want to use an external project like
-django-debug-toolbar_, or a tool that monitors your database directly.
+:pypi:`django-debug-toolbar`, or a tool that monitors your database directly.
 
 Remember that you may be optimizing for speed or memory or both, depending on
 your requirements. Sometimes optimizing for one will be detrimental to the
@@ -30,8 +30,6 @@ readability of your code. **All** of the suggestions below come with the caveat
 that in your circumstances the general principle might not apply, or might even
 be reversed.
 
-.. _django-debug-toolbar: https://github.com/jazzband/django-debug-toolbar/
-
 Use standard DB optimization techniques
 =======================================
 
diff --git a/docs/topics/email.txt b/docs/topics/email.txt
index 9b7b404ec1..212911002f 100644
--- a/docs/topics/email.txt
+++ b/docs/topics/email.txt
@@ -708,7 +708,7 @@ to a file that can be inspected at your leisure.
 
 Another approach is to use a "dumb" SMTP server that receives the emails
 locally and displays them to the terminal, but does not actually send
-anything. The `aiosmtpd`_ package provides a way to accomplish this:
+anything. The :pypi:`aiosmtpd` package provides a way to accomplish this:
 
 .. code-block:: shell
 
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index 273e856910..3ac254de98 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -1335,9 +1335,7 @@ whenever you restart your application server::
 
 You can even pre-generate the JavaScript catalog as part of your deployment
 procedure and serve it as a static file. This radical technique is implemented
-in django-statici18n_.
-
-.. _django-statici18n: https://django-statici18n.readthedocs.io/
+in :pypi:`django-statici18n`.
 
 .. _url-internationalization:
 
diff --git a/docs/topics/performance.txt b/docs/topics/performance.txt
index a346dc7385..cedd824e30 100644
--- a/docs/topics/performance.txt
+++ b/docs/topics/performance.txt
@@ -55,11 +55,10 @@ code.
 Django tools
 ~~~~~~~~~~~~
 
-`django-debug-toolbar
-<https://github.com/jazzband/django-debug-toolbar/>`_ is a very handy tool that
-provides insights into what your code is doing and how much time it spends
-doing it. In particular it can show you all the SQL queries your page is
-generating, and how long each one has taken.
+:pypi:`django-debug-toolbar` is a very handy tool that provides insights into
+what your code is doing and how much time it spends doing it. In particular it
+can show you all the SQL queries your page is generating, and how long each one
+has taken.
 
 Third-party panels are also available for the toolbar, that can (for example)
 report on cache performance and template rendering times.