From eddf26e732c1f6bdae7788265dde1267b29ce8eb Mon Sep 17 00:00:00 2001 From: Guthrie McAfee Armstrong Date: Mon, 6 Nov 2017 12:37:19 -0500 Subject: [PATCH] Remove "this can be confusing, because" The sentence "If you've staged all of your changes, `git diff` will give you no output." sounds nice by itself, and treats the behavior as a feature to be expected rather than a complication. --- book/02-git-basics/sections/recording-changes.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/02-git-basics/sections/recording-changes.asc b/book/02-git-basics/sections/recording-changes.asc index a7f194eba..52e290ee9 100644 --- a/book/02-git-basics/sections/recording-changes.asc +++ b/book/02-git-basics/sections/recording-changes.asc @@ -335,7 +335,7 @@ index 0000000..03902a1 ---- It's important to note that `git diff` by itself doesn't show all changes made since your last commit -- only changes that are still unstaged. -This can be confusing, because if you've staged all of your changes, `git diff` will give you no output. +If you've staged all of your changes, `git diff` will give you no output. For another example, if you stage the `CONTRIBUTING.md` file and then edit it, you can use `git diff` to see the changes in the file that are staged and the changes that are unstaged. If our environment looks like this: