links

diff --git a/doc/crypto/blowfish.pod b/doc/crypto/blowfish.pod
index 80cb44edba653cf37240d14f6466c3eafe167360..e8c7114311b5d634efd43e54de515c7e2c6c18ec 100644 (file)
--- a/doc/crypto/blowfish.pod
+++ b/doc/crypto/blowfish.pod
@@ -90,8 +90,9 @@ None of the functions presented here return any value.
 
 =head1 NOTE
 
-Applications should use the higher level functions EVP_EncryptInit(3) etc.
-instead of calling the blowfish functions directly.
+Applications should use the higher level functions
+L<EVP_EncryptInit(3)|EVP_EncryptInit(3)> etc. instead of calling the
+blowfish functions directly.
 
 =head1 SEE ALSO
 

diff --git a/doc/crypto/md5.pod b/doc/crypto/md5.pod
index 2b084878cda65cd547b7bb1ed3b717bdb8ca2f76..d7c120023dafca763e2a1a40408558e6598eb518 100644 (file)
--- a/doc/crypto/md5.pod
+++ b/doc/crypto/md5.pod
@@ -51,7 +51,8 @@ for MD2_DIGEST_LENGTH == 16 bytes of output, and erases the B<MD2_CTX>.
 MD5_Init(), MD5_Update() and MD5_Final() are analogous using an
 B<MD5_CTX> structure.
 
-Applications should use the higher level functions EVP_DigestInit(3)
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)>
 etc. instead of calling the hash functions directly.
 
 =head1 NOTE

diff --git a/doc/crypto/mdc2.pod b/doc/crypto/mdc2.pod
index d991a059727ba6967a8556d22883698c230804c9..11dc303e04f4d00cbe0813757a840439a6e40a3e 100644 (file)
--- a/doc/crypto/mdc2.pod
+++ b/doc/crypto/mdc2.pod
@@ -38,15 +38,16 @@ be hashed (B<len> bytes at B<data>).
 MDC2_Final() places the message digest in B<md>, which must have space
 for MDC2_DIGEST_LENGTH == 16 bytes of output, and erases the B<MDC2_CTX>.
 
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)> etc. instead of calling the
+hash functions directly.
+
 =head1 RETURN VALUES
 
 MDC2() returns a pointer to the hash value. 
 
 MDC2_Init(), MDC2_Update() and MDC2_Final() do not return values.
 
-Applications should use the higher level functions EVP_DigestInit(3) etc.
-instead of calling the hash functions directly.
-
 =head1 CONFORMING TO
 
 ISO/IEC 10118-2, with DES

diff --git a/doc/crypto/rc4.pod b/doc/crypto/rc4.pod
index aaab850afdab790d3cf43ccfc78d008099c44883..b6d3a4342caa22f066625d7d4a4dfd6f6c8fa013 100644 (file)
--- a/doc/crypto/rc4.pod
+++ b/doc/crypto/rc4.pod
@@ -37,7 +37,8 @@ Since RC4 is a stream cipher (the input is XORed with a pseudo-random
 key stream to produce the output), decryption uses the same function
 calls as encryption.
 
-Applications should use the higher level functions EVP_EncryptInit(3)
+Applications should use the higher level functions
+L<EVP_EncryptInit(3)|EVP_EncryptInit(3)>
 etc. instead of calling the RC4 functions directly.
 
 =head1 RETURN VALUES

diff --git a/doc/crypto/ripemd.pod b/doc/crypto/ripemd.pod
index 9656bb09803281d714b8bc69054882b094b1ce7b..31054b6a8ccd8dfa04150a86adbf1a45b71bf179 100644 (file)
--- a/doc/crypto/ripemd.pod
+++ b/doc/crypto/ripemd.pod
@@ -39,8 +39,9 @@ RIPEMD160_Final() places the message digest in B<md>, which must have
 space for RIPEMD160_DIGEST_LENGTH == 20 bytes of output, and erases
 the B<RIPEMD160_CTX>.
 
-Applications should use the higher level functions EVP_DigestInit(3) etc.
-instead of calling the hash functions directly.
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)> etc. instead of calling the
+hash functions directly.
 
 =head1 RETURN VALUES
 

diff --git a/doc/crypto/sha.pod b/doc/crypto/sha.pod
index 57b0fb6da4223e1b58ded39328a63acd5e723a8d..0ba315d6d7a336e0b54890dfcdff08b3818aab28 100644 (file)
--- a/doc/crypto/sha.pod
+++ b/doc/crypto/sha.pod
@@ -37,7 +37,8 @@ be hashed (B<len> bytes at B<data>).
 SHA1_Final() places the message digest in B<md>, which must have space
 for SHA_DIGEST_LENGTH == 20 bytes of output, and erases the B<SHA_CTX>.
 
-Applications should use the higher level functions EVP_DigestInit(3)
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)>
 etc. instead of calling the hash functions directly.
 
 The predecessor of SHA-1, SHA, is also implemented, but it should be