Improve text of bullet items

Co-authored-by: Ben Straub <[email protected]>

Author: HonkingGoose

book/03-git-branching/sections/branch-management.asc

@@ -168,13 +168,12 @@ But the remote still has a _master_ branch.
 Other collaborators will continue to use the _master_ branch as the base of their work, until you make some further changes.
 
 Now you have a few more tasks in front of you to complete the transition:
-* Project dependency update helper configuration files.
-* Test runner configuration files.
-* Build scripts.
-* Release scripts.
-* Repository configuration settings (like the default branch that is targeted for pull-requests, branch-protection measures, etc).
-* References to the old branch in documentation.
-* Close/merge pull requests that target the old branch
+* Any projects that depend on this one will need to update their code and/or configuration.
+* Update any test-runner configuration files.
+* Adjust build and release scripts.
+* Redirect settings on your repo host for things like thee repo's default branch, merge rules, and other things that match branch names.
+* Update references to the old branch in documentation.
+* Close or merge any pull requests that target the old branch.
 
 After you've done all these tasks, and are certain the main branch performs just as the _master_ branch, you can delete the _master_ branch:
 [source, console]