Latest update.

doc/man1/ciphers.pod

@@ -411,7 +411,7 @@ based on client preferences. An equal-preference is specified with square
 brackets, combining multiple selectors separated by |. For example:
 
  [ECDHE-ECDSA-CHACHA20-POLY1305|ECDHE-ECDSA-AES128-GCM-SHA256]
- 
+
  Once an equal-preference group is used, future directives must be
  opcode-less.
 

doc/man1/version.pod

@@ -60,7 +60,7 @@ OPENSSLDIR setting.
 
 =item B<-e>
 
-ENGINESDIR setting.
+ENGINESDIR settings.
 
 =back
 

doc/man5/config.pod

@@ -42,6 +42,13 @@ working directory so unless the configuration file containing the
 B<.include> directive is application specific the inclusion will not
 work as expected.
 
+There can be optional B<=> character and whitespace characters between
+B<.include> directive and the path which can be useful in cases the
+configuration file needs to be loaded by old OpenSSL versions which do
+not support the B<.include> syntax. They would bail out with error
+if the B<=> character is not present but with it they just ignore
+the include.
+
 Each section in a configuration file consists of a number of name and
 value pairs of the form B<name=value>