Docs: address review feedback on interned string immortality

Author: HernaniSamuel

Doc/c-api/unicode.rst

@@ -1750,11 +1750,12 @@ They all return ``NULL`` or ``-1`` if an exception occurs.
    :c:expr:`PyUnicode_CheckExact(*p_unicode)` must be true. If it is not,
    then -- as with any other error -- the argument is left unchanged.
 
-   Interned strings are not :term:`immortal`.
+   Strings interned by this function are not :term:`immortal`.
    You must keep a reference to the result to benefit from interning.
 
    .. note::
-      In the free-threaded build, all interned strings **are** :term:`immortal`.
+      On the :term:`free threaded` build, all interned strings are :term:`immortal`.
+      This may change in the future.
 
 .. c:function:: PyObject* PyUnicode_InternFromString(const char *str)
 

Doc/howto/free-threading-python.rst

@@ -99,7 +99,7 @@ This section describes known limitations of the free-threaded CPython build.
 Immortalization
 ---------------
 
-The free-threaded build introduces additional :term:`immortal` objects.
+On the free-threaded build, more objects are made immortal.
 Immortal objects are not deallocated and have reference counts that are
 never modified.  This is done to avoid reference count contention that would
 prevent efficient multi-threaded scaling.

Doc/library/sys.rst

@@ -1326,8 +1326,8 @@ always available. Unless explicitly noted otherwise, all variables are read-only
    return value of :func:`intern` around to benefit from it.
 
    .. note::
-
-      In the free-threaded build, all interned strings **are** :term:`immortal`.
+      On the :term:`free threaded` build, all interned strings are :term:`immortal`.
+      This may change in the future.
 
 .. function:: _is_gil_enabled()