fix some obvious defect in javadoc for resource/transaction package

Author: nathan.xu

hibernate-core/src/main/java/org/hibernate/resource/transaction/backend/jta/internal/DdlTransactionIsolatorJtaImpl.java

@@ -81,7 +81,7 @@ public Connection getIsolatedConnection(boolean autocommit) {
 				}
 			}
 			catch (SQLException e) {
-				throw jdbcContext.getSqlExceptionHelper().convert( e, "Unable set JDBC Connection for DDL execution to autocommit" );
+				throw jdbcContext.getSqlExceptionHelper().convert( e, "Unable to set JDBC Connection for DDL execution to autocommit" );
 			}
 		}
 		return jdbcConnection;

hibernate-core/src/main/java/org/hibernate/resource/transaction/backend/jta/internal/JtaTransactionCoordinatorImpl.java

@@ -376,7 +376,7 @@ public void removeObserver(TransactionObserver observer) {
 
 	/**
 	 * Implementation of the LocalInflow for this TransactionCoordinator.  Allows the
-	 * local transaction ({@link org.hibernate.Transaction} to callback into this
+	 * local transaction ({@link org.hibernate.Transaction}) to callback into this
 	 * TransactionCoordinator for the purpose of driving the underlying JTA transaction.
 	 */
 	public class TransactionDriverControlImpl implements TransactionDriver {

hibernate-core/src/main/java/org/hibernate/resource/transaction/backend/jta/internal/synchronization/SynchronizationCallbackCoordinatorTrackingImpl.java

@@ -35,7 +35,7 @@ public void reset() {
 		// 		1) on initialization, and
 		// 		2) after "after completion" handling is finished.
 		//
-		// Here we use that to "clear out" all 'delayed after-completion" state.  The registrationThreadId will
+		// Here we use that to "clear out" all "delayed after-completion" state.  The registrationThreadId will
 		// "lazily" be re-populated on the next synchronizationRegistered call to allow for the potential of the
 		// next Session transaction occurring on a different thread (though that transaction would need to completely
 		// operate on that thread).
@@ -46,7 +46,7 @@ public void reset() {
 	public void afterCompletion(int status) {
 		log.tracef( "Synchronization coordinator: afterCompletion(status=%s)", status );
 
-		// The whole concept of "tracking" comes down to this code block..
+		// The whole concept of "tracking" comes down to this code block.
 		// Essentially we need to see if we can process the callback immediately.  So here we check whether the
 		// current call is happening on the same thread as the thread under which we registered the Synchronization.
 		// As far as we know, this can only ever happen in the rollback case where the transaction had been rolled

hibernate-core/src/main/java/org/hibernate/resource/transaction/backend/jta/internal/synchronization/SynchronizationCallbackTarget.java

@@ -8,7 +8,7 @@
  * Defines "inflow" for JTA transactions from the perspective of Hibernate's registered JTA Synchronization
  * back into the TransactionCoordinator by means of the SynchronizationCallbackCoordinator.
  * <p>
- * That's a mouthful :)  The way it works is like this...<ul>
+ * That's a mouthful, :).  The way it works is like this...<ul>
  *     <li>
  *         Hibernate will register a JTA {@link jakarta.transaction.Synchronization} implementation
  *         ({@link RegisteredSynchronization}) which allows

hibernate-core/src/main/java/org/hibernate/resource/transaction/spi/TransactionCoordinatorBuilder.java

@@ -20,7 +20,7 @@
  */
 public interface TransactionCoordinatorBuilder extends Service {
 	/**
-	 * Access to options to are specific to each {@link TransactionCoordinator} instance.
+	 * Access to options that are specific to each {@link TransactionCoordinator} instance.
 	 */
 	interface Options {
 		/**

hibernate-core/src/main/java/org/hibernate/resource/transaction/spi/TransactionCoordinatorOwner.java

@@ -37,7 +37,7 @@ default void startTransactionBoundary() {
 	}
 
 	/**
-	 * A after-begin callback from the coordinator to its owner.
+	 * An after-begin callback from the coordinator to its owner.
 	 */
 	void afterTransactionBegin();