From 2e72cd5a4d1dfcc0044bf874eb43ae7e9ebbee3b Mon Sep 17 00:00:00 2001 From: Johnny Willemsen Date: Wed, 15 Mar 2017 14:53:23 +0100 Subject: Fixed typos * TAO/docs/orbsvcs.html: * TAO/docs/pluggable_protocols/index.html: * TAO/docs/releasenotes/ftrt_ec.html: * TAO/docs/releasenotes/index.html: * TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp: * TAO/tests/NestedUpcall/MT_Client_Test/client.cpp: --- TAO/docs/orbsvcs.html | 6 +++--- TAO/docs/pluggable_protocols/index.html | 2 +- TAO/docs/releasenotes/ftrt_ec.html | 2 +- TAO/docs/releasenotes/index.html | 2 +- TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp | 2 +- TAO/tests/NestedUpcall/MT_Client_Test/client.cpp | 4 ++-- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/TAO/docs/orbsvcs.html b/TAO/docs/orbsvcs.html index b4d2f0c1aa8..94e7677c333 100644 --- a/TAO/docs/orbsvcs.html +++ b/TAO/docs/orbsvcs.html @@ -48,7 +48,7 @@ bgcolor="#ffffff"> the users control over collocation of the services implementation. As a first cut all the service implementations are included in the orbsvcs library $TAO_ROOT/orbsvcs/orbsvcs. - Since there are serveral services and each one is implemented + Since there are several services and each one is implemented using several files we have given a different directory to each service. This structure could also simplify a future split into several @@ -79,7 +79,7 @@ bgcolor="#ffffff"> Event Service orbsvcs/orbsvcs/CosEvent - Pradeep Gore + Pradeep Gore and OCI @@ -179,7 +179,7 @@ bgcolor="#ffffff"> executables if they want any changes in CORBA policies or would like to set their own bits when running a service. The executables that are packed with the TAO distribution should be - viewed as an executable with a basic subset of features. + viewed as an executable with a basic subset of features. The binaries in question are located in $TAO_ROOT/orbsvcs, and the list includes:

diff --git a/TAO/docs/pluggable_protocols/index.html b/TAO/docs/pluggable_protocols/index.html index 88817c7b5ab..3c277c19852 100644 --- a/TAO/docs/pluggable_protocols/index.html +++ b/TAO/docs/pluggable_protocols/index.html @@ -1054,7 +1054,7 @@ public: 
  // To support pluggable we need to abstract away the connect() 
-  // method so it can be called from the GIOP code independant of the  +  // method so it can be called from the GIOP code independent of the 
  // actual transport protocol in use. 
diff --git a/TAO/docs/releasenotes/ftrt_ec.html b/TAO/docs/releasenotes/ftrt_ec.html index c0c705b633e..45a7a59aa82 100644 --- a/TAO/docs/releasenotes/ftrt_ec.html +++ b/TAO/docs/releasenotes/ftrt_ec.html @@ -56,7 +56,7 @@ build it. See here for the i
 

Programs

-There are serveral programs in $TAO_ROOT/orbsvcs/FTRT_Event_Servce directory: +There are several programs in $TAO_ROOT/orbsvcs/FTRT_Event_Servce directory:

ftrt_eventservice : Located under $TAO_ROOT/orbsvcs/FTRT_Event_Servce/Event_Service directory. It implements the functionality of fault tolerant event channel. It can be started directly or  be started by the ftrtec_factory_service. diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html index a6afd718313..a529c8898a2 100644 --- a/TAO/docs/releasenotes/index.html +++ b/TAO/docs/releasenotes/index.html @@ -743,7 +743,7 @@ CORBA specification.

  • The generated sequence classes should not be generated per sequence, but per type and parent scope. Which means, that the overhead of having the -source code generated serveral times should be reduced. To do this, an +source code generated several times should be reduced. To do this, an extra pass over the internal representation of the IDL file has to be done.
  • diff --git a/TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp b/TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp index 26c57aa73fe..09cdf6e0b86 100644 --- a/TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp +++ b/TAO/orbsvcs/orbsvcs/Notify/EventChannelFactory.cpp @@ -107,7 +107,7 @@ TAO_Notify_EventChannelFactory::init (PortableServer::POA_ptr poa) this->adopt_poa (auto_object_poa.release ()); // Note topology factory is configured separately from the "builder" mediated - // objects since it is independant of the "style" of Notification Service. + // objects since it is independent of the "style" of Notification Service. this->topology_factory_ = ACE_Dynamic_Service ::instance ("Topology_Factory"); diff --git a/TAO/tests/NestedUpcall/MT_Client_Test/client.cpp b/TAO/tests/NestedUpcall/MT_Client_Test/client.cpp index abea802b15f..03e0d81e9ea 100644 --- a/TAO/tests/NestedUpcall/MT_Client_Test/client.cpp +++ b/TAO/tests/NestedUpcall/MT_Client_Test/client.cpp @@ -3,8 +3,8 @@ /** * @file client.cpp * - * Start one server thread calling a distant MT Object serveral times, - * also starting serveral client threads which call the MT Object too. + * Start one server thread calling a distant MT Object several times, + * also starting several client threads which call the MT Object too. * The server does nested upcalls. * * @author Michael Kircher -- cgit v1.2.1