diff --git a/Doc/c-api/import.rst b/Doc/c-api/import.rst
@@ -283,23 +283,25 @@ Importing Modules

.. c:struct:: _inittab

-   Structure describing a single entry in the list of built-in modules.  Each of
-   these structures gives the name and initialization function for a module built
-   into the interpreter.  The name is an ASCII encoded string.  Programs which
   embed Python may use an array of these structures in conjunction with
   :c:func:`PyImport_ExtendInittab` to provide additional built-in modules.
-   The structure is defined in :file:`Include/import.h` as::

-      struct _inittab {
-          const char *name;           /* ASCII encoded string */
-          PyObject* (*initfunc)(void);
-      };


.. c:function:: int PyImport_ExtendInittab(struct _inittab *newtab)

   Add a collection of modules to the table of built-in modules.  The *newtab*
-   array must end with a sentinel entry which contains ``NULL`` for the :attr:`name`
   field; failure to provide the sentinel value can result in a memory fault.
   Returns ``0`` on success or ``-1`` if insufficient memory could be allocated to
   extend the internal table.  In the event of failure, no modules are added to the

diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
@@ -914,8 +914,11 @@ code, or when embedding the Python interpreter:
.. c:type:: PyThreadState

   This data structure represents the state of a single thread.  The only public
-   data member is :attr:`interp` (:c:expr:`PyInterpreterState *`), which points to
-   this thread's interpreter state.


.. c:function:: void PyEval_InitThreads()

diff --git a/Doc/c-api/structures.rst b/Doc/c-api/structures.rst
@@ -34,7 +34,7 @@ the definition of all other Python objects.

.. c:type:: PyVarObject

-   This is an extension of :c:type:`PyObject` that adds the :attr:`ob_size`
   field.  This is only used for objects that have some notion of *length*.
   This type does not often appear in the Python/C API.
   Access to the members must be done by using the macros
@@ -171,7 +171,7 @@ the definition of all other Python objects.
.. c:macro:: PyVarObject_HEAD_INIT(type, size)

   This is a macro which expands to initialization values for a new
-   :c:type:`PyVarObject` type, including the :attr:`ob_size` field.
   This macro expands to::

      _PyObject_EXTRA_INIT
@@ -247,21 +247,21 @@ Implementing functions and methods
   Structure used to describe a method of an extension type.  This structure has
   four fields:

-   .. c:member:: const char* ml_name

-      name of the method

   .. c:member:: PyCFunction ml_meth

-      pointer to the C implementation

   .. c:member:: int ml_flags

-      flags bits indicating how the call should be constructed

-   .. c:member:: const char* ml_doc

-      points to the contents of the docstring

The :c:member:`~PyMethodDef.ml_meth` is a C function pointer.
The functions may be of different

diff --git a/Doc/c-api/tuple.rst b/Doc/c-api/tuple.rst
@@ -164,7 +164,8 @@ type.

   Describes a field of a struct sequence. As a struct sequence is modeled as a
   tuple, all fields are typed as :c:expr:`PyObject*`.  The index in the
-   :attr:`fields` array of the :c:type:`PyStructSequence_Desc` determines which
   field of the struct sequence is described.

   +-----------+------------------+-----------------------------------------+

diff --git a/Doc/extending/newtypes_tutorial.rst b/Doc/extending/newtypes_tutorial.rst
@@ -176,8 +176,8 @@ Everything else in the file should be familiar, except for some code in
   if (PyType_Ready(&CustomType) < 0)
       return;

-This initializes the :class:`Custom` type, filling in a number of members
-to the appropriate default values, including :attr:`ob_type` that we initially
set to ``NULL``. ::

   Py_INCREF(&CustomType);

diff --git a/Doc/whatsnew/2.5.rst b/Doc/whatsnew/2.5.rst
@@ -954,7 +954,7 @@ The return value must be either a Python integer or long integer. The
interpreter will check that the type returned is correct, and raises a
:exc:`TypeError` if this requirement isn't met.

-A corresponding :attr:`nb_index` slot was added to the C-level
:c:type:`PyNumberMethods` structure to let C extensions implement this protocol.
``PyNumber_Index(obj)`` can be used in extension code to call the
:meth:`__index__` function and retrieve its result.