Sep 23, 2024 · Sep 22, 2024 · Sep 23, 2024 · Sep 23, 2024
diff --git a/Doc/c-api/monitoring.rst b/Doc/c-api/monitoring.rst
 .. highlight:: c

 .._monitoring:
 .._c-api-monitoring:

 Monitoring C API
 ================
   to the base-2 logarithm of ``sys.monitoring.events.PY_START``.
   ``state_array`` is an array with a monitoring state entry for each event in
   ``event_types``, it is allocated by the user but populated by
 ``PyMonitoring_EnterScope`` with information about the activation state of
 :c:func:`!PyMonitoring_EnterScope` with information about the activation state of
   the event. The size of ``event_types`` (and hence also of ``state_array``)
   is given in ``length``.

   The ``version`` argument is a pointer to a value which should be allocated
   by the user together with ``state_array`` and initialized to 0,
   and then set only by``PyMonitoring_EnterScope`` itelf. It allows this
   and then set only by:c:func:`!PyMonitoring_EnterScope` itelf. It allows this
   function to determine whether event states have changed since the previous call,
   and to return quickly if they have not.

   The scopes referred to here are lexical scopes: a function, class or method.
 ``PyMonitoring_EnterScope`` should be called whenever the lexical scope is
 :c:func:`!PyMonitoring_EnterScope` should be called whenever the lexical scope is
   entered. Scopes can be reentered, reusing the same *state_array* and *version*,
   in situations like when emulating a recursive Python function. When a code-like's
   execution is paused, such as when emulating a generator, the scope needs to

 .. c:function:: int PyMonitoring_ExitScope(void)

   Exit the last scope that was entered with``PyMonitoring_EnterScope``.
   Exit the last scope that was entered with:c:func:`!PyMonitoring_EnterScope`.
diff --git a/Doc/c-api/time.rst b/Doc/c-api/time.rst
 .. highlight:: c

 .. _c-api-time:

 PyTime C API
 ============

diff --git a/Doc/library/sys.monitoring.rst b/Doc/library/sys.monitoring.rst
 Events can also be controlled on a per code object basis. The functions
 defined below which accept a :class:`types.CodeType` should be prepared
 to accept a look-alike object from functions which are not defined
 in Python (see :ref:`monitoring`).
 in Python (see :ref:`c-api-monitoring`).

 .. function:: get_local_events(tool_id: int, code: CodeType, /) -> int
Original file line number	Diff line number	Diff line change
		@@ -1,6 +1,6 @@
		.. highlight:: c

		.._monitoring:
		.._c-api-monitoring:

		Monitoring C API
		================
Expand DownExpand Up		@@ -141,18 +141,18 @@ would typically correspond to a python function.
		to the base-2 logarithm of ``sys.monitoring.events.PY_START``.
		``state_array`` is an array with a monitoring state entry for each event in
		``event_types``, it is allocated by the user but populated by
		``PyMonitoring_EnterScope`` with information about the activation state of
		:c:func:`!PyMonitoring_EnterScope` with information about the activation state of
		the event. The size of ``event_types`` (and hence also of ``state_array``)
		is given in ``length``.

		The ``version`` argument is a pointer to a value which should be allocated
		by the user together with ``state_array`` and initialized to 0,
		and then set only by``PyMonitoring_EnterScope`` itelf. It allows this
		and then set only by:c:func:`!PyMonitoring_EnterScope` itelf. It allows this
		function to determine whether event states have changed since the previous call,
		and to return quickly if they have not.

		The scopes referred to here are lexical scopes: a function, class or method.
		``PyMonitoring_EnterScope`` should be called whenever the lexical scope is
		:c:func:`!PyMonitoring_EnterScope` should be called whenever the lexical scope is
		entered. Scopes can be reentered, reusing the same state_array and version,
		in situations like when emulating a recursive Python function. When a code-like's
		execution is paused, such as when emulating a generator, the scope needs to
Expand DownExpand Up		@@ -189,4 +189,4 @@ would typically correspond to a python function.

		.. c:function:: int PyMonitoring_ExitScope(void)

		Exit the last scope that was entered with``PyMonitoring_EnterScope``.
		Exit the last scope that was entered with:c:func:`!PyMonitoring_EnterScope`.
Original file line number	Diff line number	Diff line change
		@@ -1,5 +1,7 @@
		.. highlight:: c

		.. _c-api-time:

		PyTime C API
		============

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -262,7 +262,7 @@ Per code object events
		Events can also be controlled on a per code object basis. The functions
		defined below which accept a :class:`types.CodeType` should be prepared
		to accept a look-alike object from functions which are not defined
		in Python (see :ref:`monitoring`).
		in Python (see :ref:`c-api-monitoring`).

		.. function:: get_local_events(tool_id: int, code: CodeType, /) -> int

Expand Down