src/share/classes/javax/sql/package.html

@@ -34,14 +34,13 @@
 
 Provides the API for server side data source access and processing from
 the Java<sup><font size=-2>TM</font></sup> programming language.
 This package supplements the <code>java.sql</code>
 package and, as of the version 1.4 release, is included in the 
-Java Platform, Standard Edition
-(Java SE<sup><font size=-2>TM</sup></font>).
+Java Platform, Standard Edition (Java SE&trade;).
 It remains an essential part of the Java Platform, Enterprise Edition
-(Java EE<sup><font size=-2>TM</sup></font>).
+(Java EE&trade;).
 <P>
 The <code>javax.sql</code> package provides for the following:
 <OL>
   <LI>The <code>DataSource</code> interface as an alternative to the 
       <code>DriverManager</code> for establishing a 

@@ -143,11 +142,10 @@
 connection pool manager will register as a <code>StatementEventListener</code>
 object with the new <code>PooledConnection</code> object.  When the 
 <code>PreparedStatement</code> is closed or there is an error, the connection 
 pool manager (being a listener)
 gets a notification that includes a <code>StatementEvent</code> object.
-<p>
 
 <H2>Distributed Transactions</H2>
 
 As with pooled connections, connections made via a <code>DataSource</code>
 object that is implemented to work with the middle tier infrastructure

@@ -201,18 +199,16 @@
 <P>
 When the <code>RowSet</code> object changes one of its rows, changes all of
 it rows, or moves its cursor, it also notifies each listener that is registered 
 with it.  The listener reacts by carrying out its implementation of the 
 notification method called on it.
-<P>
   <LI><code>RowSetEvent</code><br>
 As part of its internal notification process, a <code>RowSet</code> object
 creates an instance of <code>RowSetEvent</code> and passes it to the listener.
 The listener can use this <code>RowSetEvent</code> object to find out which rowset
 had the event.
 </UL>
-<P>
 <LI>Metadata 
 <UL>
   <LI><code>RowSetMetaData</code><br>
 This interface, derived from the
 <code>ResultSetMetaData</code> interface, provides information about

@@ -224,11 +220,10 @@
 setting the information about columns, but an application would not
 normally use these methods.  When an application calls the <code>RowSet</code> 
 method <code>execute</code>, the <code>RowSet</code> object will contain
 a new set of rows, and its <code>RowSetMetaData</code> object will have been
 internally updated to contain information about the new columns.
-<P>
 </UL>
 <LI>The Reader/Writer Facility<br>
 A <code>RowSet</code> object that implements the <code>RowSetInternal</code>
 interface can call on the <code>RowSetReader</code> object associated with it
 to populate itself with data.  It can also call on the <code>RowSetWriter</code>

@@ -246,11 +241,11 @@
 preceded the current ones, referred to as the <i>original</i> values.  A rowset
 also keeps track of (1) the parameters that have been set for its command and 
 (2) the connection that was passed to it, if any.  A rowset uses the 
 <code>RowSetInternal</code> methods behind the scenes to get access to
 this information.  An application does not normally invoke these methods directly.
-<P>
+
   <LI><code>RowSetReader</code><br>
 A disconnected <code>RowSet</code> object that has implemented the 
 <code>RowSetInternal</code> interface can call on its reader (the 
 <code>RowSetReader</code> object associated with it) to populate it with 
 data.  When an application calls the <code>RowSet.execute</code> method, 

@@ -267,11 +262,10 @@
 <code>RowSetInternal</code> interface can call on its writer (the 
 <code>RowSetWriter</code> object associated with it) to write changes
 back to the underlying data source.  Implementations may vary widely, but
 generally, a writer will do the following:
 
-<P>
 <UL>
   <LI>Make a connection to the data source 
   <LI>Check to see whether there is a conflict, that is, whether
       a value that has been changed in the rowset has also been changed 
       in the data source

@@ -289,11 +283,10 @@
 <P>
 <B>IMPORTANT NOTE:</B> Code that uses API marked "Since 1.6" must be run using a 
 JDBC technology driver that implements the JDBC 4.0 API.
 You must check your driver documentation to be sure that it implements
 the particular features you want to use.
-<P>
 
 <h2>Package Specification</h2>
 
 <ul>
   <li><a href="https://jcp.org/en/jsr/detail?id=221">JDBC 4.2 Specification</a>

@@ -305,9 +298,9 @@
 information about the classes and interfaces in the <code>javax.sql</code>
 package: 
 
 <ul>
   <li><a href="http://www.oracle.com/technetwork/java/index-142838.html">
-          <i>JDBC™API Tutorial and Reference, Third Edition</i></a>
+          <i>JDBC™API Tutorial and Reference, Third Edition</i></a>
 </ul>
 </body>
 </html>