Skip to content

Commit a250fee

Browse files
committed
use h2 for top-level header
otherwise javadoc complains: ``` [ERROR] /tmp/tmp3xdp27n9/4c8eec7e8183f75869e1154d4ed490149e848e80/core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java:47: error: headi ng used out of sequence: <H3>, compared to implicit preceding heading: <H1> [ERROR] * <h3>Performance considerations</h3> [ERROR] ^ ``` Signed-off-by: Kefu Chai <[email protected]>
1 parent 0042cdb commit a250fee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@
4646
* a reasonable trade-off if the cardinality stays low. This class provides a way to emulate this
4747
* behavior on the client side.
4848
*
49-
* <h3>Performance considerations</h3>
49+
* <h2>Performance considerations</h2>
5050
*
5151
* For each page that you want to retrieve:
5252
*
@@ -71,7 +71,7 @@
7171
* OffsetPager.Page&lt;Row&gt; page5 = pager.getPage(rs, 5);
7272
* </pre>
7373
*
74-
* <h3>Establishing application-level guardrails</h3>
74+
* <h2>Establishing application-level guardrails</h2>
7575
*
7676
* Linear performance should be fine for the values typically encountered in real-world
7777
* applications: for example, if the page size is 25 and users never go past page 10, the worst case

0 commit comments

Comments
 (0)