From 6328d3673fabc336e3064368d855c2d1153ef54c Mon Sep 17 00:00:00 2001 From: Gustaf Neumann Date: Sat, 4 Jul 2020 21:58:30 +0200 Subject: Fix typos and repeated words Reviewed-by: Paul Dale Reviewed-by: Matthias St. Pierre (Merged from https://github.com/openssl/openssl/pull/12370) --- doc/man1/s_client.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/man1/s_client.pod') diff --git a/doc/man1/s_client.pod b/doc/man1/s_client.pod index 86cc295691..132778b4d9 100644 --- a/doc/man1/s_client.pod +++ b/doc/man1/s_client.pod @@ -427,11 +427,11 @@ File to send output of B<-msg> or B<-trace> to, default standard output. =item B<-nbio_test> -Tests non-blocking I/O +Tests nonblocking I/O =item B<-nbio> -Turns on non-blocking I/O +Turns on nonblocking I/O =item B<-crlf> @@ -781,14 +781,14 @@ is that a web client complains it has no certificates or gives an empty list to choose from. This is normally because the server is not sending the clients certificate authority in its "acceptable CA list" when it requests a certificate. By using B the CA list can be viewed -and checked. However some servers only request client authentication +and checked. However, some servers only request client authentication after a specific URL is requested. To obtain the list in this case it is necessary to use the B<-prexit> option and send an HTTP request for an appropriate page. If a certificate is specified on the command line using the B<-cert> option it will not be used unless the server specifically requests -a client certificate. Therefore merely including a client certificate +a client certificate. Therefore, merely including a client certificate on the command line is no guarantee that the certificate works. If there are problems verifying a server certificate then the -- cgit v1.2.3