replace redudundant and incomplete encryption para with link

1 files changed, 3 insertions, 12 deletions

diff --git a/doc/git-annex-initremote.mdwn b/doc/git-annex-initremote.mdwn
index 4265d89f4..1b46ff536 100644
--- a/doc/git-annex-initremote.mdwn
+++ b/doc/git-annex-initremote.mdwn
@@ -21,20 +21,11 @@ The remote's configuration is specified by the parameters passed
 to this command. Different types of special remotes need different
 configuration values. The command will prompt for parameters as needed.
 
-All special remotes support encryption. You can either specify
+All special remotes support encryption. You can specify
 `encryption=none` to disable encryption, or specify
 `encryption=hybrid keyid=$keyid ...` to specify a GPG key id (or an email
-address associated with a key).
-
-There are actually three schemes that can be used for management of the
-encryption keys. When using the encryption=hybrid scheme, additional
-GPG keys can be given access to the encrypted special remote easily
-(without re-encrypting everything). When using encryption=shared,
-a shared key is generated and stored in the git repository, allowing
-anyone who can clone the git repository to access it. Finally, when using
-encryption=pubkey, content in the special remote is directly encrypted
-to the specified GPG keys, and additional ones cannot easily be given
-access.
+address associated with a key). For details about ways to configure
+encryption, see <https://git-annex.branchable.com/encryption/>
 
 If you anticipate using the new special remote in other clones of the
 repository, you can pass "autoenable=true". Then when [[git-annex-init]](1)