summaryrefslogtreecommitdiff
path: root/TAO/docs/orbsvcs.html
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/docs/orbsvcs.html')
-rw-r--r--TAO/docs/orbsvcs.html6
1 files changed, 3 insertions, 3 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 <CODE>$TAO_ROOT/orbsvcs/orbsvcs</CODE>.
- 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">
<TR>
<TD>Event Service</TD>
<TD><CODE>orbsvcs/orbsvcs/CosEvent</CODE></TD>
- <TD>Pradeep Gore <pradeep at oomworks dot com>
+ <TD>Pradeep Gore <pradeep at oomworks dot com>
and OCI<taosupport at ociweb dot com> </TD>
</TR>
<TR>
@@ -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
<CODE>$TAO_ROOT/orbsvcs</CODE>, and the list includes:
</P>