Apply suggestions from code review

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

Author: encukou

peps/pep-0793.rst

@@ -27,7 +27,7 @@ To make this viable, we also specify new module slot types to replace
 We also add an API for defining modules from slots dynamically.
 
 The existing API (``PyInit_*``) is soft-deprecated.
-(That is: it will continue to work without warnings, and it'll fe fully
+(That is: it will continue to work without warnings, and it'll be fully
 documented and supported, but we plan to not add any new features to it.)
 
 
@@ -289,7 +289,7 @@ If specified, using a new ``Py_mod_token`` slot, the module token must:
 
 (Typically, it should point to a static constant.)
 
-When the address of a ``PyModuleDef`` is used as as a module's token,
+When the address of a ``PyModuleDef`` is used as a module's token,
 the module should behave as if it was created from that ``PyModuleDef``.
 In particular, the module state must have matching layout and semantics.
 
@@ -429,7 +429,7 @@ module, so this should not be considered a breaking change.
 
 Similarly, the ``PyType_GetModuleByDef`` function may stop matching modules
 whose definition changed. Module authors may avoid this by explicitly
-explicitly setting a *def* as the *token*.
+setting a *def* as the *token*.
 
 ``PyType_GetModuleByDef`` will now accept a module token as the *def* argument.
 We specify a suitable restriction on using ``PyModuleDef`` addresses as tokens,
@@ -478,13 +478,13 @@ wrappers, the :ref:`pep793-shim` below may be more useful.
      ``PyModuleDef`` structure.
 
 #. Optionally, scan your code for uses of ``PyType_GetModuleByDef``,
-   and replace them by ``PyType_GetModuleByToken``.
+   and replace them with ``PyType_GetModuleByToken``.
    Later in this guide, you'll set the token to *be* the existing
    ``PyModuleDef`` structure.
 
    (You may skip this step if targetting Python versions that don't expose
    ``PyType_GetModuleByToken``, since ``PyType_GetModuleByDef`` is
-   backwards-compatible. )
+   backwards-compatible.)
 
 #. Look at the function identified by ``Py_mod_create``, if any.
    Make sure that it does not use its second argument (``PyModuleDef``),
@@ -550,7 +550,7 @@ Once your module no longer supports lower versions:
 
 #. If the existing ``PyModuleDef`` struct is used *only* for ``Py_mod_token``
    and/or ``PyType_GetModuleByToken``, you may remove the ``Py_mod_token``
-   line and replace ``&your_module_def`` by ``module_slots`` everywhere else.
+   line and replace ``&your_module_def`` with ``module_slots`` everywhere else.
 
 #. Delete any unused data.
    The ``PyModuleDef`` struct and the original slots array are likely to be
@@ -562,7 +562,7 @@ Once your module no longer supports lower versions:
 Backwards compatibility shim
 ----------------------------
 
-It is possible to write generic function that implements the “old” export
+It is possible to write a generic function that implements the “old” export
 hook (``PyInit_``) in terms of the API proposed here.
 
 The following implementation can be copied and pasted to a project; only the
@@ -589,7 +589,7 @@ This implementation places a few additional requirements on the slots array:
 - Any ``Py_mod_token`` must be set to ``&module_def_and_token``, defined here.
 
 It also passes ``NULL`` as *spec* to the ``PyModExport`` export hook.
-A proper implementation would pass ``None`` instead, .
+A proper implementation would pass ``None`` instead.
 
 .. literalinclude:: pep-0793/shim.c
    :language: c
@@ -653,7 +653,6 @@ Possible Future Directions
 
 These ideas are out of scope for *this* proposal.
 
-
 Improving slots in general
 --------------------------