Apply suggestions from code review

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

Author: mgorny

peps/pep-0817.rst

@@ -228,7 +228,7 @@ the burden on the maintainers to run separate infrastructure and to find
 and use non-standard features such as local version segments present on
 an index.
 
-**Induced Security Risk:** This approach has unfortunately led to supply
+**Security Risk:** This approach has unfortunately led to supply
 chain attacks - more details on the `PyTorch Blog
 <https://pytorch.org/blog/compromised-nightly-dependency/>`__. It's a
 non-trivial problem to address which has forced the PyTorch team to
@@ -365,9 +365,9 @@ the version that the software will run against, which requires building
 without build isolation. On the project side, it requires hosting wheels
 separately.
 
-**Induced Security Risk:** Similar to regular source builds, this
+**Security Risk:** Similar to regular source builds, this
 model requires running arbitrary code at install time. The wheels
-are downloaded entirely outside package manager's control, extending
+are downloaded entirely outside the package manager's control, extending
 the attack surface to two separate wheel download implementations and
 preventing proper provenance tracking.