Various fixes

Author: lucamolteni

_posts/2026-06-15-introducing-quarkus-data.adoc

@@ -51,13 +51,11 @@ Panache provided a repository pattern, a single place to define queries for each
 Since then, the Jakarta EE ecosystem has caught up.
 Jakarta Data <<jd>> standardizes the repository pattern across SQL and NoSQL databases, with an annotation processor that generates implementations at compile time, including full type checking of queries and parameter bindings against your entity model.
 It is a top-level specification in Jakarta EE 11 that supports both Jakarta Persistence and Jakarta NoSQL <<nosql>>.
-
-With Jakarta Data now standardizing what Panache pioneered, it was natural for the Quarkus team to build on it.
-In fact, the influence went both ways: ideas that originated in Panache, like writing partial HQL clauses that restrict a generated query rather than writing the full query from scratch, shaped the direction of the Jakarta Data specification itself.
+With Jakarta Data now providing some of the features Panache pioneered, it was natural for the Quarkus team to build on it.
 
 == Introducing Quarkus Data
 
-We then created "Quarkus Data", an umbrella project for data access in Quarkus.
+We then created "Quarkus Data": an umbrella project for data access in Quarkus.
 It groups all data access extensions we showed earlier under a single name, making it easier to find documentation and understand how the pieces fit together.
 This is the biggest change to data access in Quarkus since the introduction of Panache, and we believe it's a step forward for both new and existing users.
 
@@ -77,7 +75,7 @@ In the future, additional modules like Quarkus Data MongoDB could follow the sam
 
 == Quarkus Data Hibernate
 
-Quarkus Data Hibernate is the entry point for relational database access in Quarkus.
+Quarkus Data Hibernate is now the new entry point for relational database access in Quarkus.
 If you need to talk to a database, this is the one extension you add:
 
 [source,bash]
@@ -100,7 +98,7 @@ This means that it offers an experience that is enjoyable for newcomers of Hiber
 
 Here's a round up of the features it offers:
 
-- **Active Record Pattern support**: persistence operations live directly on your entity by extending a simple class. The simplest way to get started.
+- **Active Record Pattern support**: entity lifecycle operations are on your entity by extending a simple class. The simplest way to get started.
 - **Repositories**: define a standalone repository interface annotated with `@Repository`. The Hibernate annotation processor generates the implementation at compile time, with full type checking of queries and parameters against your entity model.
 - **Stateless and Managed session**: Explicit lifecycles for simple cases, all the power of Hibernate managed objects when you need it.
 - **Reactive**: The same entity model and project work in both blocking and non-blocking modes, useful when you need to interface with reactive code.
@@ -130,7 +128,7 @@ We are working on migration tooling to help existing Panache 1 users transition
 You can try Quarkus Data Hibernate today from Quarkus 3.37.0.
 It will also ship in Quarkus 4.0.
 
-Give it a try and let us know what you think. Feedback is welcome on https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext[Zulip] or via https://github.com/quarkusio/quarkus/issues[GitHub issues].
+Give it a try and let us know what you think. Feedback is welcome on https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Quarkus.20Data/with/602434654[Zulip] or via https://github.com/quarkusio/quarkus/issues[GitHub issues].
 
 [bibliography]
 == References