gh-1448: Revise typo fixes section for clarity

- Clarify which directories are appropriate for typo fixes
- Encourage small, focused PRs to reduce reviewer notification burden
- Explicitly note that large PRs or PRs outside listed directories
  may be closed with a reference to this section

Author: johnslavik

getting-started/pull-request-lifecycle.rst

@@ -265,20 +265,18 @@ See also `python/cpython#126133
 Typo fixes
 ==========
 
-Fixing typos and grammatical errors is a welcome contribution. The most
-appropriate places for such fixes are:
+Fixing typos and grammatical errors in documentation is a welcome
+contribution. The most appropriate places for such fixes are:
 
 * The ``Doc/`` directory (end-user documentation)
 * Internal documentation, such as files in ``Misc/``
 * News entries under ``Misc/NEWS.d/``
 
-Typo fixes in source code docstrings and comments are also acceptable.
-
-When submitting typo fixes, keep PRs **small and focused** — ideally one file
-or a small set of closely related files. Large PRs that touch many unrelated
-files across the repository create a significant review and notification burden
-on maintainers, making them harder to process. Such PRs may be closed, and
-contributors will be asked to resubmit as smaller, focused PRs.
+Keep typo-fix PRs **small and focused**, ideally limited to one file or a
+small set of closely related files. Large PRs that touch many unrelated files
+notify a large number of reviewers unnecessarily and are harder to review.
+Large typo-fix PRs, or PRs touching directories outside those listed above,
+may be closed with a reference to this section.
 
 
 .. _patchcheck: