summaryrefslogtreecommitdiff
path: root/doc/trust.mdwn
diff options
context:
space:
mode:
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 1fd47fd1d..a33c6dd42 100644
--- a/doc/trust.mdwn
+++ b/doc/trust.mdwn
@@ -45,7 +45,7 @@ archival drive, from which you rarely or never remove content. Deciding
when it makes sense to trust the tracking info is up to you.
One way to handle this is just to use `--force` when a command cannot
-access a remote you trust. Or to use `--trust` to specify a repisitory to
+access a remote you trust. Or to use `--trust` to specify a repository to
trust temporarily.
To configure a repository as fully and permanently trusted,
@@ -55,5 +55,5 @@ use the `git annex trust` command.
This is used to indicate that you have no trust that the repository
exists at all. It's appropriate to use when a drive has been lost,
-or a directory irretrevably deleted. It will make git-annex avoid
+or a directory irretrievably deleted. It will make git-annex avoid
even showing the repository as a place where data might still reside.