gh-140281: Doc: Update free-threading how-to

Author: Krishna-web-hub

Doc/howto/free-threading-python.rst

@@ -116,12 +116,12 @@ after the main thread is running.  The following objects are immortalized:
 * :ref:`classes <classes>` (type objects)
 
 Because immortal objects are never deallocated, applications that create many
-objects of these types may see increased memory usage.  This is expected to be
-addressed in the 3.14 release.
+objects of these types may see increased memory usage. Work to further reduce 
+this overhead continued in the 3.14 release.
 
 Additionally, numeric and string literals in the code as well as strings
-returned by :func:`sys.intern` are also immortalized.  This behavior is
-expected to remain in the 3.14 free-threaded build.
+returned by :func:`sys.intern` are also immortalized.  This behavior remains 
+in the 3.14 free-threaded build.
 
 
 Frame objects
@@ -152,9 +152,10 @@ Programs that spend most of their time in C extensions or I/O will see
 less of an impact.  The largest impact is because the specializing adaptive
 interpreter (:pep:`659`) is disabled in the free-threaded build.  We expect
 to re-enable it in a thread-safe way in the 3.14 release.  This overhead is
-expected to be reduced in upcoming Python release.   We are aiming for an
-overhead of 10% or less on the pyperformance suite compared to the default
-GIL-enabled build.
+expected to be reduced in upcoming Python release. This overhead **was reduced**
+in the 3.14 release. Reducing overhead further **remains an active development goal**,
+with an aim for 10% or less on the pyperformance suite compared to the default GIL-enabled 
+build. 
 
 
 Behavioral changes