Lint fixes

Author: zooba

.github/CODEOWNERS

@@ -680,6 +680,7 @@ peps/pep-0801.rst  @warsaw
 peps/pep-0802.rst  @AA-Turner
 peps/pep-0803.rst  @encukou
 peps/pep-0804.rst  @pradyunsg
+peps/pep-0809.rst  @zooba
 # ...
 peps/pep-2026.rst  @hugovk
 # ...

peps/pep-0809.rst

@@ -237,7 +237,7 @@ For example, if a new API were to be added during ``abi2026``'s life that allows
 more efficient access to an ``int`` object's internal data, rather than adding a
 new API, we would create a new interface: a struct containing a function pointer
 to copy the data to a new location, and a previously unused index/name for that
-interface. The caller can call ``PyObject_GetInterface(int_object, &intf_struct)`` 
+interface. The caller can call ``PyObject_GetInterface(int_object, &intf_struct)``
 first; if it succeeds, call (a hypothetical)
 ``(*intf_struct.copy_bits)(&intf_struct, dest, sizeof(dest))``; if it fails,
 they can use ``PyObject_CallMethod(int_object, "to_bytes", ...)`` to perform the
@@ -248,9 +248,10 @@ single extension module that is binary compatible with *all* releases supporting
 Overview complete, here is the full specification of each new API:
 
 .. code-block:: c
+
    // Abstract API to request an interface for an object (or type).
    PyAPI_FUNC(int) PyObject_GetInterface(PyObject *obj, void *intf);
-   
+
    // API to release an interface.
    PyAPI_FUNC(int) PyInterface_Release(void *intf);
 
@@ -268,7 +269,7 @@ Overview complete, here is the full specification of each new API:
        // Should only be invoked by PyInterface_Release(), not directly.
        int (*release)(struct PyInterface_Base *intf);
    } PyInterface_Base;
-   
+
    // Type slot definition for PyTypeObject field.
    typedef int (*Py_getinterfacefunc)(PyObject *o, PyInterface_Base *intf);