Index: openacs-4/packages/acs-service-contract/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.html,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/acs-service-contract/www/doc/index.html	7 Aug 2017 23:47:57 -0000	1.4
+++ openacs-4/packages/acs-service-contract/www/doc/index.html	31 Jan 2018 20:57:02 -0000	1.5
@@ -22,7 +22,7 @@
     calls on an interface implementation. The dispatch means
     is only available through tcl. </p><p>    Interface Discovery is available programmatically as well as via
     documentation through ad_proc.</p><p>    The Service Contract interface specification was inspired by
-    WDSL, the interface specfication for web services.</p><h2>  Hitchiker's Guide to Service Contract Definitions</h2>
+    WDSL, the interface specification for web services.</p><h2>  Hitchiker's Guide to Service Contract Definitions</h2>
 <ul>
 <li>contract - analogous to interface, contracts serve as logical 
                   containers for operations.</li>
@@ -57,7 +57,7 @@
 <ul>
 <li>(sql)::
                  acs_sc_msg_type__new (name, spec):<p>           defines a type based on spec. Spec should
-           be a string (possibly emtpy) that defines the
+           be a string (possibly empty) that defines the
            names and types that compose this type.
            example <code>ObjectDisplay.Name.InputType</code> as name
            <code>object_id:integer</code> as spec.</p></li>