Clarify that PyErr_NewException creates an exception *class*, not instance.

diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst
index 4c946c1d6ae05d1e1e5e345ce705102b779d6a71..6f13c8035a0f26b1401293668eb6c49292003e03 100644 (file)
--- a/Doc/c-api/exceptions.rst
+++ b/Doc/c-api/exceptions.rst
@@ -354,10 +354,10 @@ in various ways.  There is a separate error indicator for each thread.
 
 .. c:function:: PyObject* PyErr_NewException(char *name, PyObject *base, PyObject *dict)
 
-   This utility function creates and returns a new exception object. The *name*
+   This utility function creates and returns a new exception class. The *name*
    argument must be the name of the new exception, a C string of the form
-   ``module.class``.  The *base* and *dict* arguments are normally *NULL*.  This
-   creates a class object derived from :exc:`Exception` (accessible in C as
+   ``module.classname``.  The *base* and *dict* arguments are normally *NULL*.
+   This creates a class object derived from :exc:`Exception` (accessible in C as
    :c:data:`PyExc_Exception`).
 
    The :attr:`__module__` attribute of the new class is set to the first part (up