Various typo fixes in doc/*.mdwn

One of my

  for f in `ls *.mdwn | sort -R`; do aspell -c $f; sleep 2; done

sessions.

3647f704-e510-11e4-bf50-000df06acc56

doc/git-annex-lock.mdwn

@@ -1,6 +1,6 @@
 # NAME
 
-git-annex lock - unco unlock command
+git-annex lock - undo unlock command
 
 # SYNOPSIS
 

doc/git-annex-preferred-content.mdwn

@@ -18,7 +18,7 @@ For example:
 
 The main differences are that `exclude=` and `include=` always
 match relative to the top of the git repository, and that there is
-no equivilant to `--in`.
+no equivalent to `--in`.
 
 For more details about preferred content expressions, see
 See <https://git-annex.branchable.com/preferred_content/>

doc/git-annex-readpresentkey.mdwn

@@ -9,7 +9,7 @@ git annex readpresentkey `key uuid`
 # DESCRIPTION
 
 This plumbing-level command reads git-annex's records about whether
-the specified key's content is present in the remote with the speficied
+the specified key's content is present in the remote with the specified
 uuid.
   
 It exits 0 if the key is recorded to be present and 1 if not.

doc/git-annex-shell.mdwn

@@ -86,7 +86,7 @@ to git-annex-shell are:
 
 * -- fields=val fields=val.. --
 
-  Additional fields may be specified this way, to retain compatability with
+  Additional fields may be specified this way, to retain compatibility with
   past versions of git-annex-shell (that ignore these, but would choke
   on new dashed options).
 

doc/privacy.mdwn

@@ -41,7 +41,7 @@ output you post, and feel free to remove identifying information.
 Note that the git-annex assistant *does* sanitize XMPP protocol information
 logged when debugging is enabled.
 
-If you prefer not to post information publicaly, you can send a GPG
+If you prefer not to post information publically, you can send a GPG
 encrypted mail to Joey Hess <id@joeyh.name> (gpg key ID 2512E3C7).
 Or you can post a public bug report, and send a followup email with private
 details.

doc/transferring_data.mdwn

@@ -9,7 +9,7 @@ If a data transfer is interrupted, git-annex retains the partial transfer
 to allow it to be automatically resumed later.
 
 It's equally easy to transfer a single file to or from a repository,
-or to launch a retrievel of a massive pile of files from whatever
+or to launch a retrieval of a massive pile of files from whatever
 repositories they are scattered amongst.
 
 git-annex automatically uses whatever remotes are currently accessible,

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.

doc/upgrades.mdwn

@@ -1,9 +1,9 @@
-Occasionally improvments are made to how git-annex stores its data,
+Occasionally improvements are made to how git-annex stores its data,
 that require an upgrade process to convert repositories made with an older
 version to be used by a newer version. It's annoying, it should happen
 rarely, but sometimes, it's worth it.
 
-There's a committment that git-annex will always support upgrades from all
+There's a commitment that git-annex will always support upgrades from all
 past versions. After all, you may have offline drives from an earlier
 git-annex, and might want to use them with a newer git-annex.