Improve 3.14 whatsnew about reference counting changes.

Author: ZeroIntensity

Doc/whatsnew/3.14.rst

@@ -3046,10 +3046,12 @@ Porting to Python 3.14
 * The interpreter internally avoids some reference count modifications when
   loading objects onto the operands stack by :term:`borrowing <borrowed reference>`
   references when possible. This can lead to smaller reference count values
-  compared to previous Python versions. C API extensions that checked
-  :c:func:`Py_REFCNT` of ``1`` to determine if an function argument is not
-  referenced by any other code should instead use
-  :c:func:`PyUnstable_Object_IsUniqueReferencedTemporary` as a safer replacement.
+  compared to previous Python versions, because the creation of :term:`strong
+  references <strong reference>` is avoided in the Python interpreter. This
+  generally does not affect existing code, but C API extensions that checked
+  :c:func:`Py_REFCNT` of ``1`` to determine if an object is not referenced by
+  any other code should instead use :c:func:`PyUnstable_Object_IsUniqueReferencedTemporary`
+  as a safer replacement.
 
 
 * Private functions promoted to public C APIs: