add refs, remove CWD acronym, fix grammar

Author: rickeylev

peps/pep-0796.rst

@@ -17,7 +17,7 @@ in a Python virtual environment's :file:`pyvenv.cfg` file.
 
 Specifically, we will discuss how such relative paths are understood
 by the Python startup process, including their conversion to absolute
-paths for use by the runtime. 
+paths for use by the runtime.
 This is a fundamental building block for virtual environments to
 become more portable.
 
@@ -27,7 +27,7 @@ Motivation
 There are two main motivations for allowing relative paths in ``pyvenv.cfg``.
 
 First, it is currently prescribed that the ``home`` value in ``pyvenv.cfg`` be
-an absolute path. The behavior of relative paths is unspecified. While
+an absolute path (`gh-135773`). The behavior of relative paths is unspecified. While
 techniques exist to work around this for every other sub-part of a virtual
 environment, the one remaining part without a tenable solution is how the
 Python runtime itself finds ``PYTHONHOME``. This is because, currently, the
@@ -83,7 +83,7 @@ Tools that currently look to enable virtual environment portability across
 machines do so either by relying on undocumented interpreter behaviour
 (Bazel, omitting the ``home`` key entirely to trigger an implementation
 dependent fallback to resolving via a symlinked interpreter binary on
-non-Windows systems) or by requiring a post-installation script to be executed
+non-Windows systems, see `gh-135773`) or by requiring a post-installation script to be executed
 after the environment is placed in its target location (venvstacks).
 
 Specification
@@ -122,8 +122,8 @@ primitives are there, so the only change needed is to define how it resolves
 relative paths for ``home`` in ``pyvenv.cfg``.
 
 Currently, relative paths resolve relative to the process's current working
-directory. Because CWD isn't knowable in advance, it makes relative paths today
-effectively impossible.
+directory. Because the current working directory isn't knowable in advance, it
+makes relative paths today effectively impossible.
 
 Instead, the paths should be relative to the location of the ``pyvenv.cfg``
 file. This file is chosen as the anchor point because the tool that creates the