diff --git a/peps/pep-0765.rst b/peps/pep-0765.rst
index 104a1b8210f..f2036b0b1a8 100644
--- a/peps/pep-0765.rst
+++ b/peps/pep-0765.rst
@@ -1,12 +1,13 @@
 PEP: 765
 Title: Disallow return/break/continue that exit a finally block
 Author: Irit Katriel <irit@python.org>, Alyssa Coghlan <ncoghlan@gmail.com>
-Discussions-To: https://discuss.python.org/t/an-analysis-of-return-in-finally-in-the-wild/70633
+Discussions-To: https://discuss.python.org/t/pep-765-disallow-return-break-continue-that-exit-a-finally-block/71348
 Status: Draft
 Type: Standards Track
 Created: 15-Nov-2024
 Python-Version: 3.14
 Post-History: `09-Nov-2024 <https://discuss.python.org/t/an-analysis-of-return-in-finally-in-the-wild/70633>`__,
+              `16-Nov-2024 <https://discuss.python.org/t/pep-765-disallow-return-break-continue-that-exit-a-finally-block/71348>`__,
 
 Abstract
 ========
@@ -66,7 +67,7 @@ A recent `analysis of real world code
 This new data indicates that it would benefit Python's users if
 Python itself moved them away from this harmful feature.
 
-`One of the arguments brought up
+One of the arguments brought up in `the PEP 601 discussion
 <https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/24>`__
 was that language features should be orthogonal, and combine without
 context-based restrictions. However, in the meantime :pep:`654` has