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.7 -r1.8
--- openacs-4/packages/acs-service-contract/www/doc/index.html	18 May 2018 07:56:07 -0000	1.7
+++ openacs-4/packages/acs-service-contract/www/doc/index.html	3 Sep 2024 15:37:33 -0000	1.8
@@ -30,9 +30,9 @@
                   including both input and outputs as well as metadata
                   such as caching.</li>
 <li>implementation - an implementation is a set of concrete functions
-                  that fufills an interface.</li>
+                  that fulfillss an interface.</li>
 <li>implementation alias - is the method of an implementation that
-                  fufills a given operation of the contract.</li>
+                  fulfillss a given operation of the contract.</li>
 <li>bindings - association between an interface and an implementation.</li>
 <li>types - define the kind of input and outputs a operation receives.</li>
 </ul>
@@ -47,7 +47,7 @@
 <p>       with acs contracts.</p><p>    Implement the Contract</p><h2>  FAQ</h2>
 <h3>     Why Does an implementation reference an interface?</h3>
 <p>       This might seem a little strange since a binding is the official
-     reference between an implementation and an interface. However
+     reference between an implementation and an interface. However,
      it is quite possible that an implementation for interface might
      exist prior to the interface being defined, ie the interface
      defining package is not installed. By retaining this information
@@ -71,7 +71,7 @@
            container for operations. contract_desc is a text
            description of the contract.<ul>
 <li>(sql):<pre>                 acs_sc_operation__new (contract_name, operation_name,
-                                       operation_desc, operation_iscachable_p,
+                                       operation_desc, operation_iscacheable_p,
                                        operation_inputtype, operation_outputtype
                                       ):</pre>
 </li>