diff --git a/hibernate-core/src/main/java/org/hibernate/Cache.java b/hibernate-core/src/main/java/org/hibernate/Cache.java
index 20aca753d0..b8355ae557 100644
--- a/hibernate-core/src/main/java/org/hibernate/Cache.java
+++ b/hibernate-core/src/main/java/org/hibernate/Cache.java
@@ -49,7 +49,7 @@ package org.hibernate;
  * <p>
  * Very occasionally, it's necessary or advantageous to control the cache explicitly
  * via programmatic eviction, using, for example, {@link #evictEntityData(Class)} to
- * evicts a whole cache region, or {@link #evictEntityData(Class, Object)}, to evict
+ * evict a whole cache region, or {@link #evictEntityData(Class, Object)}, to evict
  * a single item.
  * <p>
  * If multiple entities or roles are mapped to the same cache region, they share
diff --git a/hibernate-core/src/main/java/org/hibernate/annotations/package-info.java b/hibernate-core/src/main/java/org/hibernate/annotations/package-info.java
index 4cd79dea24..310c402aea 100644
--- a/hibernate-core/src/main/java/org/hibernate/annotations/package-info.java
+++ b/hibernate-core/src/main/java/org/hibernate/annotations/package-info.java
@@ -209,8 +209,8 @@
  * The JPA-defined {@link jakarta.persistence.Cacheable} annotation is almost useless
  * to us, since:
  * <ul>
- * <li>it provides no way to specify any information about the nature of the <em>how</em>
- *     cached entity and how its cache should be managed, and
+ * <li>it provides no way to specify any information about the nature of the cached
+ *     entity and <em>how</em> its cache should be managed, and
  * <li>it may not be used to annotate associations.
  * </ul>
  * <p>