summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZack Brown <zbrown@tumblerings.org>2005-04-25 21:28:33 (GMT)
committerPetr Baudis <xpasky@machine.sinus.cz>2005-05-11 00:08:53 (GMT)
commitbebc5c61439a291e8f0f99e037ebdf63d3dfac46 (patch)
tree0b089f6d0e126acd9d827bd40383758b9be13922
parent90c4851b1787dfc1d3d3a5cf78c558d136c69bdd (diff)
downloadgit-bebc5c61439a291e8f0f99e037ebdf63d3dfac46.zip
git-bebc5c61439a291e8f0f99e037ebdf63d3dfac46.tar.gz
git-bebc5c61439a291e8f0f99e037ebdf63d3dfac46.tar.bz2
Spelling fixes in README.
Signed-off-by: Zack Brown <zbrown@tumblerings.org> Signed-off-by: Petr Baudis <pasky@ucw.cz>
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index 2500930..916d43e 100644
--- a/README
+++ b/README
@@ -95,7 +95,7 @@ The object types in some more detail:
In particular, since the blob is entirely defined by its data,
if two files in a directory tree (or in multiple different
versions of the repository) have the same contents, they will
- share the same blob object. The object is toally independent
+ share the same blob object. The object is totally independent
of it's location in the directory tree, and renaming a file does
not change the object that file is associated with in any way.
@@ -322,7 +322,7 @@ main combinations:
changes in your working directory (i.e. "update-cache").
However, if you decide to jump to a new version, or check out
- somebody elses version, or just restore a previous tree, you'd
+ somebody else's version, or just restore a previous tree, you'd
populate your index file with read-tree, and then you need to
check out the result with