fix example that combined encryption=shared with keyid=

diff --git a/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment b/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment
index 905184f9588e9de83e119fb92cb303b029770ba7..2d5f5b0b158daa3d21721671fccee5d0bb69c920 100644 (file)
--- a/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment
+++ b/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment
@@ -9,7 +9,7 @@ sufficient to back that up. You can run `git annex enableremote`
 in an clone to enable an existing special remote.
 
 The only catch is that, if you have chosen to initremote a special remote
-using a gpg key, with `encryption=shared keyid=whatever`, you'll of course
+using a gpg key, with `keyid=whatever`, you'll of course
 also need that gpg key to to use it. If you run `git annex info $myremote`
 it will tell you amoung other things, any gpg keys that are used by that
 remote.

diff --git a/doc/special_remotes/rsync.mdwn b/doc/special_remotes/rsync.mdwn
index 4992a9c86fd77a7e6d18fa224bfa8c77b9aa0a78..04af8485438a2fc30042ed0eac8b466197cd7f48 100644 (file)
--- a/doc/special_remotes/rsync.mdwn
+++ b/doc/special_remotes/rsync.mdwn
@@ -2,12 +2,12 @@ This special remote type rsyncs file contents to somewhere else.
 
 Setup example:
 
-       # git annex initremote myrsync type=rsync rsyncurl=rsync://rsync.example.com/myrsync keyid=id@joeyh.name encryption=shared
+       # git annex initremote myrsync type=rsync rsyncurl=rsync://rsync.example.com/myrsync encryption=shared
        # git annex describe myrsync "rsync server"
 
 Or for using rsync over SSH
 
-       # git annex initremote myrsync type=rsync rsyncurl=ssh.example.com:/myrsync keyid=id@joeyh.name encryption=shared
+       # git annex initremote myrsync type=rsync rsyncurl=ssh.example.com:/myrsync encryption=shared
        # git annex describe myrsync "rsync server"
 
 ## configuration