Fix spelling

Author: lucamolteni

_posts/2025-06-18-hibernate7-on-quarkus.adoc

@@ -63,8 +63,7 @@ After the deprecation of the Hibernate Criteria API, developers were still missi
 [source,java]
 ----
 var books =
-    SelectionSpecification.create(Book.class,
-            "from Book where discontinued = false")
+    SelectionSpecification.create(Book.class, "from Book where discontinued = false")
         .restrict(Restriction.startsWith(Book_.title, "hibernate"))
         .sort(Order.desc(Book_.title))
         .fetch(Path.from(Book.class).to(Book_publisher))
@@ -81,7 +80,7 @@ List<Book> books(Restriction<Book> restriction,
                  Order<Book> order);
 ```
 
-When user will call the method, they can pass the `Restriction` objects to fitler the wanted book.
+When user will call the method, they can pass the `Restriction` objects to filter the wanted book.
 
 ```java
 var books =
@@ -92,8 +91,10 @@ var books =
 
 === Hibernate Reactive together with Hibernate ORM
 
-A long-awaited feature is the ability to https://github.com/quarkusio/quarkus/issues/13425[mix Hibernate ORM and Hibernate Reactive extensions] in the same Quarkus application. Without this feature, making the two extensions coexist required workarounds that are now unnecessary as, since Quarkus 3.24, it is now possible to mix the two.
+A long-awaited feature is the ability to https://github.com/quarkusio/quarkus/issues/13425[mix Hibernate ORM and Hibernate Reactive extensions] in the same Quarkus application. Without this feature, making the two extensions coexist required workarounds that are now unnecessary as, since Quarkus 3.2.4, it is now possible to mix the two.
+
 Hibernate Reactive is a powerful reactive data access abstraction, but its advantages vary per project. Instead of dictating usage, we enable users to experiment easily with both Hibernate ORM and Reactive. Projects using Hibernate ORM can add the Reactive extension, create reactive resources reusing mapped entities, running tests and benchmarks, and determine if it suits their specific needs and scalability goals. While using both, it’s easier to choose the most suitable approach for different use cases. Another benefit is that it makes it easier to migrate in small steps from one to the other as necessary.
+
 Panache users will have this possibility in the API as well starting from https://github.com/quarkusio/quarkus/issues/46096[Panache 2.0]
 
 === Injection of the SchemaManager
@@ -108,7 +109,7 @@ image::console.gif[scaledwidth=100%]
 
 We’re working on improving the Hibernate Reactive extension as well, by providing support for https://github.com/quarkusio/quarkus/pull/48007[Named Data Sources and Named Persistence Units].
 
-Also, as part of giving a better experience for the user, the Quarkus and Hibernate teams constantly collaborate on performance and efficiency improvements. For example, an optimization that https://hibernate.atlassian.net/browse/HHH-18326[avoids the need for an `IdentityHasMap` to track persistence entities] improved the performance by https://github.com/hibernate/hibernate-orm-benchmark/pull/15[8% while running a simple query of 100-1000 immutable entities], end even more when dealing with persistent collections.
+Also, as part of giving a better experience for the user, the Quarkus and Hibernate teams constantly collaborate on performance and efficiency improvements. For example, an optimization that https://hibernate.atlassian.net/browse/HHH-18326[avoids the need for an `IdentityHashMap` to track persistence entities] improved the performance by https://github.com/hibernate/hibernate-orm-benchmark/pull/15[8% while running a simple query of 100-1000 immutable entities], end even more when dealing with persistent collections.
 And that's just _one_ improvement among many, and not the last one: even bigger performance improvements are expected in the future.
 
 https://quarkus.io/guides/update-quarkus[Take a look at the new release] and let us know what you think!