Skip to content

Commit eddf26e

Browse files
authored
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.
1 parent 8b6dc1a commit eddf26e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/02-git-basics/sections/recording-changes.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ index 0000000..03902a1
335335
----
336336

337337
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.
338-
This can be confusing, because if you've staged all of your changes, `git diff` will give you no output.
338+
If you've staged all of your changes, `git diff` will give you no output.
339339

340340
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.
341341
If our environment looks like this:

0 commit comments

Comments
 (0)