Skip to content

Commit 2e6ad36

Browse files
authored
Merge pull request #875 from rpjday/undoing
Standardize on " -- " to represent "em" dashes in "Undoing Things".
2 parents 1c5923f + 0b35fd2 commit 2e6ad36

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

book/02-git-basics/sections/undoing.asc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ $ git add forgotten_file
2929
$ git commit --amend
3030
----
3131

32-
You end up with a single commit the second commit replaces the results of the first.
32+
You end up with a single commit -- the second commit replaces the results of the first.
3333

3434
[NOTE]
3535
====
@@ -97,7 +97,7 @@ We'll go into much more detail about what `reset` does and how to master it to d
9797
==== Unmodifying a Modified File
9898

9999
What if you realize that you don't want to keep your changes to the `CONTRIBUTING.md` file?
100-
How can you easily unmodify it revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?
100+
How can you easily unmodify it -- revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?
101101
Luckily, `git status` tells you how to do that, too.
102102
In the last example output, the unstaged area looks like this:
103103

@@ -130,7 +130,7 @@ You can see that the changes have been reverted.
130130
[IMPORTANT]
131131
=====
132132
It's important to understand that `git checkout -- <file>` is a dangerous command.
133-
Any changes you made to that file are gone Git just copied another file over it.
133+
Any changes you made to that file are gone -- Git just copied another file over it.
134134
Don't ever use this command unless you absolutely know that you don't want the file.
135135
=====
136136

0 commit comments

Comments
 (0)