aboutsummaryrefslogtreecommitdiffstats
path: root/lib/crypto/doc
diff options
context:
space:
mode:
authorOle Morten Halvorsen <[email protected]>2018-08-13 20:29:37 +0200
committerOle Morten Halvorsen <[email protected]>2018-08-13 20:29:37 +0200
commit7bea41464c5ceed11be8326d54aed3712091b784 (patch)
tree412ec23c1d803e7e70136f47b38af9d8c0dbfa0d /lib/crypto/doc
parent4fc61aa178faa80290356a63d8e38d93697b9669 (diff)
downloadotp-7bea41464c5ceed11be8326d54aed3712091b784.tar.gz
otp-7bea41464c5ceed11be8326d54aed3712091b784.tar.bz2
otp-7bea41464c5ceed11be8326d54aed3712091b784.zip
Doc typo fixes, Thoose -> Those.
Diffstat (limited to 'lib/crypto/doc')
-rw-r--r--lib/crypto/doc/src/engine_keys.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/crypto/doc/src/engine_keys.xml b/lib/crypto/doc/src/engine_keys.xml
index 38714fed8a..80d811c47e 100644
--- a/lib/crypto/doc/src/engine_keys.xml
+++ b/lib/crypto/doc/src/engine_keys.xml
@@ -40,7 +40,7 @@
</p>
<p>
An engine could among other tasks provide a storage for
- private or public keys. Such a storage could be made safer than the normal file system. Thoose techniques are not
+ private or public keys. Such a storage could be made safer than the normal file system. Those techniques are not
described in this User's Guide. Here we concentrate on how to use private or public keys stored in
such an engine.
</p>