Editorial: future proofing -> future-proofing

Reviewed-by: Saša Nedvědický <sashan@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/28650)

diff --git a/doc/designs/passing-algorithmidentifier-parameters.md b/doc/designs/passing-algorithmidentifier-parameters.md
index f33862e45e20554a7899d2f7ebb71eb02ddfb070..9c5669e86b2d7e6865f28088de7c6e12ebc49c71 100644 (file)
--- a/doc/designs/passing-algorithmidentifier-parameters.md
+++ b/doc/designs/passing-algorithmidentifier-parameters.md
@@ -102,8 +102,8 @@ EVP_PKEY_CTX_get_algor_params(EVP_PKEY_CTX *ctx, X509_ALGOR *alg);
 EVP_PKEY_CTX_get_algor(EVP_PKEY_CTX *ctx, X509_ALGOR **alg);
 ```
 
-Note that all might not need to be added immediately, depending on if they
-are considered useful or not.  For future proofing, however, they should
+Note that not all may need to be added at this time, depending on whether or
+not they are considered useful.  For future-proofing, however, they should
 probably all be added.
 
 Requirements on the providers

diff --git a/doc/man3/SSL_CTX_config.pod b/doc/man3/SSL_CTX_config.pod
index 8ddb4a9739aa344902bfd152bc450f7f4fa47b0b..9b1eb3e326785c99442ad7fce2338c9924d45597 100644 (file)
--- a/doc/man3/SSL_CTX_config.pod
+++ b/doc/man3/SSL_CTX_config.pod
@@ -18,9 +18,10 @@ B<SSL> structure using the configuration B<name>.
 
 By calling SSL_CTX_config() or SSL_config() an application can perform many
 complex tasks based on the contents of the configuration file: greatly
-simplifying application configuration code. A degree of future proofing
-can also be achieved: an application can support configuration features
-in newer versions of OpenSSL automatically.
+simplifying application configuration code.
+Some future-proofing can be attained this way: the specified configuration
+section can specify settings supported by the run-time version of OpenSSL that
+were not known at the time the application code was written.
 
 A configuration file must have been previously loaded, for example using
 CONF_modules_load_file(). See L<config(5)> for details of the configuration