Clarified some statements.

1 files changed, 15 insertions, 12 deletions

diff --git a/TAO/docs/interceptors.html b/TAO/docs/interceptors.html
index a29b8aae94e..b54a64d993a 100644
--- a/TAO/docs/interceptors.html
+++ b/TAO/docs/interceptors.html
@@ -72,7 +72,7 @@ interception points including (1) <CODE>send_request</CODE>,
 (4) <CODE>receive_reply</CODE>, (5) <CODE>send_exception</CODE>,
 (6) <CODE>receive_exception</CODE>, and
 (7) <CODE>establish_components</CODE> (specific to
-<CODE>IORInterceptor</CODE>s.  Each request interception point is
+<CODE>IORInterceptor</CODE>s).  Each request interception point is
 passed a <CODE>RequestInfo</CODE> object which encapsulates the
 details of the operation like arguments, etc.  The IOR interception
 point is passed an <CODE>IORInfo</CODE> object that encapsulates
@@ -299,12 +299,12 @@ module PortableInterceptor
 <h3><a name="status">Current Status</a></h3>
 <ul>
   <li>The basic infrastructure is in place as well as the canonical
-      interception points:  <CODE>send_request</CODE>,
+      request interception points:  <CODE>send_request</CODE>,
       <CODE>receive_request</CODE>, <CODE>send_exception</CODE>,
       <CODE>receive_exception</CODE>, <CODE>send_reply</CODE>, and
-      <CODE>receive_reply</CODE>.  The other interception points are
-      mostly for specific applications like AMI, FT, etc. which will
-      be implemented as and when needed.
+      <CODE>receive_reply</CODE>.  The remaining request interception
+      points are mostly for specific applications like AMI, FT,
+      etc. which will be implemented as and when needed.
   <li><CODE>ORBInitializer</CODE> registration has been implemented,
       as per the spec.
   <li>Registration of interceptors is now conformant to the spec
@@ -319,9 +319,10 @@ module PortableInterceptor
       the <CODE>ORB::create_policy</CODE> method.
   <li>Initial reference registration, i.e.
       <CODE>ORBInitInfo::register_initial_reference</CODE>, has been
-      implemented.  This particularly useful for registering local
+      implemented.  This is particularly useful for registering local
       objects with the ORB's <CODE>resolve_initial_references</CODE>
-      since they can't be stringified and registered via -ORBInitRef.
+      mechanism since they can't be stringified and registered via
+      <CODE>-ORBInitRef</CODE> ORB option.
   <li>Basically, all <CODE>ORBInitInfo</CODE> methods have been
       implemented except <CODE>allocate_slot_id</CODE> and
       <CODE>codec_factory</CODE>.
@@ -330,9 +331,10 @@ module PortableInterceptor
 <hr><P>
 <h2><a name="future">Future Work</a></h2>
 <ol>
-  <li>Add support for the interceptor chain to <CODE>ThruPOA</CODE>
-      collocation optimization; the <CODE>direct</CODE> collocation
-      optimization will not go through the interceptor chain.
+  <li>Add support for the <CODE>ThruPOA</CODE> collocation
+      optimization to the interceptor chain; the <CODE>direct</CODE>
+      collocation optimization will not go through the interceptor
+      chain.
   <li>Implement the <CODE>PortableInterceptor::Current</CODE>
       interface.  Useful for passing data between interceptors.
   <li>Implement the <CODE>CodecFactory</CODE> interface, and an
@@ -352,8 +354,9 @@ module PortableInterceptor
   <li>The current implementation does not go through the interceptor chain
       when using collocation optimizations such as <CODE>direct</CODE> or
       <CODE>ThruPOA</CODE>.
-  <li>While multiple interceptors have been implemented, their
-      compliance with the <em>General Flow Rules</em> must be improved.
+  <li>While multiple request interceptor support has been implemented,
+      its compliance with the <em>General Flow Rules</em> dictated in
+      the Portable Interceptor specification must be improved.
 </ul>
 
 <hr><P>