Fix Antora feature-scroll attribute.

Signed-off-by: Dmitry Sulman <dmitry.sulman@gmail.com>

Closes #3262

src/main/antora/modules/ROOT/pages/index.adoc

@@ -3,7 +3,6 @@
 Oliver Gierke; Thomas Darimont; Christoph Strobl; Mark Pollack; Thomas Risberg; Mark Paluch; Jay Bryant
 :revnumber: {version}
 :revdate: {localdate}
-:feature-scroll: true
 
 (C) 2008-2025 The original authors.
 

src/main/antora/modules/ROOT/pages/repositories/core-concepts.adoc

@@ -1,5 +1,6 @@
 [[repositories.core-concepts]]
 = Core concepts
+:feature-scroll:
 
 The central interface in the Spring Data repository abstraction is `Repository`.
 It takes the domain class to manage as well as the identifier type of the domain class as type arguments.

src/main/antora/modules/ROOT/pages/repositories/query-methods-details.adoc

@@ -1,5 +1,6 @@
 [[repositories.query-methods.details]]
 = Defining Query Methods
+:feature-scroll:
 
 The repository proxy has two ways to derive a store-specific query from the method name:
 
@@ -457,10 +458,10 @@ ifdef::feature-scroll[]
 | `limit + 1` at `OffsetScrollPosition.getOffset()`
 | One to many queries fetching data starting at `OffsetScrollPosition.getOffset()` applying limiting.
 a| A `Window` can only navigate to the next `Window`.
-endif::[]
 
 * `Window` provides details whether there is more data to fetch.
 * Offset-based queries becomes inefficient when the offset is too large because the database still has to materialize the full result.
+endif::[]
 
 | `Page<T>`
 | `Pageable.getPageSize()`  at `Pageable.getOffset()`
@@ -518,8 +519,6 @@ QSort sort = QSort.by(QPerson.firstname.asc())
   .and(QSort.by(QPerson.lastname.desc()));
 ----
 
-ifdef::feature-scroll[]
-endif::[]
 
 [[repositories.limit-query-result]]
 === Limiting Query Results