summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-01-26 21:52:51 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-01-26 21:52:51 -0400
commit7ab481448c4cdc39bae746423f535ae742b8784a (patch)
tree354afc5e35331b4ed2225696ecd8017d4a93d5fe
parente1d213d6e3c9fe0cda6e2b80c4abeb17db5d3a16 (diff)
wording
-rw-r--r--doc/trust.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/trust.mdwn b/doc/trust.mdwn
index dbddfe426..f843d3858 100644
--- a/doc/trust.mdwn
+++ b/doc/trust.mdwn
@@ -4,7 +4,7 @@ Git-annex supports three levels of trust of a repository:
* untrusted
* trusted
-## semi-trusted
+## semitrusted
Normally, git-annex does not fully trust its stored [[location_tracking]]
information. When removing content, it will directly check
@@ -15,7 +15,7 @@ Generally that explicit checking is a good idea. Consider that the current
out. Or, a remote may have suffered a catastrophic loss of data, or itself
been lost.
-There is still some trust involved here. A semi-trusted repository is
+There is still some trust involved here. A semitrusted repository is
dependended on to retain a copy of the file content; possibly the only
[[copy|copies]].