fix some whitespace in package-infos

hibernate-core/src/main/java/org/hibernate/bytecode/package-info.java

@@ -6,9 +6,9 @@
  */
 
 /**
- *	This package defines an SPI for integrating bytecode libraries with Hibernate.
+ * This package defines an SPI for integrating bytecode libraries with Hibernate.
- *	A bytecode library is used for:
+ * A bytecode library is used for:
- * 	<ol>
+ * <ol>
  * 		<li>
  * 			<b>Reflection optimization</b> - to speed up the performance of entity
  * 			and component construction and field/property access,
@@ -22,6 +22,6 @@
  * 			classes for the purpose of intercepting field-level access, for both
  * 			lazy loading and dirty tracking.
  * 		</li>
- * 	</ol>
+ * </ol>
  */
 package org.hibernate.bytecode;

hibernate-core/src/main/java/org/hibernate/query/criteria/package-info.java

@@ -7,7 +7,7 @@
 
 /**
  * Hibernate's support for JPA criteria queries.
- *
+ * <p>
  * Note JPA criteria are similar to Hibernate's legacy notion
  * of a detached criteria.  Ultimately the criteria tree is transformed
  * into an SQM form and becomes a Query.

hibernate-core/src/main/java/org/hibernate/query/hql/package-info.java

@@ -8,7 +8,7 @@
 /**
  * Package defining support for HQL queries (including supprt for JPQL
  * as a subset of HQL).
- *
+ * <p>
  * This includes transformation via Antlr, {@link org.hibernate.query.Query}
  * manipulation and execution
  *

hibernate-core/src/main/java/org/hibernate/query/results/complete/package-info.java

@@ -9,7 +9,7 @@
  * Support for immutable result/fetch builder graph nodes built from static sources
  * such as JPA's {@link jakarta.persistence.SqlResultSetMapping} or `hbm.xml` mapping
  * {@code <resultset/>}.
- *
+ * <p>
  * The differentiation from {@link org.hibernate.query.results.dynamic} is that here
  * we have up-front knowledge of the complete mapping graph and can perform optimized
  * resolution process

hibernate-core/src/main/java/org/hibernate/query/results/package-info.java

@@ -10,7 +10,7 @@
  * and {@link org.hibernate.procedure.ProcedureCall} / {@link jakarta.persistence.StoredProcedureQuery}.
  * These result-set mappings are used to map the values in the JDBC {@link java.sql.ResultSet}
  * into the query result graph.
- *
+ * <p>
  * NOTE : Handling the different sources of results and fetches is split into multiple packages
  * and multiple impls for performance reasons.  The classes in {@link org.hibernate.query.results.complete}
  * represent result/fetch definitions that are completely known up-front and are faster to

hibernate-core/src/main/java/org/hibernate/sql/ast/tree/package-info.java

@@ -7,7 +7,7 @@
 
 /**
  * Package defining the SQL AST.
- *
+ * <p>
  * {@link org.hibernate.sql.ast.spi} defines support for creating and
  * consuming these trees.
  */

hibernate-core/src/main/java/org/hibernate/sql/exec/package-info.java

@@ -9,7 +9,7 @@
  * Package defining support for execution of SQL statements through JDBC.  The statement
  * to execute is modelled by {@link org.hibernate.sql.exec.spi.JdbcOperationQuery} and
  * are executed via the corresponding executor.
- *
+ * <p>
  * For operations that return ResultSets, be sure to see {@link org.hibernate.sql.results}
  * which provides support for processing results starting with
  * {@link org.hibernate.sql.results.jdbc.spi.JdbcValuesMapping}

hibernate-core/src/main/java/org/hibernate/tuple/package-info.java

@@ -8,7 +8,7 @@
 /**
  * Most contracts here have been replaced by Hibernate's
  * {@linkplain org.hibernate.metamodel.mapping mapping-model}.
- * <p/>
+ * <p>
  * Value-generation related contracts have been replaced by
  * {@link org.hibernate.generator}
  */