address a couple more review comments

peps/pep-0733.rst

@@ -123,7 +123,7 @@ There are actions which are generic, and required by
 all types of API users:
 
 * Define functions and call them
-* Create classes and instantiate them
+* Define new types
 * Create instances of builtin and user-defined types
   and perform operations on them
 * Introspect objects, including types, instances, and functions
@@ -327,8 +327,8 @@ a C preprocessor/compiler rather than just a parser (such as macros)
 Furthermore, C header files tend to expose more than what is intended
 to be part of the public API
 [`Issue 34 <https://github.com/capi-workgroup/problems/issues/34>`__].
-In particular, implementation details such as the fields of C structs
-can be exposed
+In particular, implementation details such as the precise memory
+layouts of internal data structures can be exposed
 [`Issue 22 <https://github.com/capi-workgroup/problems/issues/22>`__
 and :pep:`620`].
 This can make API evolution very difficult, in particular when it