Fix javadoc compatibility

[mdsal.git] / dom / mdsal-dom-api / src / main / java / org / opendaylight / mdsal / dom / api / DOMDataTreeWriteTransaction.java

diff --git a/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeWriteTransaction.java b/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeWriteTransaction.java
index fb11711c03ea6cbe455b62c3d46b1bc97e01e89f..9c06d7d589a1f2e23ba73bcb0c9e4a5383c3ab64 100644 (file)
--- a/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeWriteTransaction.java
+++ b/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeWriteTransaction.java
@@ -107,7 +107,7 @@ public interface DOMDataTreeWriteTransaction extends DOMDataTreeTransaction, DOM
      * The effects of a successful commit of data depends on listeners and commit participants that are registered with
      * the data broker.
      *
-     * <h3>Example usage:</h3>
+     * <h4>Example usage:</h4>
      * <pre>
      *  private void doWrite(final int tries) {
      *      WriteTransaction writeTx = dataBroker.newWriteOnlyTransaction();
@@ -135,7 +135,7 @@ public interface DOMDataTreeWriteTransaction extends DOMDataTreeTransaction, DOM
      * doWrite(2);
      * </pre>
      *
-     * <h2>Failure scenarios</h2>
+     * <h4>Failure scenarios</h4>
      *
      * <p>
      * Transaction may fail because of multiple reasons, such as
@@ -158,7 +158,7 @@ public interface DOMDataTreeWriteTransaction extends DOMDataTreeTransaction, DOM
      *   </li>
      * </ul>
      *
-     * <h3>Change compatibility</h3>
+     * <h4>Change compatibility</h4>
      * There are several sets of changes which could be considered incompatible between two transactions which are
      * derived from same initial state. Rules for conflict detection applies recursively for each subtree level.
      *
@@ -405,9 +405,9 @@ public interface DOMDataTreeWriteTransaction extends DOMDataTreeTransaction, DOM
      * </table>
      *
      *
-     * <h3>Examples of failure scenarios</h3>
+     * <h4>Examples of failure scenarios</h4>
      *
-     * <h4>Conflict of two transactions</h4>
+     * <h5>Conflict of two transactions</h5>
      * This example illustrates two concurrent transactions, which derived from same initial state
      * of data tree and proposes conflicting modifications.
      *