PEP 744: Add Discussions-To link and minor revisions (#4236)

Author: savannahostrowski

peps/pep-0774.rst

@@ -1,6 +1,7 @@
 PEP: 774
 Title: Removing the LLVM requirement for JIT builds
 Author: Savannah Ostrowski <savannah@python.org>
+Discussions-To: https://discuss.python.org/t/78548/
 Status: Draft
 Type: Standards Track
 Created: 27-Jan-2025
@@ -220,9 +221,7 @@ process. Additional tooling would be required to fetch the stencils and
 potentially create additional and unnecessary failure points in the workflow.
 This separation also makes it harder to ensure consistency between the stencils
 and the CPython source tree, as updates must be coordinated across the
-repositories. Finally, this approach introduces an attack vector, as external
-repositories are less integrated with our workflows, making provenance and
-integrity harder to guarantee.
+repositories.
 
 Hosting in cloud storage
 ------------------------
@@ -241,7 +240,7 @@ use Git LFS. Git LFS does not work well with offline workflows since files
 managed by LFS require an internet connection to fetch when checking out
 specific commits, which is disruptive for even basic Git workflows. Git LFS has
 some free quota but there are `additional
-costs <https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage>`__.
+costs <https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage>`__
 for exceeding that quota which are also undesirable.
 
 Maintain the status quo with LLVM as a build-time dependency