Skip to content

Commit dc96297

Browse files
committed
Fix a couple of typo's
Signed-off-by: Jan Schatteman <[email protected]>
1 parent e7c3f52 commit dc96297

File tree

1 file changed

+2
-2
lines changed
  • documentation/src/main/asciidoc/userguide/chapters/caching

1 file changed

+2
-2
lines changed

documentation/src/main/asciidoc/userguide/chapters/caching/Caching.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -263,7 +263,7 @@ This is useful for frequently executed queries with fixed parameter values.
263263

264264
[NOTE]
265265
====
266-
Caching of query results introduces some overhead in terms of your applications normal transactional processing.
266+
Caching of query results introduces some overhead in terms of your application's normal transactional processing.
267267
For example, if you cache results of a query against `Person`,
268268
Hibernate will need to keep track of when those results should be invalidated because changes have been committed against any `Person` entity.
269269
@@ -392,7 +392,7 @@ include::{example-dir-caching}/SecondLevelCacheTest.java[tags=caching-query-regi
392392
[[caching-query-cache-layout]]
393393
=== Query cache layout
394394

395-
The query cache usually contains the same data that is read from the original queries JDBC `ResultSet`,
395+
The query cache usually contains the same data that is read from the original query's JDBC `ResultSet`,
396396
but for entities and collections the cached information can vary depending on configuration.
397397

398398
An entity or collection in the query cache can either be represented with all its fetched data (`FULL` cache layout),

0 commit comments

Comments
 (0)