Apply suggestions from code review

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: ngoldbaum

peps/pep-0803.rst

@@ -100,13 +100,13 @@ somewhat unusual in that they ship 14 wheels each for both the ``cp38`` and
 ``cp311`` stable ABIs to enable optimizations available in newer limited API
 versions. They also ship 14 additional ``cp314t`` wheels and 6 wheels for
 pypy. If there is no free-threaded stable ABI, then with Python 3.15,
-cryptography will be using roughtly the same amount of space on PyPI to support
+cryptography will be using roughly the same amount of space on PyPI to support
 two versions of the free-threaded build as *all* non-EOL versions of the
 GIL-enabled build.
 
 Cryptography maintainer Alex Gaynor `expressed a desire
 <https://discuss.python.org/t/making-pyobject-opaque-in-the-limited-api/77206/2>`_
-on discourse for a free-threaded stable ABI:
+on Discourse for a free-threaded stable ABI:
 
     Just to state this explicitly from the PyCA maintainers perspective, as
     long as we have O(1) builds, that’s ok. What we can’t/won’t do is O(n)
@@ -166,7 +166,7 @@ ABI on the free-threaded build they can use to ship wheels and reduce their
 maintenance burden.
 
 
-Bindings Generators
+Bindings generators
 -------------------
 
 Both moocore and cryptography use bindings generators to interface with the C
@@ -184,7 +184,7 @@ for an ``abi3.abi3t`` tag.
 Cython maintainer David Woods `says
 <https://github.com/cython/cython/issues/7399#issuecomment-3947605797>`_:
 
-    Cython is doesn't have huge problems with the number of wheels we distribute
+    Cython doesn't have huge problems with the number of wheels we distribute
     because ultimately it works fine as pure-Python. We do distribute wheels for
     a few of the smaller platforms as Stable ABI wheels but that's more
     "dogfooding" than because we actually need to. So I'm adding this in