properly break lines.

2 files changed, 22 insertions, 17 deletions

diff --git a/src/ocsptool-args.def b/src/ocsptool-args.def
index b6efe43bb3..ad9e4dd0df 100644
--- a/src/ocsptool-args.def
+++ b/src/ocsptool-args.def
@@ -172,7 +172,8 @@ format is used for these files, although @code{--inder} can be used to
 specify that the input files are in DER format.
 
 @example
-$ ocsptool -q --load-issuer issuer.pem --load-cert client.pem --outfile ocsp-request.der
+$ ocsptool -q --load-issuer issuer.pem --load-cert client.pem \
+           --outfile ocsp-request.der
 @end example
 
 When generating OCSP requests, the tool will add an OCSP extension
@@ -193,7 +194,8 @@ certificate needs to be in the set of trust anchors and the OCSP
 Extended Key Usage bit has to be asserted in the signer certificate.
 
 @example
-$ ocsptool -e --load-trust issuer.pem --load-response ocsp-response.der
+$ ocsptool -e --load-trust issuer.pem \
+           --load-response ocsp-response.der
 @end example
 
 The tool will print status of verification.
@@ -208,7 +210,8 @@ one certificate and it will be used to verify the signature in the
 OCSP response.  It will not check the Extended Key Usage bit.
 
 @example
-$ ocsptool -e --load-signer ocsp-signer.pem --load-response ocsp-response.der
+$ ocsptool -e --load-signer ocsp-signer.pem \
+           --load-response ocsp-response.der
 @end example
 
 This approach is normally only relevant in two situations.  The first
@@ -251,8 +254,8 @@ This means the CA support OCSP queries over HTTP.  We are now ready to
 create a OCSP request for the certificate.
 
 @example
-$ ocsptool --ask ocsp.CAcert.org --load-issuer issuer.pem  --load-cert cert.pem \
-           --outfile ocsp-response.der
+$ ocsptool --ask ocsp.CAcert.org --load-issuer issuer.pem \
+           --load-cert cert.pem --outfile ocsp-response.der
 @end example
 
 The request is sent via HTTP to the OCSP server address specified. If the
diff --git a/src/p11tool-args.def b/src/p11tool-args.def
index 5a058e4431..b45d0442c9 100644
--- a/src/p11tool-args.def
+++ b/src/p11tool-args.def
@@ -85,19 +85,19 @@ flag = {
 
 flag = {
     name      = generate-rsa;
-    descrip   = "Generates an RSA private-public key pair on the specified token";
-    doc = "";
+    descrip   = "Generate an RSA private-public key pair";
+    doc = "Generates an RSA private-public key pair on the specified token.";
 };
 
 flag = {
     name      = generate-dsa;
-    descrip   = "Generates an RSA private-public key pair on the specified token";
-    doc = "";
+    descrip   = "Generate an RSA private-public key pair";
+    doc = "Generates an RSA private-public key pair on the specified token.";
 };
 flag = {
     name      = generate-ecc;
-    descrip   = "Generates an RSA private-public key pair on the specified token";
-    doc = "";
+    descrip   = "Generate an RSA private-public key pair";
+    doc = "Generates an RSA private-public key pair on the specified token.";
 };
 
 flag = {
@@ -188,17 +188,17 @@ flag = {
     name      = sec-param;
     arg-type  = string;
     arg-name  = "Security parameter";
-    descrip   = "Specify the security level [low|legacy|normal|high|ultra].";
-    doc      = "This is alternative to the bits option.";
+    descrip   = "Specify the security level";
+    doc      = "This is alternative to the bits option. Available options are [low|legacy|normal|high|ultra].";
 };
 
 
 flag = {
     name      = inder;
-    descrip   = "Use DER/RAW format for input certificates and private keys";
+    descrip   = "Use DER/RAW format for input";
     disabled;
     disable   = "no";
-    doc      = "";
+    doc      = "Use DER/RAW format for input certificates and private keys.";
 };
 
 flag = {
@@ -239,8 +239,10 @@ $ p11tool --login --list-all "pkcs11:TOKEN-URL"
 
 To store a private key and a certificate in a token run:
 @example
-$ p11tool --login --write "pkcs11:URL" --load-privkey key.pem --label "Mykey"
-$ p11tool --login --write "pkcs11:URL" --load-certificate cert.pem --label "MyCert"
+$ p11tool --login --write "pkcs11:URL" --load-privkey key.pem \
+          --label "Mykey"
+$ p11tool --login --write "pkcs11:URL" --load-certificate cert.pem \
+          --label "MyCert"
 @end example
 _EOT_;
 };