mention SKEIN*E variants

1 files changed, 5 insertions, 4 deletions

diff --git a/doc/backends.mdwn b/doc/backends.mdwn
index 79bacd68e..baa96c149 100644
--- a/doc/backends.mdwn
+++ b/doc/backends.mdwn
@@ -5,8 +5,8 @@ to retrieve the file's content (its value).
 Multiple pluggable key-value backends are supported, and a single repository
 can use different ones for different files.
 
-* `SHA256E` -- The default backend for new files, combines a SHA256 hash of
-  the file's content with the file's extension. This allows
+* `SHA256E` -- The default backend for new files, combines a 256 bit SHA-2
+  hash of the file's content with the file's extension. This allows
   verifying that the file content is right, and can avoid duplicates of
   files with the same content. Its need to generate checksums
   can make it slower for large files. 
@@ -16,12 +16,13 @@ can use different ones for different files.
   the same basename, size, and modification time has the same content.
   This is the least expensive backend, recommended for really large
   files or slow systems.
-* `SHA512`, `SHA512E` -- Best currently available hash, for the very paranoid.
+* `SHA512`, `SHA512E` -- Best SHA-2 hash, for the very paranoid.
 * `SHA1`, `SHA1E` -- Smaller hash than `SHA256` for those who want a checksum
    but are not concerned about security.
 * `SHA384`, `SHA384E`, `SHA224`, `SHA224E` -- Hashes for people who like
   unusual sizes.
-* `SKEIN512`, `SKEIN256` -- [Skein hash](http://en.wikipedia.org/wiki/Skein_hash),
+* `SKEIN512`, `SKEIN512E`, `SKEIN256`, `SKEIN256E`
+  -- [Skein hash](http://en.wikipedia.org/wiki/Skein_hash),
   a well-regarded SHA3 hash competition finalist.
 
 The `annex.backends` git-config setting can be used to list the backends