summaryrefslogtreecommitdiff
path: root/doc/trust.mdwn
diff options
context:
space:
mode:
authorGravatar http://sunny256.sunbase.org/ <sunny256@web>2011-02-15 05:56:24 +0000
committerGravatar admin <admin@branchable.com>2011-02-15 05:56:24 +0000
commit000d9fcf334436dc085d52655dc07f69cd465980 (patch)
treefc171a7a5727b17cab7d49eca7d2f40126bffc78 /doc/trust.mdwn
parent36e13cfce64b43a47c2812be6b17b7a8af22f786 (diff)
Typo fixes in trust.mdwn
Diffstat (limited to 'doc/trust.mdwn')
-rw-r--r--doc/trust.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/trust.mdwn b/doc/trust.mdwn
index f843d3858..317e4b541 100644
--- a/doc/trust.mdwn
+++ b/doc/trust.mdwn
@@ -11,12 +11,12 @@ information. When removing content, it will directly check
that other repositories have enough [[copies]].
Generally that explicit checking is a good idea. Consider that the current
-[[location_tracking]] information for a remote may not yet have propigated
+[[location_tracking]] information for a remote may not yet have propagated
out. Or, a remote may have suffered a catastrophic loss of data, or itself
been lost.
There is still some trust involved here. A semitrusted repository is
-dependended on to retain a copy of the file content; possibly the only
+depended on to retain a copy of the file content; possibly the only
[[copy|copies]].
(Being semitrusted is the default. The `git annex semitrust` command