1 files changed, 4 insertions, 4 deletions

diff --git a/src/lib/libcrypto/doc/DSA_set_method.pod b/src/lib/libcrypto/doc/DSA_set_method.pod
index 5ad7362f58..707370adf7 100644
--- a/src/lib/libcrypto/doc/DSA_set_method.pod
+++ b/src/lib/libcrypto/doc/DSA_set_method.pod
@@ -103,8 +103,8 @@ B<DSA_METHOD>s.
 
 DSA_set_default_method() returns no value.
 
-DSA_set_method() returns non-zero if the provided B<meth> was successfully set as
-the method for B<dsa> (including unloading the ENGINE handle if the previous
+DSA_set_method() returns non-zero if the provided B<meth> was successfully set
+as the method for B<dsa> (including unloading the ENGINE handle if the previous
 method was supplied by an ENGINE).
 
 DSA_new_method() returns NULL and sets an error code that can be
@@ -117,8 +117,8 @@ As of version 0.9.7, DSA_METHOD implementations are grouped together with other
 algorithmic APIs (eg. RSA_METHOD, EVP_CIPHER, etc) in B<ENGINE> modules. If a
 default ENGINE is specified for DSA functionality using an ENGINE API function,
 that will override any DSA defaults set using the DSA API (ie.
-DSA_set_default_method()). For this reason, the ENGINE API is the recommended way
-to control default implementations for use in DSA and other cryptographic
+DSA_set_default_method()). For this reason, the ENGINE API is the recommended
+way to control default implementations for use in DSA and other cryptographic
 algorithms.
 
 =head1 SEE ALSO