bpo-41455: Provide a link to how the third generation is collected in the GC docs...

Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
(cherry picked from commit 82ca8fada15b121866530f2cdac1b7055be4a244)

Co-authored-by: Yaroslav Pankovych <31005942+P-Alban@users.noreply.github.com>

diff --git a/Doc/library/gc.rst b/Doc/library/gc.rst
index 13eda917b9a801522e2af51e7fa59e1e5985f25d..adaa30295b5e8b0da82d94ce78be2dd777f11dab 100644 (file)
--- a/Doc/library/gc.rst
+++ b/Doc/library/gc.rst
@@ -106,9 +106,9 @@ The :mod:`gc` module provides the following functions:
    allocations minus the number of deallocations exceeds *threshold0*, collection
    starts.  Initially only generation ``0`` is examined.  If generation ``0`` has
    been examined more than *threshold1* times since generation ``1`` has been
-   examined, then generation ``1`` is examined as well.  Similarly, *threshold2*
-   controls the number of collections of generation ``1`` before collecting
-   generation ``2``.
+   examined, then generation ``1`` is examined as well.
+   With the third generation, things are a bit more complicated,
+   see `Collecting the oldest generation <https://devguide.python.org/garbage_collector/#collecting-the-oldest-generation>`_ for more information.
 
 
 .. function:: get_count()