* Update documentation.

Relates to #31

Author: zantvoort

README.adoc

@@ -1428,17 +1428,6 @@ interface UserRepository : EntityRepository<User> {
 ----
 ====
 
-=== Intercepting SQL Statements ===
-
-Storm provides a powerful mechanism called SqlInterceptor for observing and modifying SQL statements generated by the
-template engine. This feature allows you to inspect or alter SQL before it's sent to the database, enabling scenarios
-such as logging, debugging, or applying query transformations.
-
-[NOTE]
-====
-Intercepting SQL statements is primarily intended for logging, diagnostics, debugging, and similar concerns. It is not recommended to use SQL interceptors for implementing business logic or critical application functionality.
-====
-
 === Spring Framework Integration
 
 Spring Framework integration is straightforward. Include the following dependency to tie Storm into your Spring (Boot)
@@ -1548,6 +1537,17 @@ class AcmeRepositoryBeanFactoryPostProcessor : RepositoryBeanFactoryPostProcesso
 ----
 ====
 
+=== Intercepting SQL Statements ===
+
+Storm provides a powerful mechanism called SqlInterceptor for observing and modifying SQL statements generated by the
+template engine. This feature allows you to inspect or alter SQL before it's sent to the database, enabling scenarios
+such as logging, debugging, or applying query transformations.
+
+[NOTE]
+====
+Intercepting SQL statements is primarily intended for logging, diagnostics, debugging, and similar concerns. It is not recommended to use SQL interceptors for implementing business logic or critical application functionality. The `SqlInterceptor` is part of the `storm-core` module, which needs to be made available at compile time in order to use it.
+====
+
 ==== Observing SQL Statements ====
 
 To observe SQL statements without modifying them, you can use an observer: