X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=doc%2Fcrypto%2Fd2i_DSAPublicKey.pod;h=7acb329f2382502d5c8107f86623b7e674212745;hp=e999376492401b8001f916759eb31cfcf93fe71d;hb=0c787647ded59a81311d905024bc93df5d3a061c;hpb=aafbe1ccd28439d0eb484f5b889272cbc71d62b5

diff --git a/doc/crypto/d2i_DSAPublicKey.pod b/doc/crypto/d2i_DSAPublicKey.pod
index e999376492..7acb329f23 100644
--- a/doc/crypto/d2i_DSAPublicKey.pod
+++ b/doc/crypto/d2i_DSAPublicKey.pod
@@ -49,7 +49,7 @@ d2i_DSA_SIG(), i2d_DSA_SIG() decode and encode a DSA signature using a
 B<Dss-Sig-Value> structure as defined in RFC2459.
 
 The usage of all of these functions is similar to the d2i_X509() and
-i2d_X509() described in the L<d2i_X509(3)|d2i_X509(3)> manual page.
+i2d_X509() described in the L<d2i_X509(3)> manual page.
 
 =head1 NOTES
 
@@ -62,19 +62,17 @@ offers no private key security.
 The B<DSA_PUBKEY> functions should be used in preference to the B<DSAPublicKey>
 functions when encoding public keys because they use a standard format.
 
-The B<DSAPublicKey> functions use an non standard format the actual data encoded
-depends on the value of the B<write_params> field of the B<a> key parameter.
-If B<write_params> is zero then only the B<pub_key> field is encoded as an
-B<INTEGER>. If B<write_params> is 1 then a B<SEQUENCE> consisting of the
-B<p>, B<q>, B<g> and B<pub_key> respectively fields are encoded.
+The B<DSAPublicKey> functions use a non standard format which is a
+B<SEQUENCE> consisting of the B<p>, B<q>, B<g> and B<pub_key> fields
+respectively.
 
-The B<DSAPrivateKey> functions also use a non standard structure consiting
+The B<DSAPrivateKey> functions also use a non standard structure consisting
 consisting of a SEQUENCE containing the B<p>, B<q>, B<g> and B<pub_key> and
 B<priv_key> fields respectively.
 
 =head1 SEE ALSO
 
-L<d2i_X509(3)|d2i_X509(3)>
+L<d2i_X509(3)>
 
 =head1 HISTORY