summaryrefslogtreecommitdiffstats
path: root/doc/HOWTO
diff options
context:
space:
mode:
authorRich Salz <rsalz@openssl.org>2015-07-31 12:34:24 -0400
committerRich Salz <rsalz@openssl.org>2015-07-31 12:34:24 -0400
commitb68fa4d19ee68640f18d8eea4249eb0191a07694 (patch)
treefe6579d29f5c283453bf2aae0f69afecded9af08 /doc/HOWTO
parent602af7d01da82dc6c45946572f531bcbe9ebbf47 (diff)
Various doc fixes from GH pull requests
Thanks, folks! 348 Benjamin Kaduk 317 Christian Brueffer 254 Erik Tews 253 Erik Tews 219 Carl Mehner 155 (ghost) 95 mancha 51 DominikNeubauer (Manually picked from 59c554b36e39256ac2cfc34dca052453e10c6d9c) Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
Diffstat (limited to 'doc/HOWTO')
-rw-r--r--doc/HOWTO/keys.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/HOWTO/keys.txt b/doc/HOWTO/keys.txt
index 7ae2a3a118..ba0314fafc 100644
--- a/doc/HOWTO/keys.txt
+++ b/doc/HOWTO/keys.txt
@@ -40,9 +40,8 @@ consider insecure or to be insecure pretty soon.
3. To generate a DSA key
-A DSA key can be used for signing only. This is important to keep
-in mind to know what kind of purposes a certificate request with a
-DSA key can really be used for.
+A DSA key can be used for signing only. It is important to
+know what a certificate request with a DSA key can really be used for.
Generating a key for the DSA algorithm is a two-step process. First,
you have to generate parameters from which to generate the key: