Update Doc/c-api/memory.rst

Co-authored-by: Peter Bierma <[email protected]>

Author: corona10

Doc/c-api/memory.rst

@@ -108,7 +108,7 @@ belonging to a given domain for only the purposes hinted by that domain.
 (although this is the recommended practice). For example, one could use the memory
 returned by :c:func:`PyMem_RawMalloc` for allocating Python objects or the memory
 returned by :c:func:`PyObject_Malloc` for allocating memory for buffers.
-However, in the free-threaded build, Python objects must be allocated through :c:func:`PyObject_Malloc`.
+However, in the free-threaded build, Python objects *must* be allocated through :c:func:`PyObject_Malloc`.
 Non-Python objects must not be allocated this function, for example, it is currently acceptable to
 allocate buffers(non-Python objects) through :c:func:`PyObject_Malloc`; that will no longer be allowed
 and buffers should instead be allocated through :c:func:`PyMem_Malloc`, :c:func:`PyMem_RawMalloc`, or :c:func:`malloc`.