summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-02-10 12:26:47 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-02-10 12:26:47 -0400
commit30f3d7d168c8010ed1f9303b9b47b1c05d178a95 (patch)
tree8b2d53941a744347535da5e4ef29beabdcada80c
parent5cec5d9d7cd40e5bd9ba488ee544b55a9c57cdf5 (diff)
s/large/annexed/
-rw-r--r--doc/how_it_works.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/how_it_works.mdwn b/doc/how_it_works.mdwn
index d91af8309..69e5256e3 100644
--- a/doc/how_it_works.mdwn
+++ b/doc/how_it_works.mdwn
@@ -6,7 +6,7 @@ You do not need to read this page to get started with using git-annex. The
Still reading? Ok. Git's man page calls it "a stupid content
tracker". With git-annex, git is instead "a stupid filename and metadata"
-tracker. The contents of large files are not stored in git, only the
+tracker. The contents of annexed files are not stored in git, only the
names of the files and some other metadata remain there.
The contents of the files are kept by git-annex in a distributed key/value