generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

s/recommend/recommended/

Browse Source
This commit is contained in:
Ben Laurie 2013-09-05 21:43:50 +01:00
parent 478b50cf67
commit cda01d55ba
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/crypto/X509_NAME_add_entry_by_txt.pod
View File

@ -44,7 +44,7 @@ B<loc>. The deleted entry is returned and must be freed up.
=head1 NOTES =head1 NOTES
The use of string types such as B<MBSTRING_ASC> or B<MBSTRING_UTF8> The use of string types such as B<MBSTRING_ASC> or B<MBSTRING_UTF8>
is strongly recommend for the B<type> parameter. This allows the is strongly recommended for the B<type> parameter. This allows the
internal code to correctly determine the type of the field and to internal code to correctly determine the type of the field and to
apply length checks according to the relevant standards. This is apply length checks according to the relevant standards. This is
done using ASN1_STRING_set_by_NID(). done using ASN1_STRING_set_by_NID().

2
doc/crypto/rand.pod
View File

@ -39,7 +39,7 @@ Since the introduction of the ENGINE API, the recommended way of controlling
default implementations is by using the ENGINE API functions. The default default implementations is by using the ENGINE API functions. The default
B<RAND_METHOD>, as set by RAND_set_rand_method() and returned by B<RAND_METHOD>, as set by RAND_set_rand_method() and returned by
RAND_get_rand_method(), is only used if no ENGINE has been set as the default RAND_get_rand_method(), is only used if no ENGINE has been set as the default
"rand" implementation. Hence, these two functions are no longer the recommend "rand" implementation. Hence, these two functions are no longer the recommended
way to control defaults. way to control defaults.
If an alternative B<RAND_METHOD> implementation is being used (either set If an alternative B<RAND_METHOD> implementation is being used (either set