CONF_modules_load_file.pod: The ssl_module no longer uses global data

Remove the paragraph that is no longer relevant.

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/29374)

diff --git a/doc/man3/CONF_modules_load_file.pod b/doc/man3/CONF_modules_load_file.pod
index 86de1678019f0f77926fdbd45309de31db6b1718..4c7029e780da49cc26c6e45f9ab2e111ad2692ba 100644 (file)
--- a/doc/man3/CONF_modules_load_file.pod
+++ b/doc/man3/CONF_modules_load_file.pod
@@ -162,12 +162,6 @@ context.
 Therefore, even if used with a freshly created library context, the function
 is not thread safe, and should not be used except as part of early application
 initialisation.
-Applications that want to use multiple library contexts may find that the most
-recently loaded configuration file perturbs prior settings in other library
-contexts.
-For example, B<ssl> module settings are not library context specific, and the
-last configuration file loaded that has an C<ssl_config> setting changes the
-SSL settings for all library contexts.
 The L<SSL_CTX_config(3)> and L<SSL_config(3)> functions can be used to perform
 late customisation of SSL contexts and connection handles.
 Here I<late> means that the chosen section's settings are applied in addition