From f6e7063174678863aeb50e5d36256c92f223277e Mon Sep 17 00:00:00 2001 From: jmcb Date: Thu, 5 Sep 2024 16:30:53 +0100 Subject: [PATCH] Fix typo in definition.adoc --- src/main/antora/modules/ROOT/pages/repositories/definition.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/antora/modules/ROOT/pages/repositories/definition.adoc b/src/main/antora/modules/ROOT/pages/repositories/definition.adoc index 3b6f92ae88..44de48c585 100644 --- a/src/main/antora/modules/ROOT/pages/repositories/definition.adoc +++ b/src/main/antora/modules/ROOT/pages/repositories/definition.adoc @@ -18,7 +18,7 @@ If you are using a reactive store you might choose `ReactiveCrudRepository`, or If you are using Kotlin you might pick `CoroutineCrudRepository` which utilizes Kotlin's coroutines. -Additional you can extend `PagingAndSortingRepository`, `ReactiveSortingRepository`, `RxJava3SortingRepository`, or `CoroutineSortingRepository` if you need methods that allow to specify a `Sort` abstraction or in the first case a `Pageable` abstraction. +Additionally you can extend `PagingAndSortingRepository`, `ReactiveSortingRepository`, `RxJava3SortingRepository`, or `CoroutineSortingRepository` if you need methods that allow to specify a `Sort` abstraction or in the first case a `Pageable` abstraction. Note that the various sorting repositories no longer extended their respective CRUD repository as they did in Spring Data Versions pre 3.0. Therefore, you need to extend both interfaces if you want functionality of both.