Fixed fuzz

8 files changed, 19 insertions, 20 deletions

diff --git a/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_SupplierSideEC/README b/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_SupplierSideEC/README
index a4db5d42ba2..ed60620ea05 100644
--- a/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_SupplierSideEC/README
+++ b/TAO/orbsvcs/DevGuideExamples/EventServices/OMG_SupplierSideEC/README
@@ -29,8 +29,8 @@ EchoEventSupplerMain.cpp
   Main program for a PushSupplier.
 
     EchoEventSupplier -ORBInitRef NameService=file://ns.ior
-  
-  It will create an event channel and publish an event to it every 
+
+  It will create an event channel and publish an event to it every
   second.
   Use Control-C to kill the process.
 
diff --git a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Basic/README b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Basic/README
index e2c3aae04e1..02def9ed8d6 100644
--- a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Basic/README
+++ b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Basic/README
@@ -26,7 +26,7 @@ EchoEventSupplerMain.cpp
   Main program for a PushSupplier.
 
     EchoEventSupplier -ORBInitRef NameService=file://ns.ior
-  
+
   It will publish an event to the event channel every 1 second.
   Use Control-C to kill the process.
 
diff --git a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Federated/README b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Federated/README
index f905a2717da..078899e15c0 100644
--- a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Federated/README
+++ b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Federated/README
@@ -44,7 +44,7 @@ EchoEventSupplerMain.cpp
   it locates the remote event channel, initialize the gateway,
   and then publish an event to the local event channel every 10
   milliseconds.  This event will contain the string <name> in the
-  any_value field. When the gateway is initialized, you'll see a 
+  any_value field. When the gateway is initialized, you'll see a
   message stating "Gateway initialized".  If you pass the -iorfile
   parameter, this server also writes the EC's IOR to <file> when
   the gateway is initialized.
diff --git a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Filter/README b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Filter/README
index 74f2f79cd5a..1c7f1437143 100644
--- a/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Filter/README
+++ b/TAO/orbsvcs/DevGuideExamples/EventServices/RTEC_Filter/README
@@ -26,7 +26,7 @@ EchoEventSupplerMain.cpp
   Main program for a PushSupplier.
 
     EchoEventSupplier -ORBInitRef NameService=file://ns.ior
-  
+
   It will publish an event to the event channel every 1 second.
   Use Control-C to kill the process.
 
diff --git a/TAO/orbsvcs/DevGuideExamples/ImplRepo/README b/TAO/orbsvcs/DevGuideExamples/ImplRepo/README
index 99a264e11a9..d52509ea832 100644
--- a/TAO/orbsvcs/DevGuideExamples/ImplRepo/README
+++ b/TAO/orbsvcs/DevGuideExamples/ImplRepo/README
@@ -11,7 +11,7 @@ How to Run
 
 Start the Implementation Repository (ImplRepo) server:
 ------------------------------------------------------
-$TAO_ROOT/orbsvcs/ImplRepo_Service/ImplRepo_Service -o implrepo.ior 
+$TAO_ROOT/orbsvcs/ImplRepo_Service/ImplRepo_Service -o implrepo.ior
 
 Register the server's POA name and start-up command with the ImplRepo:
 ----------------------------------------------------------------------
@@ -26,4 +26,4 @@ $TAO_ROOT/orbsvcs/ImplRepo_Service/tao_imr -ORBInitRef \
 
 Run the client (ImplRepo should automatically start the server):
 ----------------------------------------------------------------
-./MessengerClient 
+./MessengerClient
diff --git a/TAO/orbsvcs/DevGuideExamples/NamingService/corbaloc_Messenger/README b/TAO/orbsvcs/DevGuideExamples/NamingService/corbaloc_Messenger/README
index 414445658a0..32a56f491b4 100644
--- a/TAO/orbsvcs/DevGuideExamples/NamingService/corbaloc_Messenger/README
+++ b/TAO/orbsvcs/DevGuideExamples/NamingService/corbaloc_Messenger/README
@@ -1,13 +1,12 @@
 // $Id$
 
 DevGuideExamples/NamingService/corbaloc_Messenger/README
-// $Id$
 
-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 
+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
 to get the NameService object reference.
- 
+
 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.)
 
@@ -17,18 +16,18 @@ To start the Naming_Service:
 ----------------------------
 $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service -m 1 &
 
-Note: Must start the Naming_Service using multicast (-m 1) 
+Note: Must start the Naming_Service using multicast (-m 1)
       for the default initial reference for NameService to work.
 
 To start the server:
 ------------------
-./MessengerServer 
+./MessengerServer
 To start the client:
 ------------------
 ./MessengerClient
 
 
-This MessengerClient will optionally take parameter that is a URL (corbaloc:) 
+This MessengerClient will optionally take parameter that is a URL (corbaloc:)
 that addresses the Naming_Service.
 
 The MessengerServer and MessengerClient may also take an -ORBInitRef option
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
index 4a60c213d06..7869702238c 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
@@ -7,12 +7,12 @@ File: examples/NotifyService/EventSequence/README
 
 This directory contains an example which transmits an EventBatch using the Notification Service.
 
-This example extends the Messenger example in GettingStarted directory 
-to illustrate how the Notification channel can be used to push event batches 
+This example extends the Messenger example in GettingStarted directory
+to illustrate how the Notification channel can be used to push event batches
 from the supplier to the consumer. The example uses the push/push model.
 
 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/Messenger/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
index 29688714703..609933cb8d5 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
@@ -7,13 +7,13 @@ File: examples/NotifyService/Messenger/README
 
 This directory contains a simple example of using the Notification Service.
 
-This example extends the Messenger example in GettingStarted directory 
+This example extends the Messenger example in GettingStarted directory
 to illustrate how the Notification channel can be used to push messages
 from the supplier to the consumer.  Structured events are used to demonstrate
 the operation of the channel.  The example uses the push/push model.
 
 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.