Merge pull request #1327 from agdillon/typos

fix typos

Author: jnavila

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

@@ -376,7 +376,7 @@ Submodule DbConnector c3f01dc..c87d55d:
 Git will by default try to update *all* of your submodules when you run `git submodule update --remote` so if you have a lot of them, you may want to pass the name of just the submodule you want to try to update.
 
 ===== Pulling Upstream Changes from the Project Remote
-Let's now step into the shoes of your collaborator, who has his own local clone of the the MainProject repository.
+Let's now step into the shoes of your collaborator, who has his own local clone of the MainProject repository.
 Simply executing `git pull` to get your newly committed changes is not enough:
 
 [source,console]
@@ -952,7 +952,7 @@ Your branch is up-to-date with 'origin/master'.
 nothing to commit, working tree clean
 ----
 
-Using the the `--recurse-submodules` flag of `git checkout` can also be useful when you work on several branches in the superproject, each having your submodule pointing at different commits.
+Using the `--recurse-submodules` flag of `git checkout` can also be useful when you work on several branches in the superproject, each having your submodule pointing at different commits.
 Indeed, if you switch between branches that record the submodule at different commits, upon executing `git status` the submodule will appear as ``modified'', and indicate ``new commits''. That is because the submodule state is by default not carried over when switching branches.
 
 This can be really confusing, so it's a good idea to always `git checkout --recurse-submodules` when your project has submodules.