diff --git a/book/02-git-basics/sections/recording-changes.asc b/book/02-git-basics/sections/recording-changes.asc
index 54388f93f..d8a586ecf 100644
--- a/book/02-git-basics/sections/recording-changes.asc
+++ b/book/02-git-basics/sections/recording-changes.asc
@@ -27,7 +27,7 @@ If you run this command directly after a clone, you should see something like th
 $ git status
 On branch master
 Your branch is up-to-date with 'origin/master'.
-nothing to commit, working directory clean
+nothing to commit, working tree clean
 ----
 
 This means you have a clean working directory; in other words, none of your tracked files are modified.
diff --git a/book/02-git-basics/sections/remotes.asc b/book/02-git-basics/sections/remotes.asc
index b785ce4bb..85ab6c845 100644
--- a/book/02-git-basics/sections/remotes.asc
+++ b/book/02-git-basics/sections/remotes.asc
@@ -179,7 +179,7 @@ $ git remote show origin
 ----
 
 It lists the URL for the remote repository as well as the tracking branch information.
-The command helpfully tells you that if you're on the `master` branch and you run `git pull`, it will automatically merge in the `master` branch on the remote after it fetches all the remote references.
+The command helpfully tells you that if you're on the `master` branch and you run `git pull`, it will automatically merge the remote's `master` branch into the local one after it has been fetched.
 It also lists all the remote references it has pulled down.
 
 That is a simple example you're likely to encounter.