summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar spwhitton <spwhitton@web>2012-12-09 21:59:14 +0000
committerGravatar admin <admin@branchable.com>2012-12-09 21:59:14 +0000
commit813fb669246a7d4247b95b15cd52bab02a2e0adb (patch)
treef1bc9c1008fbfa0972375311880a64cab7a0bb30
parentfff11a39a2ed064d00c5e931a87d1faf56f11bf3 (diff)
typos
-rw-r--r--doc/scalability.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/scalability.mdwn b/doc/scalability.mdwn
index 232a84cc6..9a4ff95ef 100644
--- a/doc/scalability.mdwn
+++ b/doc/scalability.mdwn
@@ -23,9 +23,9 @@ git-annex is designed for scalability. The key points are:
improves this will improve. Scaling to hundreds of thousands of files
is not a problem, scaling beyond that and git will start to get slow.
- To some degree, git-annex works around innefficiencies in git; for
- example it batches input sent to certian git commands that are slow
- when run in an emormous repository.
+ To some degree, git-annex works around inefficiencies in git; for
+ example it batches input sent to certain git commands that are slow
+ when run in an enormous repository.
* It can use as much, or as little bandwidth as is available. In
particular, any interrupted file transfer can be resumed by git-annex.