Merge pull request #575 from YueLinHo/i553

Fix issue #553: Git does the checkout while cloning, not "you".
progit · Mar 22, 2016 · f3531c7 · f3531c7
2 parents 6054c33 + 7ca6f55
commit f3531c7
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/book/02-git-basics/sections/recording-changes.asc b/book/02-git-basics/sections/recording-changes.asc
@@ -6,7 +6,7 @@ You need to make some changes and commit snapshots of those changes into your re
 Remember that each file in your working directory can be in one of two states: tracked or untracked.
 Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged.
 Untracked files are everything else – any files in your working directory that were not in your last snapshot and are not in your staging area.
-When you first clone a repository, all of your files will be tracked and unmodified because you just checked them out and haven't edited anything.
+When you first clone a repository, all of your files will be tracked and unmodified because Git just checked them out and you haven't edited anything.
 
 As you edit files, Git sees them as modified, because you've changed them since your last commit.
 You stage these modified files and then commit all your staged changes, and the cycle repeats.