Merge pull request #267 from jwillemsen/master

Documentation changes

2 files changed, 49 insertions, 60 deletions

diff --git a/ACE/README b/ACE/README
index 79125cf22de..f58f1a9100e 100644
--- a/ACE/README
+++ b/ACE/README
@@ -5,7 +5,7 @@ This document is also available at the following URL:
 http://www.dre.vanderbilt.edu/~schmidt/ACE.html
 
 All software and documentation is available via both anonymous ftp and
-the http.]
+http.
 
 THE ADAPTIVE COMMUNICATION ENVIRONMENT (ACE)
 
@@ -55,28 +55,28 @@ The lower-level portions of ACE provide a set of portable and
 type-secure C++ wrappers that encapsulate the following C language OS
 interfaces:
 
-        . IPC mechanisms
-                -- e.g., Internet- and UNIX-domain sockets, TLI, Named
-                   Pipes (for UNIX and Win32) and STREAM pipes;
+. IPC mechanisms
+  -- e.g., Internet- and UNIX-domain sockets, TLI, Named
+      Pipes (for UNIX and Win32) and STREAM pipes;
 
-        . Event demultiplexing
-                -- e.g., select(), poll(), and Win32
-                   WaitForMultipleObjects and I/O completion ports;
+. Event demultiplexing
+  -- e.g., select(), poll(), and Win32
+      WaitForMultipleObjects and I/O completion ports;
 
-        . Multi-threading and synchronization
-                -- e.g., Solaris threads, POSIX Pthreads, and Win32
-                   threads;
+. Multi-threading and synchronization
+  -- e.g., Solaris threads, POSIX Pthreads, and Win32
+      threads;
 
-        . Explicit dynamic linking
-                -- e.g., dlopen/dlsym on UNIX and LoadLibrary/GetProc
-                   on Win32;
+. Explicit dynamic linking
+  -- e.g., dlopen/dlsym on UNIX and LoadLibrary/GetProc
+      on Win32;
 
-        . Memory-mapped files and shared memory management
-                -- e.g., BSD mmap(), SYSV shared memory, and Win32
-                   shared memory;
+. Memory-mapped files and shared memory management
+  -- e.g., BSD mmap(), SYSV shared memory, and Win32
+      shared memory;
 
-        . System V IPC
-                -- e.g., shared memory, semaphores, message queues.
+. System V IPC
+  -- e.g., shared memory, semaphores, message queues.
 
 The OS Adaptation Layer shields the upper levels of ACE from platform
 dependencies associated with the underlying OS interfaces.
@@ -91,25 +91,25 @@ supports the dynamic configuration of concurrent distributed services
 into applications.  The framework portion of ACE contains the
 following class categories:
 
-        . The Reactor
-                -- Supports both Reactive and Proactive I/O;
+. The Reactor
+  -- Supports both Reactive and Proactive I/O;
 
-        . The Service Configurator
-                -- Support dynamic (re)configuration of objects;
+. The Service Configurator
+  -- Support dynamic (re)configuration of objects;
 
-        . The ADAPTIVE Service Executive
-                -- A user-level implementation of System V STREAMS,
-                   that supports modular integration of
-                   hierarchically-related communication services;
+. The ADAPTIVE Service Executive
+  -- A user-level implementation of System V STREAMS,
+      that supports modular integration of
+      hierarchically-related communication services;
 
-        . Concurrency
-                -- Various types of higher-level concurrency
-                   control and synchronization patterns (such as
-                   Polymorphic Futures and Active Objects);
+. Concurrency
+  -- Various types of higher-level concurrency
+      control and synchronization patterns (such as
+      Polymorphic Futures and Active Objects);
 
-        . Shared Malloc
-                -- Components for managing dynamically allocation
-                   of shared and local memory;
+. Shared Malloc
+  -- Components for managing dynamically allocation
+      of shared and local memory;
 
 ----------------------------------------
 
@@ -119,13 +119,13 @@ Finally, ACE provides a standard library of distributed services that
 are packaged as components.  These service components play two roles
 in ACE:
 
-        1. They provide reusable components for common distributed
-           system tasks such as logging, naming, locking, and time
-           synchronization.
+1. They provide reusable components for common distributed
+    system tasks such as logging, naming, locking, and time
+    synchronization.
 
-        2. They illustrate how to utilize ACE features such as the
-           Reactor, Service Configurator, Service Initialization,
-           Concurrency, and IPC components.
+2. They illustrate how to utilize ACE features such as the
+    Reactor, Service Configurator, Service Initialization,
+    Concurrency, and IPC components.
 
 ----------------------------------------
 
@@ -138,12 +138,12 @@ Ericsson, Motorola, and Lucent; medical imaging systems at Siemens and
 Kodak; and many academic research projects.  Two example middleware
 applications provided with the ACE release include:
 
-        1. The ACE ORB (TAO) -- TAO is a real-time implementation of
-           CORBA built using the framework components and patterns
-           provided by ACE.
+1. The ACE ORB (TAO) -- TAO is a real-time implementation of
+    CORBA built using the framework components and patterns
+    provided by ACE.
 
-        2. JAWS -- JAWS is a high-performance, adaptive Web server
-           built using the components in ACE.
+2. JAWS -- JAWS is a high-performance, adaptive Web server
+    built using the components in ACE.
 
 ----------------------------------------
 
@@ -195,8 +195,7 @@ how to subscribe to the mailing list.
 
 BUILDING AND INSTALLING ACE
 
-Please refer to the
-http://www.dre.vanderbilt.edu/~schmidt/ACE-install.html file for
+Please refer to the $ACE_ROOT/ACE-INSTALL.html file for
 information on how to build and test the ACE wrappers.  The
 BIBLIOGRAPHY file contains information on where to obtain articles
 that describe the ACE wrappers and the ADAPTIVE system in more detail.
@@ -208,11 +207,11 @@ $ACE_ROOT/PROBLEM-REPORT-FORM.  Please use the same form to submit
 questions, comments, etc.  To ensure that you see responses, please do
 one of the following:
 
-    1) Subscribe to the ace-users mail list, by sending email with
-       contents "subscribe ace-users" to
-       ace-users-request@list.isis.vanderbilt.edu.
+1) Subscribe to the ace-users mail list, by sending email with
+    contents "subscribe ace-users" to
+    ace-users-request@list.isis.vanderbilt.edu.
 
-    2) Or, monitor the comp.soft-sys.ace newsgroup for responses.
+2) Or, monitor the comp.soft-sys.ace newsgroup for responses.
 
 ----------------------------------------
 
diff --git a/TAO/orbsvcs/orbsvcs/CosLifeCycle.idl b/TAO/orbsvcs/orbsvcs/CosLifeCycle.idl
index 6a1610c36f7..02533edecae 100644
--- a/TAO/orbsvcs/orbsvcs/CosLifeCycle.idl
+++ b/TAO/orbsvcs/orbsvcs/CosLifeCycle.idl
@@ -80,11 +80,6 @@ module CosLifeCycle
 
   interface LifeCycleObject
     {
-      // = TITLE
-      //   @@ Please fill in.
-      // = DESCRIPTION
-      //   @@ Please fill in.
-
       LifeCycleObject copy (in FactoryFinder there,
                             in Criteria the_criteria)
         raises (NoFactory, NotCopyable, InvalidCriteria, CannotMeetCriteria);
@@ -97,11 +92,6 @@ module CosLifeCycle
 
   interface GenericFactory
     {
-      // = TITLE
-      //   @@ Please fill in.
-      // = DESCRIPTION
-      //   @@ Please fill in.
-
       boolean _supports (in Key k);
       Object create_object (in Key k,
                             in Criteria the_criteria)