Apply suggestions from code review

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

Author: StanFromIreland

.github/CONTRIBUTING.md

@@ -18,10 +18,12 @@ Please be aware that our workflow does deviate slightly from the typical GitHub
 project. Details on how to properly submit a pull request are covered in
 [Lifecycle of a Pull Request](https://devguide.python.org/pullrequest/).
 We utilize various bots and status checks to help with this, so do follow the
-comments they leave and their "Details" links, respectively. A key point of
-our workflow that is not covered by a bot or status check is that all
-discussions that are not directly related to the code in the pull request
-should happen on the [issue tracker](https://devguide.python.org/tracker/).
+comments they leave and their "Details" links, respectively.
+
+The final key part of our workflow is that all discussions that are not
+directly related to the code in the pull request should happen on the
+[issue tracker](https://devguide.python.org/tracker/), generally in the
+pull request's parent issue.
 
 
 ## Setting Expectations

getting-started/git-boot-camp.rst

@@ -611,7 +611,7 @@ When a pull request submitter has enabled the `Allow edits from maintainers`_
 option, Python Core Developers may decide to make any remaining edits needed
 prior to merging themselves, rather than asking the submitter to do them. This
 can be particularly appropriate when the remaining changes are bookkeeping
-items.
+items like updating a news entry.
 
 .. _Allow edits from maintainers: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork