Remove more references to PyPy 5.7 and 5.9 in the docs

Author: YannickJadoul

docs/advanced/misc.rst

@@ -223,7 +223,7 @@ avoids this issue involves weak reference with a cleanup callback:
 
 .. code-block:: cpp
 
-    // Register a callback function that is invoked when the BaseClass object is colelcted
+    // Register a callback function that is invoked when the BaseClass object is collected
     py::cpp_function cleanup_callback(
         [](py::handle weakref) {
             // perform cleanup here -- this function is called with the GIL held
@@ -237,9 +237,9 @@ avoids this issue involves weak reference with a cleanup callback:
 
 .. note::
 
-    PyPy (at least version 5.9) does not garbage collect objects when the
-    interpreter exits. An alternative approach (which also works on CPython) is to use
-    the :py:mod:`atexit` module [#f7]_, for example:
+    PyPy does not garbage collect objects when the interpreter exits. An alternative
+    approach (which also works on CPython) is to use the :py:mod:`atexit` module [#f7]_,
+    for example:
 
     .. code-block:: cpp
 

docs/intro.rst

@@ -20,7 +20,7 @@ become an excessively large and unnecessary dependency.
 Think of this library as a tiny self-contained version of Boost.Python with
 everything stripped away that isn't relevant for binding generation. Without
 comments, the core header files only require ~4K lines of code and depend on
-Python (2.7 or 3.x, or PyPy2.7 >= 5.7) and the C++ standard library. This
+Python (2.7 or 3.x, or PyPy2.7 >= 7.3) and the C++ standard library. This
 compact implementation was possible thanks to some of the new C++11 language
 features (specifically: tuples, lambda functions and variadic templates). Since
 its creation, this library has grown beyond Boost.Python in many ways, leading
@@ -49,7 +49,7 @@ Goodies
 *******
 In addition to the core functionality, pybind11 provides some extra goodies:
 
-- Python 2.7, 3.x, and PyPy (PyPy2.7 >= 5.7) are supported with an
+- Python 2.7, 3.x, and PyPy (PyPy2.7 >= 7.3) are supported with an
   implementation-agnostic interface.
 
 - It is possible to bind C++11 lambda functions with captured variables. The