jlprat commented on a change in pull request #10770:
URL: https://github.com/apache/kafka/pull/10770#discussion_r640515305



##########
File path: docs/security.html
##########
@@ -428,12 +428,12 @@ <h3 class="anchor-heading"><a id="security_sasl" 
class="anchor-link"></a><a href
             <tt>zookeeper.sasl.client.username</tt> to the appropriate name
             (<i>e.g.</i>, <tt>-Dzookeeper.sasl.client.username=zk</tt>).</p>
 
-            <p>Brokers may also configure JAAS using the broker configuration 
property <code>sasl.jaas.config</code>.
-            The property name must be prefixed with the listener prefix 
including the SASL mechanism,
-            i.e. 
<code>listener.name.{listenerName}.{saslMechanism}.sasl.jaas.config</code>. 
Only one
-            login module may be specified in the config value. If multiple 
mechanisms are configured on a
-            listener, configs must be provided for each mechanism using the 
listener and mechanism prefix.
-            For example,
+                    <p>Brokers may also configure JAAS using the broker 
configuration property <code>sasl.jaas.config</code>.
+                        The property name must be prefixed with the listener 
prefix including the SASL mechanism,
+                        i.e. 
<code>listener.name.{listenerName}.{saslMechanism}.sasl.jaas.config</code>. 
Only one
+                        login module may be specified in the config value. If 
multiple mechanisms are configured on a
+                        listener, configs must be provided for each mechanism 
using the listener and mechanism prefix.
+                        For example,

Review comment:
       Actually, it seems the above paragraphs should be indented to the right, 
there are several nested `<ol>` and `<li>` and `<p>` that didn't follow 
indentation.
   I'm fixing these now.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to