Doxygen fixes

4 files changed, 8 insertions, 8 deletions

diff --git a/TAO/tao/Messaging/Asynch_Reply_Dispatcher.cpp b/TAO/tao/Messaging/Asynch_Reply_Dispatcher.cpp
index 90a1c4223a7..22ae0b71339 100644
--- a/TAO/tao/Messaging/Asynch_Reply_Dispatcher.cpp
+++ b/TAO/tao/Messaging/Asynch_Reply_Dispatcher.cpp
@@ -67,7 +67,7 @@ TAO_Asynch_Reply_Dispatcher::dispatch_reply (TAO_Pluggable_Reply_Params &params)
     }
 
   // See whether we need to delete the data block by checking the
-  // flags. We cannot be happy that we initally allocated the
+  // flags. We cannot be happy that we initially allocated the
   // datablocks of the stack. If this method is called twice, as is in
   // some cases where the same invocation object is used to make two
   // invocations like forwarding, the release becomes essential.
diff --git a/TAO/tao/Synch_Invocation.cpp b/TAO/tao/Synch_Invocation.cpp
index de7f3e18ad4..82e21b6d15b 100644
--- a/TAO/tao/Synch_Invocation.cpp
+++ b/TAO/tao/Synch_Invocation.cpp
@@ -143,7 +143,7 @@ namespace TAO
         countdown.update ();
 
         // For some strategies one may want to release the transport
-        // back to  cache. If the idling is successful let the
+        // back to cache. If the idling is successful let the
         // resolver about that.
         if (transport->idle_after_send ())
           this->resolver_.transport_released ();
@@ -152,7 +152,7 @@ namespace TAO
         // here; need to investigate.  Client threads would frequently be
         // canceled sometime during recv_request ... the correct action to
         // take on being canceled is to issue a CancelRequest message to the
-        // server and then imediately let other client-side cancellation
+        // server and then immediately let other client-side cancellation
         // handlers do their jobs.
         //
         // In C++, that basically means to unwind the stack using almost
diff --git a/TAO/tao/Transport.h b/TAO/tao/Transport.h
index 5a768714b81..52f6976eb38 100644
--- a/TAO/tao/Transport.h
+++ b/TAO/tao/Transport.h
@@ -244,14 +244,14 @@ namespace TAO
  *  - Minimize locking and copying overhead when trying to attack the
  *    above.
  *
- * <H3> Parsing messages (GIOP) & processing the message:</H3>
+ * <H3>Parsing messages (GIOP) & processing the message:</H3>
  *
  * The messages should be checked for validity and the right
  * information should be sent to the higher layer for processing. The
  * process of doing a sanity check and preparing the messages for the
  * higher layers of the ORB are done by the messaging protocol.
  *
- * <H3> Design forces and Challenges </H3>
+ * <H3>Design forces and Challenges </H3>
  *
  * To keep things as efficient as possible for medium sized requests,
  * it would be good to minimize data copying and locking along the
@@ -293,7 +293,7 @@ namespace TAO
  *       message from the queue and processes that. Once the queue
  *       is drained the last thread resumes the handle.
  *
- * <H3> Sending Replies </H3>
+ * <H3>Sending Replies </H3>
  *
  * We could use the outgoing path of the ORB to send replies. This
  * would allow us to reuse most of the code in the outgoing data
@@ -304,7 +304,7 @@ namespace TAO
  * Reactor could potentially handle other messages (incoming or
  * outgoing) and the stack starts growing leading to crashes.
  *
- * <H4> Solution to the nesting problem </H4>
+ * <H4>Solution to the nesting problem </H4>
  *
  * The solution that we (plan to) adopt is pretty straight
  * forward. The thread sending replies will not block to send the
diff --git a/TAO/tao/Transport_Mux_Strategy.h b/TAO/tao/Transport_Mux_Strategy.h
index 94eeef24060..ba7ebd62068 100644
--- a/TAO/tao/Transport_Mux_Strategy.h
+++ b/TAO/tao/Transport_Mux_Strategy.h
@@ -58,7 +58,7 @@ public:
 
   /**
    * Unbind the dispatcher, the client is no longer waiting for the
-   * request, for example, because the request timedout.
+   * request, for example, because the request timed out.
    * The strategy can (must) cleanup any resources associated with the
    * request.
    * A later reply for that request should be ignored.