From f60d209703ac4e1d375a9670d2a655edd57185a8 Mon Sep 17 00:00:00 2001
From: Johnny Willemsen <jwillemsen@remedy.nl>
Date: Tue, 29 Oct 2019 12:34:40 +0100
Subject: Fixed typos

    * ACE/ace/Service_Gestalt.h:
    * TAO/docs/notification/reliability.html:
    * TAO/orbsvcs/tests/Log/Basic_Log_Test/Basic_Log_Test.cpp:
    * TAO/orbsvcs/tests/Log/Basic_Log_Test/Basic_Log_Test.h:
    * TAO/orbsvcs/tests/Security/mixed_security_test/README:
---
 TAO/docs/notification/reliability.html | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

(limited to 'TAO/docs')

diff --git a/TAO/docs/notification/reliability.html b/TAO/docs/notification/reliability.html
index 2afc6272015..49b2d9a059a 100644
--- a/TAO/docs/notification/reliability.html
+++ b/TAO/docs/notification/reliability.html
@@ -281,19 +281,19 @@
     <P>The interfaces involved are defined in the NotifyExt.idl file (in
       $TAO_ROOT/orbsvcs/orbsvcs) and are shown here:</P>
   <pre>
-  /** 
+  /**
    * \brief An interface which gets registered with a ReconnectionRegistry.
-   * 
-   * A supplier or consumer must implement this interface in order to 
-   * allow the Notification Service to attempt to reconnect to it after 
-   * a failure.  The supplier or consumer must register its instance of 
+   *
+   * A supplier or consumer must implement this interface in order to
+   * allow the Notification Service to attempt to reconnect to it after
+   * a failure.  The supplier or consumer must register its instance of
    * this interface with the ReconnectionRegistry.
-   */ 
+   */
   interface ReconnectionCallback
-  { 
-    /// Perform operations to reconnect to the Notification Service 
+  {
+    /// Perform operations to reconnect to the Notification Service
     /// after a failure.
-    void reconnect (in Object new_connection); 
+    void reconnect (in Object new_connection);
 
     /// Check to see if the ReconnectionCallback is alive
     boolean is_alive ();
@@ -335,7 +335,7 @@
     </P>
     <P>Application code in the Consumer should be written with the knowledge that
       events are guaranteed to be delivered, but during recovery from a failure there
-      is a possiblity that an event may arrive more than once.&nbsp; This could
+      is a possibility that an event may arrive more than once.&nbsp; This could
       happen, for example if the event was in the process of being delivered at the
       time the failure occurred and the failure prevents the Notfication service from
       determining if the delivery completed successfully.&nbsp; To meet its
-- 
cgit v1.2.1