From ff4eedbf0ee5cc8ed522333ed87dae5ebe4f364c Mon Sep 17 00:00:00 2001
From: Natalia <124304+nessita@users.noreply.github.com>
Date: Wed, 1 Jul 2026 18:05:32 -0300
Subject: [PATCH] Disambiguated duplicate "Example" hyperlink targets in
 howto-release-django.txt.

Builds on djangoproject.com report errors as per:

howto-release-django.txt:3: WARNING:
Duplicate explicit target name: "example". [docutils]
---
 docs/internals/howto-release-django.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 302865d29ab3..c8063b78df9a 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -63,8 +63,8 @@ There are a lot of details, so please read on.
    populates a lot of boilerplate you will need for announcements, CVE
    publication, and hashes for commit messages. By using this app for preparing
    security issue metadata, your peer releasers can check your entries and
-   consult them again in the future.
-   (`Example <https://www.djangoproject.com/checklists/release/5.2.4/>`_)
+   consult them again in the future. See `example checklist
+   <https://www.djangoproject.com/checklists/release/5.2.4/>`_.
 
 Prerequisites
 =============
@@ -742,7 +742,8 @@ You're almost done! All that's left to do now is:
    #. Process the older versions that will reach End-Of-Mainstream and/or
       End-Of-Life support when this final release is published:
 
-      #. Ensure that the EOL versions are mentioned in the blog post. `Example
+      #. Ensure that the EOL versions are mentioned in the blog post. See
+         `example announcement
          <https://www.djangoproject.com/weblog/2025/apr/02/django-52-released/>`_.
 
       #. Create a tag for the EOL stable branch and delete the stable branch.