Lint docs v9

Author: eduardo-elizondo

Misc/NEWS.d/next/Core and Builtins/2024-01-15-18-11-48.gh-issue-113190.OwQX64.rst

@@ -7,14 +7,14 @@ Worth noting that if an extension accidentally holds onto a interned string,
 event after calling Py_Finalize, it will result in use-after-free error,
 leaving the user to a potential vulnerabilities. That said, the history of
 how these interned strings are handled have been changing during throughout
-different versions. For example:
+different versions.
 
-*   In Python 3.9 and older, interned strings were never deleted. Only special
-build for Valgrind and Purity cleared them at exit.
-*   In Python 3.10 and 3.11, interned strings are always deleted at exit.
-*   In Python 3.12, interned strings are deleted only if Python is built in
-debug mode: they are not deleted in release mode.
-*   In Python 3.13, interned strings will now be akll deleted.
+For example, in Python 3.9 and older, interned strings were never deleted.
+Only special builds for Valgrind and Purity cleared them at exit. In Python
+3.10 and 3.11, interned strings are always deleted at exit. In Python 3.12,
+interned strings are deleted only if Python is built in debug mode: they
+are not deleted in release mode. In Python 3.13, interned strings will
+now be all deleted.
 
-Given how we've changed guarantees throughout different versions, we do not
-expect that users actively rely on this behavior for their extensions.
+Given how the guarantees changed throughout different versions, it is not
+expected that users actively rely on this behavior for their extensions.