Fixed fuzz

10 files changed, 35 insertions, 37 deletions

diff --git a/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_Basic/README b/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_Basic/README
index 42db0c2a7c1..b454e74edd4 100644
--- a/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_Basic/README
+++ b/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_Basic/README
@@ -28,7 +28,7 @@ EchoEventSupplerMain.cpp
   Main program for a PushSupplier.
 
     EchoEventSupplier -ORBInitRef NameService=file://ns.ior
-  
+
   It will publish an event to the event channel every second.
   Use Control-C to kill the process.
 
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/Messenger/README b/TAO/orbsvcs/DevGuideExamples/NamingService/Messenger/README
index 68eec11fbc1..52288003990 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/Messenger/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/Messenger/README
@@ -5,9 +5,9 @@ OMG Naming Service
 File: DevGuideExamples/NamingService/Messenger/README
 
 
-The Original Messenger example, introduced in Chapters 4 and 5 
-(GettingStartedUNIX and GettingStartedVC), is modified to utilize the 
-Naming Service.  The client now uses the Naming Service rather than 
+The Original Messenger example, introduced in Chapters 4 and 5
+(GettingStartedUNIX and GettingStartedVC), is modified to utilize the
+Naming Service.  The client now uses the Naming Service rather than
 reading the server object's IOR as a string from a file.
 
 The Client code is stored in:
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Client/README b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Client/README
index d3b94d1a528..e03c0224638 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Client/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Client/README
@@ -6,8 +6,8 @@ File: DevGuideExamples/NamingService/Naming_Client/README
 
 
 The example in this directory is a modification of the code given
-in the NamingService/Messenger example.  It illustrates how to use the 
-TAO_Naming_Client class for accessing the Naming Service.  This class 
+in the NamingService/Messenger example.  It illustrates how to use the
+TAO_Naming_Client class for accessing the Naming Service.  This class
 simplifies the interface for accessing and using the Naming Service.
 The TAO_Naming_Client class is used by both the Client and
 Server to access the Naming Service.
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Context_Ext/README b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Context_Ext/README
index e2466608fcf..eb64ef78a82 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Context_Ext/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Context_Ext/README
@@ -2,14 +2,14 @@
 
 DevGuideExamples/NamingService/Naming_Context_Ext/README
 
-The example in this directory illustratues how to convert between CosNames, 
-Stringified Names, and URLs. 
+The example in this directory illustratues how to convert between CosNames,
+Stringified Names, and URLs.
 
-A Name can be converted to a stringified Name by to_string operation. A stringified 
-Name can be converted to a Name by to_name operation. The resolve_str operation 
-resolves an object by passing a strigified Name. 
+A Name can be converted to a stringified Name by to_string operation. A stringified
+Name can be converted to a Name by to_name operation. The resolve_str operation
+resolves an object by passing a strigified Name.
 
-The MessengerServer writes its corbaname URL to a file by calling to_url and 
+The MessengerServer writes its corbaname URL to a file by calling to_url and
 the MessengerClient reads the URL file to get the MessengerServer object reference.
 
 
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Server/README b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Server/README
index b98ba3a2ee3..e7f9abe3d5e 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Server/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/Naming_Server/README
@@ -4,11 +4,11 @@ OMG Naming Service
 
 File: DevGuideExamples/NamingService/Naming_Server/README
 
-The example in NamingService/Naming_Client is modified to utilize 
-the TAO_Naming_Server class.  This class enables the Naming Service 
-to easily be collocated within an application.  In this example, 
-the Naming Service is collocated with a server that supports the 
-Messenger Interface described in GettingStartedUNIX (or GettingStartedVC). 
+The example in NamingService/Naming_Client is modified to utilize
+the TAO_Naming_Server class.  This class enables the Naming Service
+to easily be collocated within an application.  In this example,
+the Naming Service is collocated with a server that supports the
+Messenger Interface described in GettingStartedUNIX (or GettingStartedVC).
 
 The Server code is stored in:
 
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/corbaname_Messenger/README b/TAO/orbsvcs/DevGuideExamples/NamingService/corbaname_Messenger/README
index 4486d3b9da4..aa9482f1f21 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/corbaname_Messenger/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/corbaname_Messenger/README
@@ -2,14 +2,14 @@
 
 DevGuideExamples/NamingService/corbaname_Messenger/README
 
-The example in this directory extends the example in GettingStartedUNIX 
+The example in this directory extends the example in GettingStartedUNIX
 (or GettingStartedVC) to use the Naming_Service
-and calling string_to_object instead of calling resolve_initial_references 
+and calling string_to_object instead of calling resolve_initial_references
 to get the NameService object reference and look up the service in the Naming_Service.
 
 This example only differs from the NamingService/Messenger example by a few lines
 in the MessengerClient.cpp.  (All other source files should be the same.)
- 
+
 How to Run:
 -----------
 To start the Naming_Service:
@@ -25,7 +25,7 @@ To start the client:
 ./MessengerClient
 
 
-This MessengerClient will optionally take parameter that is a URL (corbaname:) 
+This MessengerClient will optionally take parameter that is a URL (corbaname:)
 that addresses the Naming_Service and the MessengerServer within it.
 
 The MessengerServer and MessengerClient may also take an -ORBInitRef option
@@ -50,7 +50,7 @@ REM start the client
 cd/d %EXAMPLES%\NamingService\corbaname_Messenger\Debug
 title client
 
-REM use a corbaname that does not require -ORBDefaultInitRef 
+REM use a corbaname that does not require -ORBDefaultInitRef
 MessengerClient corbaname:iiop:localhost:2809#example/Messenger
 
 REM defaults to iiop protocol
@@ -61,5 +61,5 @@ MessengerClient corbaname::localhost#example/Messenger
 
 
 
-REM use RIR 
+REM use RIR
 MessengerClient -ORBInitRef NameService=iiop://localhost:2809/NameService corbaname:rir:#example/Messenger
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/Filtering/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/Filtering/README
index c91cd77888d..051f920e2bf 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/Filtering/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/Filtering/README
@@ -2,18 +2,16 @@
 
 Event Notification Service
 
-
 File: DevGuideExamples/NotifyService/Filtering/README
 
-
 This example extends the NotifyService/Messenger example by
-demonstrating how filtering can be incorporated into the utilization 
+demonstrating how filtering can be incorporated into the utilization
 of the Notification channel.  Supplier-side, and consumer-side
-filtering can be implemented, but only consumer_side filtering is 
+filtering can be implemented, but only consumer_side filtering is
 demonstrated in this example.
 
-Filters are configured to guarantee that only certain events are 
-passed to the consumer. The criteria is specified by imposing constraints 
+Filters are configured to guarantee that only certain events are
+passed to the consumer. The criteria is specified by imposing constraints
 on the appropriate fields of a structured event.
 
 
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/QoSProperties/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/QoSProperties/README
index d35c3106746..c09d124e31c 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/QoSProperties/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/QoSProperties/README
@@ -7,7 +7,7 @@ File: DevGuideExamples/NotifyService/QoSProperties/README
 
 
 This example extends the NotifyService/Messenger example by
-demonstrating how QoS features can be incorporated into the utilization 
+demonstrating how QoS features can be incorporated into the utilization
 of the Notification channel.
 
 The Client code is stored in:
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/RTNotify/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/RTNotify/README
index b2308f5b781..d55f471a84c 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/RTNotify/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/RTNotify/README
@@ -8,7 +8,7 @@ File: examples/NotifyService/RTNotify/README
 This directory contains a simple example of using the Notification Service
 with Real-Time CORBA.
 
-This example extends the basic Messenger notify service example to illustrate 
+This example extends the basic Messenger notify service example to illustrate
 how the Notification channel can be used with RT CORBA features.  The supplier
 and consumer both set up their proxies to use a thread pool with lanes and
 the Notify_Service executable is configured to load the RT_Notification library
@@ -16,7 +16,7 @@ and associated features.  A priority is set in the supplier and propagetd throug
 the channel into the consumer.
 
 The MessengerServer in this example plays the role of a server for
-the MessengerClient and the role of a supplier for the MessengerConsumer. 
+the MessengerClient and the role of a supplier for the MessengerConsumer.
 The flow of messages is shown below:
 
 MessengerClient->MessengerSupplier->NotificationChannel->MessengerConsumer.
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/SupplierSideNC/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/SupplierSideNC/README
index 74ca8f88ca8..e11834fb236 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/SupplierSideNC/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/SupplierSideNC/README
@@ -4,19 +4,19 @@ examples/NotifyService/SupplierSideNC/README
 
 This directory contains a simple example of using the Notification Service.
 
-This example extends the Messenger example in Filtering directory 
+This example extends the Messenger example in Filtering directory
 to illustrate how the Notification channel can be used to push messages
 from the supplier to the consumer. Furthermore, this example shows
-how you could set up filters so that only a certain events are 
+how you could set up filters so that only a certain events are
 passed to the consumer.
- 
+
 This example uses the push/push model.
 
-In this example, the Notify Service initiation is incorporated into the 
+In this example, the Notify Service initiation is incorporated into the
 MessengerServer.
 
 The MessengerSupplier in this example plays the role of a server for
-the MessengerClient and the role of a supplier for the MessengerConsumer. 
+the MessengerClient and the role of a supplier for the MessengerConsumer.
 The flow of messages is shown below:
 
 MessengerClient->(MessengerSupplier->NotificationChannel)->MessengerConsumer.