1 files changed, 8 insertions, 8 deletions

diff --git a/src/lib/libcrypto/man/BN_num_bytes.3 b/src/lib/libcrypto/man/BN_num_bytes.3
index 5223ff1116..3e96a401a5 100644
--- a/src/lib/libcrypto/man/BN_num_bytes.3
+++ b/src/lib/libcrypto/man/BN_num_bytes.3
@@ -1,11 +1,11 @@
-.\"     $OpenBSD: BN_num_bytes.3,v 1.2 2016/11/06 15:52:50 jmc Exp $
+.\"     $OpenBSD: BN_num_bytes.3,v 1.3 2016/11/08 22:19:45 jmc Exp $
 .\"
-.Dd $Mdocdate: November 6 2016 $
+.Dd $Mdocdate: November 8 2016 $
 .Dt BN_NUM_BYTES 3
 .Os
 .Sh NAME
-.Nm BN_num_bits ,
 .Nm BN_num_bytes ,
+.Nm BN_num_bits ,
 .Nm BN_num_bits_word
 .Nd get BIGNUM size
 .Sh SYNOPSIS
@@ -25,12 +25,12 @@
 .Sh DESCRIPTION
 .Fn BN_num_bytes
 returns the size of a
-.Sy BIGNUM
+.Vt BIGNUM
 in bytes.
 .Pp
 .Fn BN_num_bits_word
 returns the number of significant bits in a word.
-If we take 0x00000432 as an example, it returns 11, not 16, not 32.
+As an example, 0x00000432 returns 11, not 16 or 32.
 Basically, except for a zero, it returns
 .Pp
 .D1 floor(log2( Ns Fa w ) ) No + 1 .
@@ -43,9 +43,7 @@ following the same principle as
 .Pp
 .Fn BN_num_bytes
 is a macro.
-.Sh RETURN VALUES
-The size.
-.Sh NOTES
+.Pp
 Some have tried using
 .Fn BN_num_bits
 on individual numbers in RSA keys, DH keys and DSA keys, and found that
@@ -65,6 +63,8 @@ or use
 .Fn BN_num_bytes
 and multiply with 8 (although there's no real guarantee that will match
 the "key size", just a lot more probability).
+.Sh RETURN VALUES
+The size.
 .Sh SEE ALSO
 .Xr bn 3 ,
 .Xr DH_size 3 ,