diff --git a/documentation/src/main/asciidoc/introduction/Tuning.adoc b/documentation/src/main/asciidoc/introduction/Tuning.adoc
index ade9d9af0c4e..cb91c7bef841 100644
--- a/documentation/src/main/asciidoc/introduction/Tuning.adoc
+++ b/documentation/src/main/asciidoc/introduction/Tuning.adoc
@@ -870,7 +870,7 @@ StatelessSession ss = getSessionFactory().openStatelessSession();
 
 A stateless session:
 
-- doesn't have a first-level cache (persistence context), nor does it interact with any second-level caches, and
+- doesn't have a first-level cache (persistence context), and
 - doesn't implement transactional write-behind or automatic dirty checking, so all operations are executed immediately when they're explicitly called.
 
 For a stateless session, we're always working with detached objects.
diff --git a/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc b/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc
index eb124111ab25..a7e0e9dbc7dc 100644
--- a/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc
+++ b/documentation/src/main/asciidoc/userguide/chapters/batch/Batching.adoc
@@ -125,8 +125,7 @@ However, it is good practice to close the `ScrollableResults` explicitly.
 
 Thus, a stateless session is a slightly lower-level abstraction that's closer to the underlying JDBC activity:
 
-* there's no first-level cache,
-* the stateless session does not interact with any second-level or query cache, and
+* there's no first-level cache, and
 * there's no transactional write-behind or automatic dirty checking.
 
 Instead, persistence operations occur synchronously when a method of `StatelessSession` is invoked, and entities returned by a stateless session are always detached.
@@ -140,9 +139,8 @@ With a stateless session, there's no need to explicitly manage the size of the f
 The `StatelessSession` API comes with certain limitations:
 
 * operations performed using a stateless session never cascade to associated instances,
-* collections are ignored by a stateless session,
 * lazy loading of associations is not transparent, and is only available via an explicit operation named `fetch()`, and
-* operations performed via a stateless session bypass Hibernate's event model and interceptors.
+* operations performed via a stateless session bypass Hibernate's event model and action queue.
 
 IMPORTANT: Due to the lack of a first-level cache, stateless sessions are vulnerable to data aliasing effects.