Apply suggestions from code review

Co-authored-by: Carol Willing <carolcode@willingconsulting.com>

Author: mgorny

peps/pep-0817.rst

@@ -22,13 +22,13 @@ Post-History:
 Abstract
 ========
 
-The Python wheel packaging format uses
+Python's existing wheel packaging format uses
 :doc:`packaging:specifications/platform-compatibility-tags` to specify
 a given wheel's supported environments. These tags are unable to express
-features of modern hardware configurations, such as the availability of
-GPU acceleration, or to provide custom package variants, such as builds
-against different dependency ABIs. This is particularly challenging for
-the scientific computing, artificial intelligence (AI), machine learning
+modern hardware configurations and their features, such as the availability of
+GPU acceleration. The tags fail to provide custom package variants, such as builds
+against different dependency ABIs. These inabilities are particularly challenging for
+scientific computing, artificial intelligence (AI), machine learning
 (ML), and high-performance computing (HPC) communities.
 
 This PEP proposes "Wheel Variants", an extension to the
@@ -430,7 +430,7 @@ levels, including students, scientists and engineers:
 Heterogeneous computing environments
 ''''''''''''''''''''''''''''''''''''
 
-Research institutions and cloud providers often manage heterogeneous
+Research institutions and cloud providers manage heterogeneous
 computing clusters with different architectures (CPU, Hardware
 accelerators, ASICS, etc.). The current system requires
 environment-specific installation procedures, making reproducible
@@ -531,10 +531,10 @@ Motivation summary
 ------------------
 
 As highlighted in the previous section, the current Python packaging
-system cannot adequately serve the needs of modern heterogeneous
-computing environments. These aforementioned limitations force package
+system does not adequately serve the needs of modern heterogeneous
+computing environments. These existing limitations force package
 authors into complex workarounds that create friction for users,
-increase maintenance burden, and fragment the ecosystem.
+increase maintenance burden, and fragment the package tooling ecosystem.
 
 **Wheel Variants provide a standardized solution that:**
 
@@ -554,8 +554,7 @@ increase maintenance burden, and fragment the ecosystem.
 Out-of-scope features
 ---------------------
 
-This PEP tries to present the minimal scope required and leaves aspects
-to tools to evolve. A non-exhaustive list:
+This PEP presents the minimal scope required to meet modern heterogenous system needs. It leaves aspects beyond the minimal scope to evolve via tools or future PEPs. A non-exhaustive list of these aspects include:
 
 - The format of a static file to select variants deterministically or
   include variants in a ``pylock.toml`` file,