Fix ModuleSpec.name reference, clarify why PyModule_Exec is still recommended

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BRMivCCCk5sjAJ6GmBEDUv

Author: itamaro

Doc/c-api/extension-modules.rst

@@ -328,8 +328,8 @@ in the following ways:
   tuple where:
 
   - *module_name* is the module's full dotted name, taken from
-    :py:attr:`~importlib.machinery.ModuleSpec`
-    (or similar argument to importing function).
+    :py:attr:`ModuleSpec.name <importlib.machinery.ModuleSpec.name>`
+    (or the equivalent argument of the importing function).
     Note that names that the initialization function uses to create the module
     (for example, :c:member:`PyModuleDef.m_name`) are not taken into account.
   - *file_name* is the extension's file name.

Doc/c-api/import.rst

@@ -434,7 +434,8 @@ Importing Modules
      contents instead of calling *initfunc* again.
    - The module will be fully initialized by *initfunc*.
      Calling :c:func:`PyModule_Exec` on it will have no effect, though it is
-     recommended (in case the module's implementation will change).
+     still recommended, in case the module later switches to
+     :ref:`multi-phase initialization <multi-phase-initialization>`.
    - Also, if the *spec*'s :py:attr:`!name` contains dots, this name is used
      for prepending a parent package to the new module's
      :attr:`~module.__name__`.