summaryrefslogtreecommitdiffstats
path: root/user-manual.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-02-04 08:32:04 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-02-04 08:32:04 +0000
commitee1e428396a619659999df3e609e3d689173aaf5 (patch)
tree4887669f14cd36b9ffe70f49d535d3b4b1426284 /user-manual.txt
parent8a66a65638e314180d1e8aa89b35544b1800dc87 (diff)
downloadgit-htmldocs-ee1e428396a619659999df3e609e3d689173aaf5.tar.gz
Autogenerated HTML docs for v1.5.0-rc3-39-gec804
Diffstat (limited to 'user-manual.txt')
-rw-r--r--user-manual.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/user-manual.txt b/user-manual.txt
index 6576625fa..c5e9ea8a4 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -425,8 +425,8 @@ if commit X is an ancestor of commit Y. Equivalently, you could say
that Y is a descendent of X, or that there is a chain of parents
leading from commit Y to commit X.
-Undestanding history: History diagrams
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Understanding history: History diagrams
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We will sometimes represent git history using diagrams like the one
below. Commits are shown as "o", and the links between them with
@@ -806,7 +806,7 @@ display options.
Note that git log starts with the most recent commit and works
backwards through the parents; however, since git history can contain
-multiple independant lines of development, the particular order that
+multiple independent lines of development, the particular order that
commits are listed in may be somewhat arbitrary.
Generating diffs
@@ -1075,7 +1075,7 @@ $ git commit
-------------------------------------------------
and git will prompt you for a commit message and then create the new
-commmit. Check to make sure it looks like what you expected with
+commit. Check to make sure it looks like what you expected with
-------------------------------------------------
$ git show
@@ -2953,7 +2953,7 @@ Include cross-references to the glossary, where appropriate.
Document shallow clones? See draft 1.5.0 release notes for some
documentation.
-Add a sectin on working with other version control systems, including
+Add a section on working with other version control systems, including
CVS, Subversion, and just imports of series of release tarballs.
More details on gitweb?