summaryrefslogtreecommitdiff
path: root/Documentation/tutorial-2.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/tutorial-2.txt')
-rw-r--r--Documentation/tutorial-2.txt15
1 files changed, 7 insertions, 8 deletions
diff --git a/Documentation/tutorial-2.txt b/Documentation/tutorial-2.txt
index f363d17f0b..8d89992712 100644
--- a/Documentation/tutorial-2.txt
+++ b/Documentation/tutorial-2.txt
@@ -352,24 +352,23 @@ situation:
------------------------------------------------
$ git status
-#
-# Added but not yet committed:
-# (will commit)
+# On branch master
+# Changes to be committed:
+# (use "git reset HEAD <file>..." to unstage)
#
# new file: closing.txt
#
-#
-# Changed but not added:
-# (use "git add file1 file2" to include for commit)
+# Changed but not updated:
+# (use "git add <file>..." to update what will be committed)
#
# modified: file.txt
#
------------------------------------------------
Since the current state of closing.txt is cached in the index file,
-it is listed as "added but not yet committed". Since file.txt has
+it is listed as "Changes to be committed". Since file.txt has
changes in the working directory that aren't reflected in the index,
-it is marked "changed but not added". At this point, running "git
+it is marked "changed but not updated". At this point, running "git
commit" would create a commit that added closing.txt (with its new
contents), but that didn't modify file.txt.