summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Richard Hartmann <richih.mailinglist@gmail.com>2013-04-15 08:53:52 +0200
committerGravatar Richard Hartmann <richih.mailinglist@gmail.com>2013-04-15 08:53:52 +0200
commitecf378f25488650df260e0cce5950de38e3dd980 (patch)
tree7f2bd4e49eb0579dbc7f5eabfdae6da81c1ee972
parentba977b50aad8768b4e57a759a25f4d6668ede03b (diff)
Typo
-rw-r--r--doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
index 7a528573b..01b8195b6 100644
--- a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
+++ b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn
@@ -14,7 +14,7 @@ the source). If you use gnome-keyring and have set up a repository on a
remote server with the assistant, I'd recommend moving the keys it set up
and editing `~/.ssh/config` to point to their new location.
-gnome-keyring is not the only peice of software that has a bad
+gnome-keyring is not the only piece of software that has a bad
interaction with git-annex. I've been working on a bug that makes git-annex
fail to authenticate to ejabberd. ejabberd 2.1.10 got support for
SCRAM-SHA-1, but its code violates the RFC, and chokes on an address