docs: Make SSL manpage fragments less specific to OpenFlow.

These manpage fragments are used in OVSDB manpages as well, so their text
should try to avoid referring to OpenFlow-specific concepts.

diff --git a/lib/ssl-bootstrap.man b/lib/ssl-bootstrap.man
index 178350d..68e41c0 100644 (file)
--- a/lib/ssl-bootstrap.man
+++ b/lib/ssl-bootstrap.man
@@ -14,7 +14,7 @@ for bootstrapping.
 .IP
 This option is only useful if the SSL peer sends its CA certificate as
 part of the SSL certificate chain.  The SSL protocol does not require
-the controller to send the CA certificate, but
+the server to send the CA certificate, but
 \fBovs\-controller\fR(8) can be configured to do so with the
 \fB\-\-peer\-ca\-cert\fR option.
 .IP

diff --git a/lib/ssl.man b/lib/ssl.man
index 29e3db0..30c25c9 100644 (file)
--- a/lib/ssl.man
+++ b/lib/ssl.man
@@ -11,10 +11,10 @@ private key specified on \fB\-p\fR or \fB\-\-private\-key\fR to be
 trustworthy.  The certificate must be signed by the certificate
 authority (CA) that the peer in SSL connections will use to verify it.
 .
-.IP "\fB\-C\fR \fIswitch\-cacert.pem\fR"
-.IQ "\fB\-\-ca\-cert=\fIswitch\-cacert.pem\fR"
+.IP "\fB\-C\fR \fIcacert.pem\fR"
+.IQ "\fB\-\-ca\-cert=\fIcacert.pem\fR"
 Specifies a PEM file containing the CA certificate that \fB\*(PN\fR
 should use to verify certificates presented to it by SSL peers.  (This
 may be the same certificate that SSL peers use to verify the
 certificate specified on \fB\-c\fR or \fB\-\-certificate\fR, or it may
-beq a different one, depending on the PKI design in use.)
+be a different one, depending on the PKI design in use.)