links

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
 

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

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

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

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
 

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