diff -r 5577d3eae04c -r fa48ab29abd2 docs/html/encryption.html
--- a/docs/html/encryption.html	Fri Aug 04 20:03:21 2017 +0200
+++ b/docs/html/encryption.html	Sat Aug 05 09:36:03 2017 +0200
@@ -67,7 +67,7 @@
 <h1 id="encryption">Encryption</h1>
 <p>The davutils programs have an integrated client-side encryption feature, that allows you to encrypt and decrypt on the fly with AES256 or AES128. To use this feature, the server <strong>must</strong> support WebDAV dead properties.</p>
 <p>The tools support both, encryption of the resource content and encryption of the resource name. Each resource is encrypted separately. With activated name encryption, the actual resource name is random but the name used by the client is stored encrypted in WebDAV properties. This means, an attacker can see the directory structure and the file length, but can't see which files have the same name.</p>
-<p>To enable encryption a key must be configured in <code>$HOME/.dav/config.xml</code>. A key must have an unique name. To access encrypted resources, all clients must configure the same key with the same name. Currently a key can only be loaded from a file and not generated from a password.</p>
+<p>To enable encryption a key must be configured in <code>$HOME/.dav/config.xml</code>. A key must have a unique name. To access encrypted resources, all clients must configure the same key with the same name. Currently a key can only be loaded from a file and not generated from a password.</p>
 <p>A configuration for a key looks like:</p>
 <pre><code>&lt;key&gt;
     &lt;name&gt;mykey1&lt;/name&gt;