--- old/src/java.naming/share/classes/javax/naming/event/package.html	2015-08-04 13:14:50.820900756 +0300
+++ new/src/java.naming/share/classes/javax/naming/event/package.html	2015-08-04 13:14:50.528900750 +0300
@@ -42,21 +42,21 @@
 
 <h4>Naming Events</h4>
 <p>
-This package defines a <tt>NamingEvent</tt> class to represent an event
+This package defines a <code>NamingEvent</code> class to represent an event
 that is generated by a naming/directory service.
-It also defines subinterfaces of <tt>Context</tt> and <tt>DirContext</tt>,
-called <tt>EventContext</tt> and <tt>EventDirContext</tt>,
+It also defines subinterfaces of <code>Context</code> and <code>DirContext</code>,
+called <code>EventContext</code> and <code>EventDirContext</code>,
 through which applications can register their interest in events
 fired by the context.
 <p>
-<tt>NamingEvent</tt> represents an event that occurs in a 
+<code>NamingEvent</code> represents an event that occurs in a 
 naming or directory service. There are two categories of naming events:
 <ul>
 <li>Those that affect the namespace (add/remove/rename an object)
 <li>Those that affect the objects' contents.
 </ul>
 Each category of events is handled by a corresponding listener:
-<tt>NamespaceChangeListener</tt>, <tt>ObjectChangeListener</tt>.
+<code>NamespaceChangeListener</code>, <code>ObjectChangeListener</code>.
 <p>
 An application, for example, can register its interest in changes to
 objects in a context as follows:
@@ -82,19 +82,19 @@
 <h4>Threading Issues</h4>
 
 When an event is dispatched to a listener, the listener method (such
-as <tt>objectChanged()</tt>) may be executed in a thread other than the
-one in which the call to <tt>addNamingListener()</tt> was executed.
+as <code>objectChanged()</code>) may be executed in a thread other than the
+one in which the call to <code>addNamingListener()</code> was executed.
 The choice of which thread to use is made by the service provider.
 When an event is dispatched to multiple listeners, the service provider
 may choose (and is generally encouraged) to execute the listener methods
 concurrently in separate threads.
 <p>
-When a listener instance invokes <tt>NamingEvent.getEventContext()</tt>,
+When a listener instance invokes <code>NamingEvent.getEventContext()</code>,
 it must take into account the possibility that other threads will be
 working with that context concurrently.  Likewise, when a listener is
-registered via <tt>addNamingListener()</tt>, the registering thread
+registered via <code>addNamingListener()</code>, the registering thread
 must take into account the likely possibility that the service provider
-will later invoke the listeners in newly-created threads.  As <tt>Context</tt>
+will later invoke the listeners in newly-created threads.  As <code>Context</code>
 instances are not guaranteed to be thread-safe in general, all context
 operations must be synchronized as needed.
 
@@ -107,9 +107,9 @@
 on the server that will eventually be translated into events.
 If an exception occurs that prevents information about the events from
 being collected, the listener will never be notified of the events.
-When such an exception occurs, a <tt>NamingExceptionEvent</tt> is
+When such an exception occurs, a <code>NamingExceptionEvent</code> is
 fired to notify the listener. The listener's
-<tt>namingExceptionThrown()</tt> method is invoked, as shown in the 
+<code>namingExceptionThrown()</code> method is invoked, as shown in the 
 sample code above,
 and the listener is automatically deregistered.