Revert "KAFKA-16101: Additional fixes on KRaft migration documentation (

apache#15287)"

This reverts commit 46d7626.

docs/ops.html

@@ -4045,7 +4045,7 @@ <h3>Reverting to ZooKeeper mode During the Migration</h3>
  <li>
  On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
  <code>controller.listener.names</code>, and <code>controller.quorum.voters</code>
- configurations.
+ configurations, and replace <code>node.id</code> with <code>broker.id</code>.
  Then perform a rolling restart of all brokers.
  </li>
  <li>
@@ -4054,7 +4054,7 @@ <h3>Reverting to ZooKeeper mode During the Migration</h3>
  </ul>
  </td>
  <td>
- It is important to perform the <code>zookeeper-shell.sh</code> step quickly together with rolling at least one broker (into pure ZooKeeper mode), to minimize the amount of
+ It is important to perform the <code>zookeeper-shell.sh</code> step quickly, to minimize the amount of
  time that the cluster lacks a controller.
  </td>
  </tr>
@@ -4063,8 +4063,7 @@ <h3>Reverting to ZooKeeper mode During the Migration</h3>
  <td>
  <ul>
  <li>
- On each broker, remove the <code>process.roles</code> configuration,
- replace the <code>node.id</code> with <code>broker.id</code> and
+ On each broker, remove the <code>process.roles</code> configuration, and
  restore the <code>zookeeper.connect</code> configuration to its previous value.
  If your cluster requires other ZooKeeper configurations for brokers, such as
  <code>zookeeper.ssl.protocol</code>, re-add those configurations as well.
@@ -4080,7 +4079,7 @@ <h3>Reverting to ZooKeeper mode During the Migration</h3>
  <li>
  On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
  <code>controller.listener.names</code>, and <code>controller.quorum.voters</code>
- configurations.
+ configurations. Replace <code>node.id</code> with <code>broker.id</code>.
  Then perform a second rolling restart of all brokers.
  </li>
  <li>
@@ -4091,7 +4090,7 @@ <h3>Reverting to ZooKeeper mode During the Migration</h3>
  <td>
  <ul>
  <li>
- It is important to perform the <code>zookeeper-shell.sh</code> step <b>quickly</b> together with rolling at least one broker (into pure ZooKeeper mode), to minimize the amount of
+ It is important to perform the <code>zookeeper-shell.sh</code> step <b>quickly</b>, to minimize the amount of
  time that the cluster lacks a controller.
  </li>
  <li>