1
0

Fixed typo: seperate to separate

This commit is contained in:
Joel Clermont 2010-07-11 01:13:01 +08:00 committed by Scott Chacon
parent e105f0b29e
commit e1d2f292b9

View File

@ -518,11 +518,11 @@ Further paragraphs come after blank lines.
The commit message is very important. Since much of the power of
Git is this flexibility in carefully crafting commits locally and then
sharing them later, it is very powerful to be able to write three or
four commits of logically seperate changes so that your work may be more
four commits of logically separate changes so that your work may be more
easily peer reviewed. Since there is a seperation between committing and
pushing those changes, do take the time to make it easier for the people
you are working with to see what you've done by putting each logically
seperate change in a seperate commit with a nice commit message so it
separate change in a separate commit with a nice commit message so it
is easier for them to see what you are doing and why.</p>
<h4>
@ -610,7 +610,7 @@ Further paragraphs come after blank lines.
<code>git reset HEAD -- file</code>. Technically here you don't have to
add the <code>--</code> - it is used to tell Git when you have stopped
listing options and are now listing file paths, but it's probably good to
get into the habit of using it to seperate options from paths even if you
get into the habit of using it to separate options from paths even if you
don't need to.
</p>