Shorten the regrtest loading description and fix the reap_children wording.

Author: bazhil

Doc/library/test.rst

@@ -167,13 +167,11 @@ test.regrtest` used in previous Python versions still works.  Running the
 script by itself automatically starts running all regression tests in the
 :mod:`!test` package. It does this by finding modules and packages whose names
 start with ``test_``, importing each one, and loading its tests with
-:meth:`unittest.TestLoader.loadTestsFromModule`. The loader collects
-:class:`unittest.TestCase` tests defined in the module. If the module defines
-``load_tests``, the loader calls it with that suite and runs the suite the
-function returns. Test packages use ``load_tests``, often via
-:func:`test.support.load_package_tests`, to add tests discovered in
-submodules. A module-level ``test_main()`` function is not called. If a test
-module defines ``test_main``, :mod:`!test.regrtest` fails that test. The names of
+:meth:`unittest.TestLoader.loadTestsFromModule`. See the
+:ref:`load_tests protocol <load_tests-protocol>` for how a module or package
+can customize what is loaded. A module-level ``test_main()`` function is not
+called. If a test module defines ``test_main``, :mod:`!test.regrtest` fails
+that test. The names of
 tests to execute may also be passed to the script. Specifying a single
 regression test (:program:`python -m test test_spam`) will minimize output and
 only print whether the test passed or failed.
@@ -888,7 +886,7 @@ The :mod:`!test.support` module defines the following functions:
 .. function:: reap_children()
 
    Call this from a test's :meth:`~unittest.TestCase.setUp`,
-   :meth:`~unittest.TestCase.tearDown`, or from ``tearDownModule`` when the
+   :meth:`~unittest.TestCase.tearDown`, or ``tearDownModule`` when the
    test starts subprocesses.  This will help ensure that no extra children
    (zombies) stick around to hog resources and create problems when looking
    for refleaks.