From: Loup Vaillant Date: Mon, 6 Nov 2017 19:29:58 +0000 (+0100) Subject: Manual review: applying CuleX's advice X-Git-Url: https://git.codecow.com/?a=commitdiff_plain;h=4d462c4f2e35e55b7db3ade90fa141128a4ffc9e;p=Monocypher.git Manual review: applying CuleX's advice --- diff --git a/doc/man/man3/crypto_lock_init.3monocypher b/doc/man/man3/crypto_lock_init.3monocypher index 7ad982e..ff5b1b5 100644 --- a/doc/man/man3/crypto_lock_init.3monocypher +++ b/doc/man/man3/crypto_lock_init.3monocypher @@ -9,7 +9,7 @@ .Nm crypto_lock_final , .Nm crypto_unlock_update , .Nm crypto_unlock_final -.Nd incremental authenticated encryption with authenticated data +.Nd incremental authenticated encryption with additional data .Sh SYNOPSIS .In monocypher.h .Ft void @@ -82,7 +82,7 @@ Authentication with .Fn crypto_lock_auth . This authenticates (or verifies) additional data, if any. .It -Update, with +Update with .Fn crypto_lock_update for encryption, or .Fn crypto_unlock_update @@ -90,7 +90,7 @@ for decryption. This encrypts (or decrypts) and authenticates (or verifies) part of the secret message. .It -Final, with +Finalisation with .Fn crypto_lock_final to generate the MAC, or .Fn crypto_unlock_final diff --git a/doc/man/man3/crypto_poly1305_auth.3monocypher b/doc/man/man3/crypto_poly1305_auth.3monocypher index 2195cae..dbece62 100644 --- a/doc/man/man3/crypto_poly1305_auth.3monocypher +++ b/doc/man/man3/crypto_poly1305_auth.3monocypher @@ -188,7 +188,7 @@ The authentication key should be wiped with .Xr crypto_wipe 3monocypher after use. .Pp -Incremental interface users don't need to wipe the +Incremental interface users do not need to wipe the .Ft crypto_poly1305_ctx explicitly, .Fn crypto_poly1305_final diff --git a/doc/man/man3/crypto_sign_init_first_pass.3monocypher b/doc/man/man3/crypto_sign_init_first_pass.3monocypher index b843741..f9a5941 100644 --- a/doc/man/man3/crypto_sign_init_first_pass.3monocypher +++ b/doc/man/man3/crypto_sign_init_first_pass.3monocypher @@ -168,8 +168,8 @@ Ed25519 is described in RFC 7748. The same as documented on .Xr crypto_sign 3monocypher . .Sh IMPLEMENTATION DETAILS -EdDSA signatures require two passes, that cannot be performed in +EdDSA signatures require two passes that cannot be performed in parallel. There are ways around this limitation, but they all lower security in some way. -For this reason, Monocypher doesn't support them. +For this reason, Monocypher does not support them.