ChangeLogTag: Mon Mar 28 18:44:03 2005 J.T. Conklin <jtc@acorntoolworks.com>

11 files changed, 46 insertions, 28 deletions

diff --git a/TAO/ChangeLog b/TAO/ChangeLog
index 136e4091718..28801f00494 100644
--- a/TAO/ChangeLog
+++ b/TAO/ChangeLog
@@ -1,3 +1,21 @@
+Mon Mar 28 18:44:03 2005  J.T. Conklin  <jtc@acorntoolworks.com>
+
+	* orbsvcs/tests/Event/Mcast/Simple/consumer.cpp:
+
+          Changed #include "orbsvcs/orbsvcs/..." to #include "orbsvcs/...".
+
+	* orbsvcs/Concurrency_Service/README:
+	* orbsvcs/CosEvent_Service/README:
+	* orbsvcs/Logging_Service/Basic_Logging_Service/README:
+	* orbsvcs/Logging_Service/Event_Logging_Service/README:
+	* orbsvcs/Logging_Service/Notify_Logging_Service/README:
+	* orbsvcs/Logging_Service/RTEvent_Logging_Service/README:
+	* orbsvcs/Naming_Service/README:
+	* orbsvcs/Notify_Service/README:
+        * orbsvcs/Time_Service/README:
+
+	  Fix various typos, spelling mistakes, etc.
+
 Mon Mar 28 02:15:09 2005  Ossama Othman  <ossama@dre.vanderbilt.edu>
 
 	* tao/DynamicAny/DynamicAnyC.cpp:
diff --git a/TAO/orbsvcs/Concurrency_Service/README b/TAO/orbsvcs/Concurrency_Service/README
index 007d4fb7b51..5eb1c83a529 100644
--- a/TAO/orbsvcs/Concurrency_Service/README
+++ b/TAO/orbsvcs/Concurrency_Service/README
@@ -23,13 +23,13 @@ $TAO_ROOT/orbsvcs/Concurrency_Service
 
 directory.
 
-The server accepts the folowing options:
+The server accepts the following options:
 
         usage:  ./Concurrency_Service [-d] [-o] <ior_output_file>
         [-d] is the debug option
         [-o] <ior_output_file> outputs the IOR of the lock set factory
              to the file
-        [-s] Prevents the concurency server from using the naming server
+        [-s] Prevents the concurrency server from using the naming server
 
 The lock set factory is registered in the naming service in the
 CosConcurrency context with the name "LockSetFactory".
@@ -44,12 +44,12 @@ the following files:
 
         CC_LockSet.{h,cpp} Implementation of the lock set. At present
 		there is only one implementation of the lock set which
-		implements multiple possesion semantics for both
+		implements multiple possession semantics for both
 		transactional (which is not otherwise supported) and
 		non-transactional clients. Please see the comments in
 		the CC_LockSet.h file for further details.
 
-        CC_LockSetFactory.{h,cpp} Iplementation of the lock set
+        CC_LockSetFactory.{h,cpp} Implementation of the lock set
                 factory
 
         Concurrency_Utils.{h,cpp} Wrapper around the concurrency
diff --git a/TAO/orbsvcs/CosEvent_Service/README b/TAO/orbsvcs/CosEvent_Service/README
index 34e0c70d98e..448f3d47dda 100644
--- a/TAO/orbsvcs/CosEvent_Service/README
+++ b/TAO/orbsvcs/CosEvent_Service/README
@@ -1,7 +1,7 @@
                         CORBA COS Event Service
                         -----------------------
 
-The CosEvent_Service is a COS compilant Event Service.
+The CosEvent_Service is a COS compliant Event Service.
 
 The service is registered with the naming service with the name
 "CosEventService" .  It exposes the <EventChannel> interface which can be
diff --git a/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README
index aab3e4b715b..5288ca240e1 100644
--- a/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README
+++ b/TAO/orbsvcs/Logging_Service/Basic_Logging_Service/README
@@ -7,6 +7,6 @@ To run the Basic Logging Service:
    if not, start one at $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service
 
 2. execute the Basic_Logging_Service
-   at $TAO_ROOT/orbsvcs/Logging_Service/BasicLogging_Service/Basic_Logging_Service
+   at $TAO_ROOT/orbsvcs/Logging_Service/Basic_Logging_Service/Basic_Logging_Service
 
 The idl spec is $TAO_ROOT/orbsvcs/orbsvcs/DsLogAdmin.idl
diff --git a/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README
index 3821c88927a..4977a7bac72 100755
--- a/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README
+++ b/TAO/orbsvcs/Logging_Service/Event_Logging_Service/README
@@ -7,7 +7,7 @@ To run the Event Logging Service:
    if not, start one at $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service
 
 2. execute the Event_Logging_Service
-   at $TAO_ROOT/orbsvcs/Logging_Service/EventLogging_Service/Event_Logging_Service
+   at $TAO_ROOT/orbsvcs/Logging_Service/Event_Logging_Service/Event_Logging_Service
 
 
 The idl spec is $TAO_ROOT/orbsvcs/orbsvcs/DsEventLogAdmin.idl
diff --git a/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README b/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README
index 9dfd86d5e40..282768d11e9 100755
--- a/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README
+++ b/TAO/orbsvcs/Logging_Service/Notify_Logging_Service/README
@@ -7,7 +7,7 @@ To run the Notify Logging Service:
    if not, start one at $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service
 
 2. execute the Notify_Logging_Service
-   at $TAO_ROOT/orbsvcs/Logging_Service/NotifyLogging_Service/Notify_Logging_Service
+   at $TAO_ROOT/orbsvcs/Logging_Service/Notify_Logging_Service/Notify_Logging_Service
 
 
 The idl spec is $TAO_ROOT/orbsvcs/orbsvcs/DsNotifyLogAdmin.idl
diff --git a/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README b/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README
index d34b97f0f60..9f49da0c078 100755
--- a/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README
+++ b/TAO/orbsvcs/Logging_Service/RTEvent_Logging_Service/README
@@ -7,7 +7,7 @@ To run the RTEvent Logging Service:
    if not, start one at $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service
 
 2. execute the Event_Logging_Service
-   at $TAO_ROOT/orbsvcs/Logging_Service/RTEventLogging_Service/RTEvent_Logging_Service
+   at $TAO_ROOT/orbsvcs/Logging_Service/RTEvent_Logging_Service/RTEvent_Logging_Service
 
 
 The idl spec is $TAO_ROOT/orbsvcs/orbsvcs/RTEventLogAdmin.idl
diff --git a/TAO/orbsvcs/Naming_Service/README b/TAO/orbsvcs/Naming_Service/README
index 1bfc7602f4e..67daa651f8a 100644
--- a/TAO/orbsvcs/Naming_Service/README
+++ b/TAO/orbsvcs/Naming_Service/README
@@ -17,7 +17,7 @@ The following describes how to run the TAO Naming Service.
                          [-p pid_file_name]
                          [-s context_size]
                          [-t time]
-                         [-f persitence_file_name]
+                         [-f persistence_file_name]
                          [-b base_address]
 			 [-m (1=enable multicast responses,0=disable(default)]
 			 [-z time]
@@ -63,7 +63,7 @@ The following describes how to run the TAO Naming Service.
 	-m <0|1>
                 TAO offers a simple, very non-standard method for
                 clients to discover the initial reference for the
-                Naming Service.  However, since it can be innadequate and cause
+                Naming Service.  However, since it can be inadequate and cause
 		unexpected results if, for example, there are multiple
 		naming services running on the network, the DEFAULT
 		behavior is for the Naming Service to NOT RESPOND to
@@ -164,7 +164,7 @@ The following describes how to run the TAO Naming Service.
 
                 Example (Unix, same host):
 
-                        % TAO_ROOT/orbsvcs/Naming_Service -o ior_file
+                        % $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service -o ior_file
                         % my_client -ORBInitRef NameService=file://ior_file
 
                         On the first line, we start the Naming
@@ -179,7 +179,7 @@ The following describes how to run the TAO Naming Service.
                 TAO implements the standard CORBA Interoperable Naming
                 Service (ING).  Therefore, most initialization options
                 provided by INS can be used to bootstrap to the Naming
-                Service (see TAO's releasenotes for the status of INS
+                Service (see TAO's release notes for the status of INS
                 implementation).
 
         3. Multicast
@@ -235,7 +235,7 @@ The following describes how to run the TAO Naming Service.
 How to use the NT_Naming_Service
 ================================
 
-To set the options for the TAO Naming Sevice, go to the Services icon
+To set the options for the TAO Naming Service, go to the Services icon
 in the Settings group under the start menu (start menu -> settings ->
 services).  There, highlight the NT_Naming_Service, which is the name
 used by the Naming Service when it is registered.  After it's
@@ -323,7 +323,7 @@ network interfaces( e.g. eth0 ).
 
 ---------------------------------------
 (Step 1)
-Check to see if you have mutlicasting enabled. In the case of Linux
+Check to see if you have multicasting enabled. In the case of Linux
 you will need to check the configuration of your kernel. RedHat users
 have multicasting enabled by default. Once you are sure that you have
 multicast enabled then move to the next step. Alternative is to start
diff --git a/TAO/orbsvcs/Notify_Service/README b/TAO/orbsvcs/Notify_Service/README
index 4a67126e30a..61c8998f1dc 100644
--- a/TAO/orbsvcs/Notify_Service/README
+++ b/TAO/orbsvcs/Notify_Service/README
@@ -42,7 +42,7 @@ Command line arguments:
                           created and registered with the Naming Service.
                           This option is disabled by default.
 
-"-ChannelName channel_name" : Specifes the <channel_name> to register with the
+"-ChannelName channel_name" : Specifies the <channel_name> to register with the
                               Naming Service.
                               The default is "NotifyEventChannel".
 
@@ -57,7 +57,7 @@ option instead.
                                number of worker threads to utilize.
 
 
-Note that the svc.conf file must instruct the oRB to use a TP reactor
+Note that the svc.conf file must instruct the ORB to use a TP reactor
 e.g. static Resource_Factory "-ORBReactorType tp -ORBReactorMaskSignals 0"
 Please look up the ORB configuration options to get more information
 on this.
@@ -135,7 +135,7 @@ The "Notify_Default_Event_Manager_Objects_Factory" service object accepts the fo
                                        "-MTDispatching",
                                        "-MTSourceEval"
                                        "-MTListenerEval"
-                                       *see footnote below for explaination*
+                                       *see footnote below for explanation*
 
 e.g. svc.conf
 static Notify_Default_Event_Manager_Objects_Factory "-MTSourceEval -MTDispatching -DispatchingThreads 2"
@@ -156,7 +156,7 @@ This is the default case.
 When you specify "-AllocateTaskperProxy" it asks notify to create a
 dispatching task (with the specified thread pool size) PER
 PROXYSUPPLIER. So if you use this option and connect 50 consumers with
-1 thread for the dispaching task you will have created 50 dispatching
+1 thread for the dispatching task you will have created 50 dispatching
 threads! so use this option with care and you might not need it in
 most cases.
 
@@ -169,17 +169,17 @@ throughput to it's consumers. (Eventually i want to be able to set the
 thread pool size via a QoS property)
 
 Similarly, the "-MTSourceEval" specifies a thread pool for the filter
-evauation at the proxyconsumer ("Source").
+evaluation at the proxyconsumer ("Source").
 and the "-MTListenerEval" specifies a thread pool for the filter
-evauation at the proxyconsumer ("Listener").
+evaluation at the proxyconsumer ("Listener").
 
 How to use the NT_Notify_Service
 ================================
 
-To set the options for the TAO Notification Sevice, go to the Services
+To set the options for the TAO Notification Service, go to the Services
 icon in the Settings group under the start menu (start menu ->
 settings -> services).  There, highlight the NT_Notify_Service, which
-is the name used by the Notificiation Service when it is registered.
+is the name used by the Notification Service when it is registered.
 After it's highlighted, you should see at the bottom of the dialog box
 an area to specify options.  Just enter the options you wish in that
 edit box and everything should just work.  However, some options, such
diff --git a/TAO/orbsvcs/Time_Service/README b/TAO/orbsvcs/Time_Service/README
index 7bea0a6145a..2ca9f457b45 100644
--- a/TAO/orbsvcs/Time_Service/README
+++ b/TAO/orbsvcs/Time_Service/README
@@ -10,8 +10,8 @@ clerks and the clerks in turn keep their time synchronized
 globally. The clerks do this by talking to the servers running on
 different machines. 
 
-There needs to be atleast one time server running in the network. The Clerks
-update their time periofically from the servers. The servers and clerks
+There needs to be at least one time server running in the network. The Clerks
+update their time periodically from the servers. The servers and clerks
 export their IORs through the
   * Naming Service.
   * Files
diff --git a/TAO/orbsvcs/tests/Event/Mcast/Simple/consumer.cpp b/TAO/orbsvcs/tests/Event/Mcast/Simple/consumer.cpp
index 545bcb9b877..5e8d479e004 100644
--- a/TAO/orbsvcs/tests/Event/Mcast/Simple/consumer.cpp
+++ b/TAO/orbsvcs/tests/Event/Mcast/Simple/consumer.cpp
@@ -2,9 +2,9 @@
 
 #include "Constants.h"
 #include "orbsvcs/Event/EC_Lifetime_Utils_T.h"
-#include "orbsvcs/orbsvcs/Event_Utilities.h"
-#include "orbsvcs/orbsvcs/RtecEventChannelAdminC.h"
-#include "orbsvcs/orbsvcs/RtecEventCommS.h"
+#include "orbsvcs/Event_Utilities.h"
+#include "orbsvcs/RtecEventChannelAdminC.h"
+#include "orbsvcs/RtecEventCommS.h"
 
 class EC_Consumer:
   public POA_RtecEventComm::PushConsumer,