This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch 11.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/11.0.x by this push:
     new ad66ab27db Improve wording
ad66ab27db is described below

commit ad66ab27db917a9faf4b23cfa6b952e977b3c054
Author: Mark Thomas <[email protected]>
AuthorDate: Tue Jan 6 10:09:02 2026 +0000

    Improve wording
---
 webapps/docs/config/http.xml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/webapps/docs/config/http.xml b/webapps/docs/config/http.xml
index 32e29bfc30..1fa65b36b2 100644
--- a/webapps/docs/config/http.xml
+++ b/webapps/docs/config/http.xml
@@ -1236,12 +1236,13 @@
   attributes to the values <code>https</code> and <code>true</code>
   respectively, to pass correct information to the servlets.</p>
 
-  <p>The NIO and NIO2 connectors use either the JSSE Java SSL implementation or
-  an OpenSSL implementation. As far as possible, common configuration 
attributes
-  are used for both JSSE and OpenSSL. You must use a consistent configuration
-  style (JSSE specific attributes or OpenSSL specfic attributes) for each of 
the
-  following groups of configuration attributes but you may use a different
-  configuration style for each group:</p>
+  <p>The NIO and NIO2 connectors may be configured to use either the JSSE Java 
SSL
+  implementation or an OpenSSL implementation. As far as possible, common
+  configuration attributes are used for both JSSE and OpenSSL. For each
+  Connector, you must use a consistent configuration style (JSSE specific
+  attributes or OpenSSL specfic attributes) for each of the following groups of
+  configuration attributes but you may use a different configuration style for
+  each group:</p>
   <ul>
     <li>trust attributes</li>
     <li>all other attributes</li>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to