[3.12] gh-107298: Fix some references in the C API documentation (GH-108072) (#108074)

gh-107298: Fix some references in the C API documentation (GH-108072)
(cherry picked from commit f51f0466c07eabc6177c2f64f70c952dada050e8)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/Doc/extending/extending.rst b/Doc/extending/extending.rst
index 72e30a6..68f8e0c 100644
--- a/Doc/extending/extending.rst
+++ b/Doc/extending/extending.rst
@@ -242,7 +242,7 @@ needed to ensure that it will not be discarded, causing :c:data:`!SpamError` to
 become a dangling pointer. Should it become a dangling pointer, C code which
 raises the exception could cause a core dump or other unintended side effects.
 
-We discuss the use of ``PyMODINIT_FUNC`` as a function return type later in this
+We discuss the use of :c:macro:`PyMODINIT_FUNC` as a function return type later in this
 sample.
 
 The :exc:`!spam.error` exception can be raised in your extension module using a
@@ -363,7 +363,7 @@ only non-\ ``static`` item defined in the module file::
        return PyModule_Create(&spammodule);
    }
 
-Note that PyMODINIT_FUNC declares the function as ``PyObject *`` return type,
+Note that :c:macro:`PyMODINIT_FUNC` declares the function as ``PyObject *`` return type,
 declares any special linkage declarations required by the platform, and for C++
 declares the function as ``extern "C"``.