fix warnings

Author: rhansen

Doc/c-api/lifecycle.rst

@@ -42,7 +42,7 @@ Explanation:
   :c:member:`~PyTypeObject.tp_finalize` via
   :c:func:`PyObject_CallFinalizerFromDealloc` if it wishes to reuse that code to
   help with object destruction.  This is recommended because it guarantees that
-  :c:member:`tp_finalize` is always called before destruction.
+  :c:member:`!tp_finalize` is always called before destruction.
 * When :c:member:`~PyTypeObject.tp_dealloc` finishes object destruction, it
   directly calls :c:member:`~PyTypeObject.tp_free` to deallocate the memory.
 
@@ -103,7 +103,7 @@ longer isolated due to finalizer resurrection (see
 #. **Leaked:** If a cyclic isolate still exists after all objects in the group
    have been finalized and cleared, then the objects remain indefinitely
    uncollectable (see :data:`gc.garbage`).  It is a bug if a cyclic isolate
-   reaches this stage---it means the :c:member:`~PyTypeObjects.tp_clear` methods
+   reaches this stage---it means the :c:member:`~PyTypeObject.tp_clear` methods
    have failed to break the reference cycle as required.
 
 If :c:member:`~PyTypeObject.tp_clear` did not exist, then Python would have no

Doc/c-api/typeobj.rst

@@ -2022,7 +2022,7 @@ and :c:data:`PyType_Type` effectively act as defaults.)
    **Inheritance:**
 
    Static subtypes inherit this slot, which will be
-   :c:func:`PyType_GenericAlloc` if inherited from :c:data:`PyBaseObject_Type`.
+   :c:func:`PyType_GenericAlloc` if inherited from :class:`object`.
 
    Dynamic subtypes (created by a class statement) do not inherit this slot.
 
@@ -2085,11 +2085,11 @@ and :c:data:`PyType_Type` effectively act as defaults.)
    **Inheritance:**
 
    Static subtypes inherit this slot, which will be :c:func:`PyObject_Free` if
-   inherited from :c:data:`PyBaseObject_Type`.  Exception: If the type supports
-   garbage collection (i.e., the :c:macro:`Py_TPFLAGS_HAVE_GC` flag is set in
+   inherited from :class:`object`.  Exception: If the type supports garbage
+   collection (i.e., the :c:macro:`Py_TPFLAGS_HAVE_GC` flag is set in
    :c:member:`~PyTypeObject.tp_flags`) and it would inherit
-   :c:func:`PyObject_Free`, then this slot is not inherited but instead
-   defaults to :c:func:`PyObject_GC_Del`.
+   :c:func:`PyObject_Free`, then this slot is not inherited but instead defaults
+   to :c:func:`PyObject_GC_Del`.
 
    Dynamic subtypes (created by a class statement) do not inherit this slot.