Fixed typo: seperate to separate
Joel Clermont committed
Jul 11, 2010 at 01:13 UTC
e1d2f292b99ac7b6b63d6bb779f15ecabee3ac82
1 file changed
+3
-3
basic/index.html
+3
-3
@@ -518,11 +518,11 @@ Further paragraphs come after blank lines.
518
The commit message is very important. Since much of the power of
519
Git is this flexibility in carefully crafting commits locally and then
520
sharing them later, it is very powerful to be able to write three or
521
- four commits of logically seperate changes so that your work may be more
521
+ four commits of logically separate changes so that your work may be more
522
easily peer reviewed. Since there is a seperation between committing and
523
pushing those changes, do take the time to make it easier for the people
524
you are working with to see what you've done by putting each logically
525
- seperate change in a seperate commit with a nice commit message so it
525
+ separate change in a separate commit with a nice commit message so it
526
is easier for them to see what you are doing and why.</p>
527
528
<h4>
@@ -610,7 +610,7 @@ Further paragraphs come after blank lines.
610
<code>git reset HEAD -- file</code>. Technically here you don't have to
611
add the <code>--</code> - it is used to tell Git when you have stopped
612
listing options and are now listing file paths, but it's probably good to
613
- get into the habit of using it to seperate options from paths even if you
613
+ get into the habit of using it to separate options from paths even if you
614
don't need to.
615
</p>
616