From a250feea01b7eee81a011b9d1c1b060af0a3fe9a Mon Sep 17 00:00:00 2001
From: Kefu Chai <kefu.chai@scylladb.com>
Date: Sat, 13 Jul 2024 10:56:33 +0800
Subject: [PATCH] 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 <kefu.chai@scylladb.com>
---
 .../com/datastax/oss/driver/api/core/paging/OffsetPager.java  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java b/core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java
index 3cb838f3171..807f27f3b80 100644
--- a/core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java
+++ b/core/src/main/java/com/datastax/oss/driver/api/core/paging/OffsetPager.java
@@ -46,7 +46,7 @@
  * a reasonable trade-off if the cardinality stays low. This class provides a way to emulate this
  * behavior on the client side.
  *
- * <h3>Performance considerations</h3>
+ * <h2>Performance considerations</h2>
  *
  * For each page that you want to retrieve:
  *
@@ -71,7 +71,7 @@
  * OffsetPager.Page&lt;Row&gt; page5 = pager.getPage(rs, 5);
  * </pre>
  *
- * <h3>Establishing application-level guardrails</h3>
+ * <h2>Establishing application-level guardrails</h2>
  *
  * Linear performance should be fine for the values typically encountered in real-world
  * applications: for example, if the page size is 25 and users never go past page 10, the worst case