commit c608ca62770689b9dcbbbd27e0498442623a62ad
author David Arthur <mumrah@gmail.com> Wed Sep 28 18:15:54 2022 -0400
committer David Arthur <mumrah@gmail.com> Wed Sep 28 18:15:54 2022 -0400
tree 98719cf68ac8d18cb300918aa22ef3e7651d7c52
parent 971c1e48810cd06936b43c54e2573ee16f2cf827
parent 842c52bf953de680783603feda167084dea67553

Merge remote-tracking branch 'origin/asf-site' into 3.3-doc-publish

33/ops.html

diff --git a/33/ops.html b/33/ops.html
index 9ce0513..e41d274 100644
--- a/33/ops.html
+++ b/33/ops.html
@@ -1388,7 +1388,7 @@
 
   <pre class="line-numbers"><code class="language-bash"> &gt; bin/kafka-storage.sh format --cluster-id uuid --config server_properties</code></pre>
 
-  <p>It is possible for the <code>bin/kafka-storage.sh format<code> command above to fail with a message like <code>Log directory ... is already formatted<code>. This can happend when combined mode is used and only the metadata log directory was lost but not the others. In that case and only in that case, can you run the <code>kafka-storage.sh format</code> command with the <code>--ignore-formatted</code> option.</p>
+  <p>It is possible for the <code>bin/kafka-storage.sh format</code> command above to fail with a message like <code>Log directory ... is already formatted</code>. This can happend when combined mode is used and only the metadata log directory was lost but not the others. In that case and only in that case, can you run the <code>kafka-storage.sh format</code> command with the <code>--ignore-formatted</code> option.</p>
 
   <p>Start the KRaft controller after formatting the log directories.</p>