Reference the different possible values for push.recurseSubmodles

explicitly in each of their relevant sections

Author: constcuriosity

book/07-git-tools/sections/submodules.asc

@@ -518,6 +518,7 @@ to push them to a remote.
 
 As you can see, it also gives us some helpful advice on what we might want to do next.
 The simple option is to go into each submodule and manually push to the remotes to make sure they're externally available and then try this push again.
+If you want the check behavior to happen for all pushes, you can make this behavior the default by doing `git config push.recurseSubmodules check`.
 
 The other option is to use the ``on-demand'' value, which will try to do this for you.
 
@@ -543,8 +544,7 @@ To https://github.com/chaconinc/MainProject
 
 As you can see there, Git went into the DbConnector module and pushed it before pushing the main project.
 If that submodule push fails for some reason, the main project push will also fail.
-
-You can enable these behaviors for all future pushes with the `push.recurseSubmodules` config.
+You can make this behavior the default by doing `git config push.recurseSubmodules on-demand`.
 
 ===== Merging Submodule Changes