From 842f8a1f7b34f034bb176572561bfc2c718ea9c8 Mon Sep 17 00:00:00 2001
From: Ned Batchelder <ned@nedbatchelder.com>
Date: Tue, 18 Mar 2025 08:22:05 -0400
Subject: [PATCH 1/2] use page titles as link text to avoid warnings

Previously we had scary red messages:
```
devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]
devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]
```
---
 core-developers/memorialization.rst | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/core-developers/memorialization.rst b/core-developers/memorialization.rst
index 61ec0560c..e34784708 100644
--- a/core-developers/memorialization.rst
+++ b/core-developers/memorialization.rst
@@ -41,8 +41,9 @@ The PSF staff does not follow up with GitHub with regards to GitHub account
 cancellation as this action is reserved for next-of-kin or designated by
 the deceased GitHub user to act as an account successor.
 
-The general policy regarding deceased users on GitHub is described
-`here <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_.
+The general policy regarding deceased users on GitHub is described on their
+`GitHub Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
+page.
 
 Repositories in the organization
 --------------------------------
@@ -77,7 +78,9 @@ The "in memoriam" Discourse topic mentioned above is best created by
 a community member close to the deceased.
 
 The general best practice for deceased community members on
-Discourse-powered forums is described `here <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`_.
+Discourse-powered forums is described on their
+`Best practices for deceased community members <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`_
+page.
 
 python.org email account
 ------------------------
@@ -135,7 +138,8 @@ Other PSF-related infrastructure
   Discord server to remove the user from the server. The PSF staff
   does not follow up with Discord with regards to Discord account
   cancellation. The general policy regarding deceased users on Discord
-  is available `here <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`_.
+  is available on their `Deceased or Incapacitated Users <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`_
+  page.
 
 * The user is removed from Salt configuration for the PSF infrastructure
   in `/pillar/base/users <https://github.com/python/psf-salt/tree/main/pillar/base/users>`_

From 2b32e25bcf34a786ec3f81574b416a9c9fa8f918 Mon Sep 17 00:00:00 2001
From: Ned Batchelder <ned@nedbatchelder.com>
Date: Wed, 19 Mar 2025 08:10:11 -0400
Subject: [PATCH 2/2] remove a duplicate 'GitHub'

---
 core-developers/memorialization.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core-developers/memorialization.rst b/core-developers/memorialization.rst
index e34784708..b1e51cea2 100644
--- a/core-developers/memorialization.rst
+++ b/core-developers/memorialization.rst
@@ -42,7 +42,7 @@ cancellation as this action is reserved for next-of-kin or designated by
 the deceased GitHub user to act as an account successor.
 
 The general policy regarding deceased users on GitHub is described on their
-`GitHub Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
+`Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
 page.
 
 Repositories in the organization