Fix some documentation typos and grammar
Also suggest user manual mention .gitignore. Signed-off-by: Michael Coleman <tutufan@gmail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
Mike Coleman committed
Feb 2, 2007 at 00:25 UTC
aacd404e775ad73188ae9157041d7cc530d5625c
2 files changed
+8
-6
Documentation/core-tutorial.txt
+3
-3
@@ -624,7 +624,7 @@ name for the state at that point.
624
Copying repositories
625
--------------------
626
627
-git repositories are normally totally self-sufficient and relocatable
627
+git repositories are normally totally self-sufficient and relocatable.
628
Unlike CVS, for example, there is no separate notion of
629
"repository" and "working tree". A git repository normally *is* the
630
working tree, with the local git information hidden in the `.git`
@@ -1118,7 +1118,7 @@ You could do without using any branches at all, by
1118
keeping as many local repositories as you would like to have
1119
branches, and merging between them with `git pull`, just like
1120
you merge between branches. The advantage of this approach is
1121
-that it lets you keep set of files for each `branch` checked
1121
+that it lets you keep a set of files for each `branch` checked
1122
out and you may find it easier to switch back and forth if you
1123
juggle multiple lines of development simultaneously. Of
1124
course, you will pay the price of more disk usage to hold
@@ -1300,7 +1300,7 @@ differences since stage 2 (i.e. your version).
1300
Publishing your work
1301
--------------------
1302
1303
-So we can use somebody else's work from a remote repository; but
1303
+So, we can use somebody else's work from a remote repository, but
1304
how can *you* prepare a repository to let other people pull from
1305
it?
1306
Documentation/user-manual.txt
+5
-3
@@ -398,7 +398,7 @@ branch name, but this longer name can also be useful. Most
398
importantly, it is a globally unique name for this commit: so if you
399
tell somebody else the object name (for example in email), then you are
400
guaranteed that name will refer to the same commit in their repository
401
-that you it does in yours (assuming their repository has that commit at
401
+that it does in yours (assuming their repository has that commit at
402
all).
403
404
Understanding history: commits, parents, and reachability
@@ -617,7 +617,7 @@ the relationships between these snapshots.
617
Git provides extremely flexible and fast tools for exploring the
618
history of a project.
619
620
-We start with one specialized tool which is useful for finding the
620
+We start with one specialized tool that is useful for finding the
621
commit that introduced a bug into a project.
622
623
How to use bisect to find a regression
@@ -1492,7 +1492,7 @@ dangling commit 13472b7c4b80851a1bc551779171dcb03655e9b5
1492
...
1493
-------------------------------------------------
1494
1495
-and watch for output that mentions "dangling commits". You can examine
1495
+You can examine
1496
one of those dangling commits with, for example,
1497
1498
------------------------------------------------
@@ -2923,6 +2923,8 @@ Think about how to create a clear chapter dependency graph that will
2923
allow people to get to important topics without necessarily reading
2924
everything in between.
2925
2926
+Say something about .gitignore.
2927
+
2928
Scan Documentation/ for other stuff left out; in particular:
2929
howto's
2930
some of technical/?