Some rewording.

Author: ZeroIntensity

peps/pep-0797.rst

@@ -31,14 +31,14 @@ For example::
 Background
 ==========
 
-At the C level, all objects in Python's C API are interacted with through their
-type (a pointer to a :c:type:`PyTypeObject`). For example, to call an object,
+At the C level, Python interacts with objects through their
+type (:c:member:`~PyObject.ob_type`). For example, to call an object,
 the interpreter will access the :c:member:`~PyTypeObject.tp_call` field on the
 object's type. This is where the magic of a shared object proxy can happen.
 
 The :c:type:`!PyTypeObject` for a shared object proxy must implement
 wrapping behavior for every single field on the type object structure.
-So, going back to ``tp_call``, an object proxy must be able to "intercept" the
+So, for ``tp_call``, an object proxy must be able to "intercept" the
 call in such a way where the wrapped object's ``tp_call`` slot can be executed
 without thread-safety issues. This is done by switching the
 :term:`attached thread state`.