svn commit: r1792137 - /tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

svn commit: r1792137 - /tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml

markt
Author: markt
Date: Thu Apr 20 19:43:01 2017
New Revision: 1792137

URL: http://svn.apache.org/viewvc?rev=1792137&view=rev
Log:
Fix typos

Modified:
    tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml

Modified: tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml
URL: http://svn.apache.org/viewvc/tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml?rev=1792137&r1=1792136&r2=1792137&view=diff
==============================================================================
--- tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml (original)
+++ tomcat/tc8.5.x/trunk/webapps/docs/security-howto.xml Thu Apr 20 19:43:01 2017
@@ -77,12 +77,12 @@
 
     <subsection name="JMX">
       <p>The security of the JMX connection is dependent on the implementation
-      provided by the JRE and therefore falls outside the control of Tomact.</p>
+      provided by the JRE and therefore falls outside the control of Tomcat.</p>
 
       <p>Typically, access control is very limited (either read-only to
       everything or read-write to everything). Tomcat exposes a large amount
       of internal information and control via JMX to aid debugging, monitoring
-      and management. Give the limited access control available, JMX access
+      and management. Given the limited access control available, JMX access
       should be treated as equivalent to local root/admin access and restricted
       accordingly.</p>
 



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

Loading...