While dabbling with J. Friedl's script for detecting doubled words in his "Mastering Regular Expressions" book, I found these four instances of doubled words.
Three of these are completely straightforward: EC_GROUP_copy.pod: the the EC_KEY_new.pod: have have d2i_X509_NAME.pod: the the However, the doubled 'not' in EVP_DigestVerifyInit.pod reverses the meaning of the sentence. The context indicates that the word doubling is unintended. Index: lib/libssl/src/doc/crypto/EC_GROUP_copy.pod =================================================================== RCS file: /cvs/src/lib/libssl/src/doc/crypto/EC_GROUP_copy.pod,v retrieving revision 1.1 diff -u -p -r1.1 EC_GROUP_copy.pod --- lib/libssl/src/doc/crypto/EC_GROUP_copy.pod 11 Jul 2014 16:18:14 -0000 1.1 +++ lib/libssl/src/doc/crypto/EC_GROUP_copy.pod 8 Jul 2015 08:21:24 -0000 @@ -158,7 +158,7 @@ EC_GROUP_get0_seed returns a pointer to specified. EC_GROUP_get_seed_len returns the length of the seed or 0 if the seed is not specified. EC_GROUP_set_seed returns the length of the seed that has been set. If the supplied seed is NULL, or the supplied seed length is -0, the the return value will be 1. On error 0 is returned. +0, the return value will be 1. On error 0 is returned. EC_GROUP_cmp returns 0 if the curves are equal, 1 if they are not equal, or -1 on error. Index: lib/libssl/src/doc/crypto/EC_KEY_new.pod =================================================================== RCS file: /cvs/src/lib/libssl/src/doc/crypto/EC_KEY_new.pod,v retrieving revision 1.1 diff -u -p -r1.1 EC_KEY_new.pod --- lib/libssl/src/doc/crypto/EC_KEY_new.pod 11 Jul 2014 16:18:14 -0000 1.1 +++ lib/libssl/src/doc/crypto/EC_KEY_new.pod 8 Jul 2015 08:21:24 -0000 @@ -78,7 +78,7 @@ The functions EC_KEY_get_conv_form and E of point_conversion_forms please refer to L<EC_POINT_new(3)|EC_POINT_new(3)>. EC_KEY_insert_key_method_data and EC_KEY_get_key_method_data enable the caller to associate arbitary additional data specific to the -elliptic curve scheme being used with the EC_KEY object. This data is treated as a "black box" by the ec library. The data to be stored by EC_KEY_insert_key_method_data is provided in the B<data> parameter, which must have have associated functions for duplicating, freeing and "clear_freeing" the data item. If a subsequent EC_KEY_get_key_method_data call is issued, the functions for duplicating, freeing and "clear_freeing" the data item must be provided again, and they must be the same as they were when the data item was inserted. +elliptic curve scheme being used with the EC_KEY object. This data is treated as a "black box" by the ec library. The data to be stored by EC_KEY_insert_key_method_data is provided in the B<data> parameter, which must have associated functions for duplicating, freeing and "clear_freeing" the data item. If a subsequent EC_KEY_get_key_method_data call is issued, the functions for duplicating, freeing and "clear_freeing" the data item must be provided again, and they must be the same as they were when the data item was inserted. EC_KEY_set_flags sets the flags in the B<flags> parameter on the EC_KEY object. Any flags that are already set are left set. The currently defined standard flags are EC_FLAG_NON_FIPS_ALLOW and EC_FLAG_FIPS_CHECKED. In addition there is the flag EC_FLAG_COFACTOR_ECDH which is specific to ECDH and is defined in ecdh.h. EC_KEY_get_flags returns the current flags that are set for this EC_KEY. EC_KEY_clear_flags clears the flags indicated by the B<flags> parameter. All other flags are left in their existing state. Index: lib/libssl/src/doc/crypto/EVP_DigestVerifyInit.pod =================================================================== RCS file: /cvs/src/lib/libssl/src/doc/crypto/EVP_DigestVerifyInit.pod,v retrieving revision 1.5 diff -u -p -r1.5 EVP_DigestVerifyInit.pod --- lib/libssl/src/doc/crypto/EVP_DigestVerifyInit.pod 20 Jun 2015 01:07:25 -0000 1.5 +++ lib/libssl/src/doc/crypto/EVP_DigestVerifyInit.pod 8 Jul 2015 08:21:24 -0000 @@ -39,7 +39,7 @@ or a negative value for failure. In part the operation is not supported by the public key algorithm. Unlike other functions the return value 0 from EVP_DigestVerifyFinal() only -indicates that the signature did not not verify successfully (that is tbs did +indicates that the signature did not verify successfully (that is tbs did not match the original data or the signature was of invalid form) it is not an indication of a more serious error. Index: lib/libssl/src/doc/crypto/d2i_X509_NAME.pod =================================================================== RCS file: /cvs/src/lib/libssl/src/doc/crypto/d2i_X509_NAME.pod,v retrieving revision 1.2 diff -u -p -r1.2 d2i_X509_NAME.pod --- lib/libssl/src/doc/crypto/d2i_X509_NAME.pod 10 Jul 2014 13:53:11 -0000 1.2 +++ lib/libssl/src/doc/crypto/d2i_X509_NAME.pod 8 Jul 2015 08:21:24 -0000 @@ -14,7 +14,7 @@ d2i_X509_NAME, i2d_X509_NAME - X509_NAME =head1 DESCRIPTION These functions decode and encode an B<X509_NAME> structure which is the -the same as the B<Name> type defined in RFC2459 (and elsewhere) and used +same as the B<Name> type defined in RFC2459 (and elsewhere) and used for example in certificate subject and issuer names. Othewise the functions behave in a similar way to d2i_X509() and i2d_X509()
