Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.html,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	10 Aug 2019 15:15:49 -0000	1.3.2.1
+++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	1 Aug 2024 07:38:16 -0000	1.3.2.2
@@ -48,7 +48,7 @@
   <li>Account Registration (where to create new accounts) </li>
   <li>On-Demand Sync (to get user info from the source in real time) </li>
 </ul>
-<p>Those configurations simply will perform the tcl proc that is defined in the SC above described for the given SC implementation that you choose. In other words:</p>
+<p>Those configurations simply will perform the Tcl proc that is defined in the SC above described for the given SC implementation that you choose. In other words:</p>
 <ul>
   <li>For using LDAP, you need to install <a href="http://cvs.openacs.org/cvs/openacs-4/packages/auth-ldap/">auth-ldap</a>, on its installation, this package will create an <a href="http://cvs.openacs.org/cvs/*checkout*/openacs-4/packages/auth-ldap/tcl/auth-ldap-procs.tcl?rev=1.8">implementation</a> of the above mentioned SC definitions (look at &quot;specs&quot; that define which proc needs to be called for each alias).</li>
   <li>PAM package is <a href="http://cvs.openacs.org/cvs/openacs-4/packages/auth-pam/">auth-pam</a>. </li>
@@ -67,7 +67,7 @@
 </ul>
 <p>Then you can enter your specific values for your server, is likely that the recomemded ones will work fine. </p>
 <p>Hint: nssha (SSHA) doesn't work well with LDAP use ns_passwd or another encryption method (MD5...)</p>
-<p>You can make your users to logging using the email or username, by changing the parameter at the kernel named: UseEmailForLoginP under Security section. If username is used for logging, it will ask  for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identic usernames but each one belongs to a different authority). </p>
+<p>You can make your users to logging using the email or username, by changing the parameter at the kernel named: UseEmailForLoginP under Security section. If username is used for logging, it will ask  for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identical usernames but each one belongs to a different authority). </p>
 <p class="style2">&nbsp;</p>
 <p class="style2"><strong>acs-authentication defines a set of SC to interact with the different authentication implementations (LDAP or PAM):</strong></p>
 <ol>
@@ -111,7 +111,7 @@
 <ol>
   <li>The user enters the email/user &amp; password</li>
   <li> It will search the user in the users table and return the authority_id </li>
-  <li>With that authority_id it will find the respective SC implementation <em>which contains the adequate tcl proc for the authentication process</em></li>
+  <li>With that authority_id it will find the respective SC implementation <em>which contains the adequate Tcl proc for the authentication process</em></li>
   <li>That proc will check the identity of the user based on the password (right now could be locally, pam or ldap authenticated, though this model supports N methods of authentication)</li>
 </ol>
 <div class="navfooter">
Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html,v
diff -u -r1.6.2.2 -r1.6.2.3
--- openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html	3 Jul 2020 07:53:44 -0000	1.6.2.2
+++ openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html	1 Aug 2024 07:38:16 -0000	1.6.2.3
@@ -64,5 +64,5 @@
         The OpenACS server itself is the "Local Authority," used by
         default.</p><div class="orderedlist"><ol type="a"><li><p>Browse to the authentication administration page,
             <code class="computeroutput">http://<span class="replaceable"><span class="replaceable">yourserver</span></span><a href="/acs-admin/auth/" target="_top">/acs-admin/auth/</a></code>.
-             Create and name an authority (in the sitewide admin UI)</p></li><li><p>Set Authentication to PAM.</p></li><li><p>If the PAM domain defines a <code class="computeroutput">password</code> command, you can set Password Management to PAM.  If not, the PAM module cannot change the user's password and you should leave this option Disabled.</p></li><li><p>Leave Account Registration disabed.</p></li><li><p><a href="configure-batch-sync.html" title="Configure Batch Synchronization">Configure Batch Synchronization</a>
+             Create and name an authority (in the sitewide admin UI)</p></li><li><p>Set Authentication to PAM.</p></li><li><p>If the PAM domain defines a <code class="computeroutput">password</code> command, you can set Password Management to PAM.  If not, the PAM module cannot change the user's password and you should leave this option Disabled.</p></li><li><p>Leave Account Registration disabled.</p></li><li><p><a href="configure-batch-sync.html" title="Configure Batch Synchronization">Configure Batch Synchronization</a>
 </p></li></ol></div></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ext-auth-install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="ext-auth-ldap-install.html">Next</a></td></tr><tr><td width="40%" align="left">Installation </td><td width="20%" align="center"><a accesskey="u" href="ext-auth-install.html">Up</a></td><td width="40%" align="right"> Using LDAP/Active Directory with OpenACS</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a><center><a href="http://openacs.org/doc/current/ext-auth-pam-install.html#comments">View comments on this page at openacs.org</a></center></body></html>
Index: openacs-4/packages/acs-messaging/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.html,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/acs-messaging/www/doc/requirements.html	15 Aug 2019 10:20:04 -0000	1.3.2.1
+++ openacs-4/packages/acs-messaging/www/doc/requirements.html	1 Aug 2024 07:38:16 -0000	1.3.2.2
@@ -58,7 +58,7 @@
     
     <p>
     The ACS Messaging package defines a data model and API for the
-    storage and retrieval of messages. While the package standarizes how
+    storage and retrieval of messages. While the package standardizes how
     messages are stored, applications may use any data model they want
     for higher level organization of messages into threads, forums,
     and so on. ACS Messaging places no organizational constraints on
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.7.2.1
--- 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	1 Aug 2024 07:38:16 -0000	1.7.2.1
@@ -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>
Index: openacs-4/packages/acs-templating/www/doc/timing-3.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/timing-3.html,v
diff -u -r1.3 -r1.3.2.1
--- openacs-4/packages/acs-templating/www/doc/timing-3.html	7 Aug 2017 23:48:02 -0000	1.3
+++ openacs-4/packages/acs-templating/www/doc/timing-3.html	1 Aug 2024 07:38:16 -0000	1.3.2.1
@@ -20,7 +20,7 @@
       suppressed them.  The log message that marks
       the beginning of each phase is written in the lower right of the
       graphs.  Each curve curve plots 288 page requests.  As I didn't
-      back port of the configurable cache refreshing stragegy ('never' or
+      back port of the configurable cache refreshing strategy ('never' or
       'always'), I show all graphs in the 'normal' colors.  The label
       is 'do', though.
     </p>
Index: openacs-4/packages/ajaxhelper/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/ajaxhelper/www/doc/index.html,v
diff -u -r1.9 -r1.9.2.1
--- openacs-4/packages/ajaxhelper/www/doc/index.html	7 Aug 2017 23:48:03 -0000	1.9
+++ openacs-4/packages/ajaxhelper/www/doc/index.html	1 Aug 2024 07:38:16 -0000	1.9.2.1
@@ -93,7 +93,7 @@
 <br>
     <span style="font-weight: bold;">Ajax Procedures :<br>
     <br>
-Prototype</span> has a pair of javascript functions that alllow
+Prototype</span> has a pair of javascript functions that allow
 programmers to use XMLHTTP. The ajax.updater and ajax.request
 functions. See <a
  href="http://api.prototypejs.org/ajax/Ajax/Updater/">http://api.prototypejs.org/ajax/Ajax/Updater/</a>
Index: openacs-4/packages/assessment/www/doc/as_items.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_items.html,v
diff -u -r1.16.2.2 -r1.16.2.3
--- openacs-4/packages/assessment/www/doc/as_items.html	5 Oct 2019 13:43:47 -0000	1.16.2.2
+++ openacs-4/packages/assessment/www/doc/as_items.html	1 Aug 2024 07:38:16 -0000	1.16.2.3
@@ -131,7 +131,7 @@
     <ul>
       <li>Read: An assessment author (who is granted this permission)
 can
-reuse this as_item in one of his sections. (NB: Usually the original
+reuse this as_item in one of his sections. (NB: Usually, the original
 author has admin privileges.). This is a finer granulation than the
 previous "enabled_p" as it allows specific access to an item. </li>
       <li>Write: Author can reuse and change this as_item. </li>
@@ -489,7 +489,7 @@
         </ol>
       </li>
       <li>choice_label_orientation - how shall the label be positioned
-in relation to the choice (top, left, right, buttom).<br>
+in relation to the choice (top, left, right, bottom).<br>
       </li>
       <li>sort_order_type: Numerical, alphabetic, randomized or
 by order of entry (sort_order field).</li>
Index: openacs-4/packages/assessment/www/doc/as_types.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_types.html,v
diff -u -r1.1 -r1.1.16.1
--- openacs-4/packages/assessment/www/doc/as_types.html	8 Dec 2004 15:30:35 -0000	1.1
+++ openacs-4/packages/assessment/www/doc/as_types.html	1 Aug 2024 07:38:16 -0000	1.1.16.1
@@ -14,7 +14,7 @@
 <li>add new table to assessment-item-types-create.sql</li>
 <li>add entry to matrix table item_type -> display_type in assessment-types-create.sql</li>
 <li>add content type data to tcl/as-install-procs.tcl. adhere to the naming standards!!</li>
-<li>add tcl procs to tcl/as-item-type-$$-procs or tcl/as-item-display-$$-procs with ::new, ::edit, ::copy procs. adhere to naming standards!!</li>
+<li>add Tcl procs to tcl/as-item-type-$$-procs or tcl/as-item-display-$$-procs with ::new, ::edit, ::copy procs. adhere to naming standards!!</li>
 <li>add admin pages to add new instance: www/admin/item-add-$$ or www/admin/item-add-display-$$</li>
 <li>add admin pages to edit new instance: www/admin/item-edit-$$ or www/admin/item-edit-display-$$</li>
 <li>add pages to display data: lib/item-show-$$ or lib/item-show-display-$$</li>
Index: openacs-4/packages/assessment/www/doc/data-model.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/data-model.html,v
diff -u -r1.1.2.2 -r1.1.2.3
--- openacs-4/packages/assessment/www/doc/data-model.html	5 Oct 2019 13:43:47 -0000	1.1.2.2
+++ openacs-4/packages/assessment/www/doc/data-model.html	1 Aug 2024 07:38:16 -0000	1.1.2.3
@@ -30,7 +30,7 @@
 applicability intended for this package.
 </p>
 <p>As is the custom in the OpenACS framework, all RDBMS tables in
-the package will be prepended with "as_" to prevent further prefent
+the package will be prepended with "as_" to prevent further prevent
 naming clashes. Judicious use of namespaces will also be made in
 keeping with current OpenACS best practice.
 </p>
Index: openacs-4/packages/assessment/www/doc/data_collection.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/data_collection.html,v
diff -u -r1.9.2.2 -r1.9.2.3
--- openacs-4/packages/assessment/www/doc/data_collection.html	17 Aug 2019 09:29:28 -0000	1.9.2.2
+++ openacs-4/packages/assessment/www/doc/data_collection.html	1 Aug 2024 07:38:16 -0000	1.9.2.3
@@ -71,7 +71,7 @@
         package, which is based on the CR and thus can support multiple comments attached to a given
         revision of a data element. The integration between Assessment and GC thus will need to
         be at the UI level, not the data model level. Using GC will support post-test "discussions" between
-        student and teacher, for example, about inidividual items, sections or sessions.</li><p></p>
+        student and teacher, for example, about individual items, sections or sessions.</li><p></p>
     <li> <strong>Scoring-grading</strong>: This has been a rather controversial area because of the
       wide range of needs for derived calculations/evaluations that different applications need
       to perform on the raw submitted data. In many cases, no calculations are needed at all; only
Index: openacs-4/packages/assessment/www/doc/display_types.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.html,v
diff -u -r1.9.2.3 -r1.9.2.4
--- openacs-4/packages/assessment/www/doc/display_types.html	7 Feb 2023 13:15:06 -0000	1.9.2.3
+++ openacs-4/packages/assessment/www/doc/display_types.html	1 Aug 2024 07:38:16 -0000	1.9.2.4
@@ -176,9 +176,9 @@
   <li>Name: text. Name of the section like "test view sorted"</li>
   <li>Number of questions per page: integer. THIS HAS TO BE CHANGED IN
 THE DATA MODEL FROM PAGINATION_STYLE. How many questions shall be
-displayed per page in this section. Usually the answer would be "" for
+displayed per page in this section. Usually, the answer would be "" for
 all questions on one page (default), or "1" for one question per page
-(a.k.a. one question at a time), but any number is imagineable.</li>
+(aka one question at a time), but any number is imagineable.</li>
   <li><span class="context"><span class="reg">ADP style: ADP to choose
 from that will control the makeup of the section along with the option
 to create a new one and a link to edit existing ones that </span></span><span
@@ -199,7 +199,7 @@
 separately, even if we display multiple answers? If yes, display a
 "save" button next to each answer along with green "V" if the answer
 has been already submitted. To finish the section, you still have to
-click on the OK button at the buttom. Once the section is finished all
+click on the OK button at the bottom. Once the section is finished all
 answers that have not been separately submitted will be treated as not
 being submitted at all.<br>
   </li>
Index: openacs-4/packages/assessment/www/doc/grouping.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/grouping.html,v
diff -u -r1.7.2.1 -r1.7.2.2
--- openacs-4/packages/assessment/www/doc/grouping.html	17 Aug 2019 09:29:28 -0000	1.7.2.1
+++ openacs-4/packages/assessment/www/doc/grouping.html	1 Aug 2024 07:38:16 -0000	1.7.2.2
@@ -157,7 +157,7 @@
   <ul>
     <li>Read: An assessment author (who is granted this permission)
 can
-reuse this assessment (NB: Usually the original author has admin
+reuse this assessment (NB: Usually, the original author has admin
 privileges.) </li>
     <li>Write: Author can reuse and change this assessment. </li>
     <li>Admin: Author can reuse, change and give permission on this
@@ -204,7 +204,7 @@
     <ul>
       <li>Read: A section author (who is granted this permission) can
 reuse
-this section (NB: Usually the original author has admin privileges.) </li>
+this section (NB: Usually, the original author has admin privileges.) </li>
       <li>Write: Author can reuse and change this section. </li>
       <li>Admin: Author can reuse, change and give permission on this
 section </li>
Index: openacs-4/packages/assessment/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/index.html,v
diff -u -r1.9.2.1 -r1.9.2.2
--- openacs-4/packages/assessment/www/doc/index.html	17 Aug 2019 09:29:28 -0000	1.9.2.1
+++ openacs-4/packages/assessment/www/doc/index.html	1 Aug 2024 07:38:16 -0000	1.9.2.2
@@ -10,7 +10,7 @@
 <p>The Assessment Package unites the work and needs of various members
 of the OpenACS community for data collection functionality within the
 OpenACS framework. We're using the term "Assessment" instead of
-"Survey" or "Questionnaire" (or "Case Report Form" a.k.a. CRF, the term
+"Survey" or "Questionnaire" (or "Case Report Form" aka CRF, the term
 used in clinical trials) because it is a term used by IMS and because
 it connotes the more generic nature of the data collection system we're
 focusing on. </p>
@@ -196,7 +196,7 @@
 editing, and deleting the Sections themselves. Includes the page to
 browse for items to include in sections</li>
   <li><a href="user_interface/item_creation.html">Item Authoring and
-Catalogue</a>: all the pages involing the item creation and the item
+Catalogue</a>: all the pages involving the item creation and the item
 catalogue.</li>
   <li><a href="user_interface/user_experience.html"> Assessment Delivery</a>:
 all the pages involved in
Index: openacs-4/packages/assessment/www/doc/item_types.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/item_types.html,v
diff -u -r1.6.2.2 -r1.6.2.3
--- openacs-4/packages/assessment/www/doc/item_types.html	5 Oct 2019 13:43:47 -0000	1.6.2.2
+++ openacs-4/packages/assessment/www/doc/item_types.html	1 Aug 2024 07:38:16 -0000	1.6.2.3
@@ -274,7 +274,7 @@
   </li>
   <li>Composite multiple choice with Fill-in-Blank item:
     <p>Multiple Choice question with an additional short_text input
-field. Usually used for the "Other" thing </p>
+field. Usually, used for the "Other" thing </p>
     <p></p>
   </li>
   <li>Calculation:
Index: openacs-4/packages/assessment/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/requirements.html,v
diff -u -r1.6.2.3 -r1.6.2.4
--- openacs-4/packages/assessment/www/doc/requirements.html	5 Oct 2019 13:43:47 -0000	1.6.2.3
+++ openacs-4/packages/assessment/www/doc/requirements.html	1 Aug 2024 07:38:16 -0000	1.6.2.4
@@ -311,7 +311,7 @@
 Assessment or set of Assessments to a specific set of subjects,
 students or other data entry personnel. These actions potentially will
 involve interfacing with other Workflow management tools (e.g. an
-"Enrollment" package that would handle creation of new Parties (a.k.a.
+"Enrollment" package that would handle creation of new Parties (aka
 clinical trial subjects) in the database.
 </p>
 <p>Schedulers could also be teachers, curriculum designers, site
@@ -354,7 +354,7 @@
 datum, when, whether it is a correct value, whether anyone has looked
 at it or edited it and when, etc etc...)
 </p>
-<p>Staff could be site coordinators in clinical trials, insurance
+<p>Staff could be site coordinators in clinical trials, ensurance
 adjustors, accountants, tax preparation staff, etc.
 </p>
 <h2>System / Application Overview<br>
@@ -584,7 +584,7 @@
       <li> Whether anonymous Subjects are allowed </li>
       <li> Text of email to Subjects to Invite, Remind and Thank them
 for performing Assessment </li>
-      <li> Text of email to Staff to Instuct, Remind and Thank them for
+      <li> Text of email to Staff to Instruct, Remind and Thank them for
 performing Assessment on a Subject </li>
     </ul>
     <p> </p>
Index: openacs-4/packages/assessment/www/doc/sequencing.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/sequencing.html,v
diff -u -r1.5.2.1 -r1.5.2.2
--- openacs-4/packages/assessment/www/doc/sequencing.html	17 Aug 2019 09:29:28 -0000	1.5.2.1
+++ openacs-4/packages/assessment/www/doc/sequencing.html	1 Aug 2024 07:38:16 -0000	1.5.2.2
@@ -112,7 +112,7 @@
 ":item_1234 == 'blue' AND :item_4231 == 'red'". Additionally other
 variables might be defined by the API at a later
 stage,&nbsp; e.g. ":percent_score", which would be replaced by the
-current percentage value (a.k.a. score) that subject had in the test so
+current percentage value (aka score) that subject had in the test so
 far (taken from the as_session_table). It might be interesting to pass
 these variables along in the API,
 this remains to be seen when actually implementing the system.<br>
Index: openacs-4/packages/assessment/www/doc/versioning.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/versioning.html,v
diff -u -r1.2 -r1.2.16.1
--- openacs-4/packages/assessment/www/doc/versioning.html	28 Jul 2004 10:35:57 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/versioning.html	1 Aug 2024 07:38:16 -0000	1.2.16.1
@@ -16,7 +16,7 @@
 </p>
 <p>During its lifetime, an Assessment may undergo revisions in the
 midst of data collection. These revisions may be minor (change of a
-label on an Item or adddition of a new Choice to an Item) or major
+label on an Item or addition of a new Choice to an Item) or major
 (addition or deletion of an entire Section). Obviously in most
 applications, such changes are undesirable and people want to avoid
 them. But the reality is that such changes are inevitable and so the
Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html,v
diff -u -r1.4 -r1.4.2.1
--- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html	4 Aug 2018 09:34:07 -0000	1.4
+++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html	1 Aug 2024 07:38:16 -0000	1.4.2.1
@@ -1,3 +1,3 @@
 <html><head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-   <title>1.&nbsp;Manage Permissions</title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"><link rel="start" href="index.html" title="Triggers and Action Execution in Assessment"><link rel="up" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="prev" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="next" href="ch02s02.html" title="2.&nbsp;Actions Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.&nbsp;Manage Permissions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;2.&nbsp;User Manual</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e54"></a>1.&nbsp;Manage Permissions</h2></div></div></div><p>To create an assessment is necessary to have create permissions over the assessment instance. This permission can be inherit or can be granted by a site wide administrator. This permissions can be managed by the site wide administrator following the Permissions link in the assessment admin page.</p><div class="screenshot"><div class="mediaobject"><img src="resources/create_permissions.JPG"></div></div><p>To create triggers is necessary to have admin permissions over an assessment. The admin permission is inherit to the user that creates an assessment and also can be granted by the assessment administrator. This permissions can be managed follogging the Permission link that appears in the list of assessments.</p><div class="screenshot"><div class="mediaobject"><img src="resources/asm_admin_permissions.JPG"></div></div><p>Both links will lead the user to a page where the necessary permissions can be set.</p><div class="screenshot"><div class="mediaobject"><img src="resources/manage_permissions.JPG"></div></div><p>Also the user can search for another user to manage his permissions:</p><div class="screenshot"><div class="mediaobject"><img src="resources/search_user.JPG"></div></div><p>After clicking OK, the user will appear in the list an the permissions can be set properly.</p><div class="screenshot"><div class="mediaobject"><img src="resources/user_permissions.JPG"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ch02s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter&nbsp;2.&nbsp;User Manual&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;2.&nbsp;Actions Administration</td></tr></table></div></body></html>
\ No newline at end of file
+   <title>1.&nbsp;Manage Permissions</title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"><link rel="start" href="index.html" title="Triggers and Action Execution in Assessment"><link rel="up" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="prev" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="next" href="ch02s02.html" title="2.&nbsp;Actions Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.&nbsp;Manage Permissions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;2.&nbsp;User Manual</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e54"></a>1.&nbsp;Manage Permissions</h2></div></div></div><p>To create an assessment is necessary to have create permissions over the assessment instance. This permission can be inherit or can be granted by a site wide administrator. This permissions can be managed by the site wide administrator following the Permissions link in the assessment admin page.</p><div class="screenshot"><div class="mediaobject"><img src="resources/create_permissions.JPG"></div></div><p>To create triggers is necessary to have admin permissions over an assessment. The admin permission is inherit to the user that creates an assessment and also can be granted by the assessment administrator. This permissions can be managed follogging the Permission link that appears in the list of assessments.</p><div class="screenshot"><div class="mediaobject"><img src="resources/asm_admin_permissions.JPG"></div></div><p>Both links will lead the user to a page where the necessary permissions can be set.</p><div class="screenshot"><div class="mediaobject"><img src="resources/manage_permissions.JPG"></div></div><p>Also the user can search for another user to manage his permissions:</p><div class="screenshot"><div class="mediaobject"><img src="resources/search_user.JPG"></div></div><p>After clicking OK, the user will appear in the list the permissions can be set properly.</p><div class="screenshot"><div class="mediaobject"><img src="resources/user_permissions.JPG"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ch02s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter&nbsp;2.&nbsp;User Manual&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;2.&nbsp;Actions Administration</td></tr></table></div></body></html>
\ No newline at end of file
Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s05.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s05.html,v
diff -u -r1.2 -r1.2.16.1
--- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s05.html	14 Mar 2005 15:48:12 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s05.html	1 Aug 2024 07:38:16 -0000	1.2.16.1
@@ -1,3 +1,3 @@
 <html><head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-   <title>5.&nbsp;Action Triggers</title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"><link rel="start" href="index.html" title="Triggers and Action Execution in Assessment"><link rel="up" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="prev" href="ch02s04.html" title="4.&nbsp;Branch Triggers"><link rel="next" href="ch02s06.html" title="6.&nbsp;Trigger Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.&nbsp;Action Triggers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s04.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;2.&nbsp;User Manual</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ch02s06.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e204"></a>5.&nbsp;Action Triggers</h2></div></div></div><p>To define an Action Trigger, the field "Type" in the form must be checked as "Action".</p><p>The condition field shows the question and its possible anwers, it means that when the user is responding the assessment, if this answer is given for this question, the action will be executed.</p><div class="screenshot"><div class="mediaobject"><img src="resources/action_trigger.JPG"></div></div><p>After the trigger is created, the action related must be chosen, also the time when the action will be executed, and the message shown to the user when the action is executed.</p><p>The actions can be executed in three different times:</p><div class="orderedlist"><ol type="1"><li><p>Immediately: it means that the action will be executed after the user finish to respond the current section.</p></li><li><p>At the end of this Assessment: it means that the action will be executed when the user finish to respond all the sections of the assessment.</p></li><li><p>Manually:this means that the action will be executed by an administrator (i.e. in case that the request needs approval).</p></li></ol></div><div class="screenshot"><div class="mediaobject"><img src="resources/select_action.JPG"></div></div><p>After select the action related to the trigger, the parameters for the action must be set, the select boxes display the options depending on the type of the parameter.</p><div class="itemizedlist"><ul type="disc"><li><p>Query: display the values returned by the query defined for the parameter.</p></li></ul></div><div class="itemizedlist"><ul type="disc"><li><p>Name: the options displayed depends on the time of execution:</p><div class="itemizedlist"><ul type="circle"><li><p>Immediately: display all the questions defined in previuos sections.</p></li></ul></div><div class="itemizedlist"><ul type="circle"><li><p>At the end of the assessment and Manually: display all the questions defined in the assessment.</p></li></ul></div></li></ul></div><div class="screenshot"><div class="mediaobject"><img src="resources/set_params.JPG"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s04.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ch02s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.&nbsp;Branch Triggers&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;6.&nbsp;Trigger Administration</td></tr></table></div></body></html>
\ No newline at end of file
+   <title>5.&nbsp;Action Triggers</title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.0"><link rel="start" href="index.html" title="Triggers and Action Execution in Assessment"><link rel="up" href="ch02.html" title="Chapter&nbsp;2.&nbsp;User Manual"><link rel="prev" href="ch02s04.html" title="4.&nbsp;Branch Triggers"><link rel="next" href="ch02s06.html" title="6.&nbsp;Trigger Administration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.&nbsp;Action Triggers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s04.html">Prev</a>&nbsp;</td><th width="60%" align="center">Chapter&nbsp;2.&nbsp;User Manual</th><td width="20%" align="right">&nbsp;<a accesskey="n" href="ch02s06.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e204"></a>5.&nbsp;Action Triggers</h2></div></div></div><p>To define an Action Trigger, the field "Type" in the form must be checked as "Action".</p><p>The condition field shows the question and its possible answers, it means that when the user is responding the assessment, if this answer is given for this question, the action will be executed.</p><div class="screenshot"><div class="mediaobject"><img src="resources/action_trigger.JPG"></div></div><p>After the trigger is created, the action related must be chosen, also the time when the action will be executed, and the message shown to the user when the action is executed.</p><p>The actions can be executed in three different times:</p><div class="orderedlist"><ol type="1"><li><p>Immediately: it means that the action will be executed after the user finish to respond the current section.</p></li><li><p>At the end of this Assessment: it means that the action will be executed when the user finish to respond all the sections of the assessment.</p></li><li><p>Manually:this means that the action will be executed by an administrator (i.e. in case that the request needs approval).</p></li></ol></div><div class="screenshot"><div class="mediaobject"><img src="resources/select_action.JPG"></div></div><p>After select the action related to the trigger, the parameters for the action must be set, the select boxes display the options depending on the type of the parameter.</p><div class="itemizedlist"><ul type="disc"><li><p>Query: display the values returned by the query defined for the parameter.</p></li></ul></div><div class="itemizedlist"><ul type="disc"><li><p>Name: the options displayed depends on the time of execution:</p><div class="itemizedlist"><ul type="circle"><li><p>Immediately: display all the questions defined in previuos sections.</p></li></ul></div><div class="itemizedlist"><ul type="circle"><li><p>At the end of the assessment and Manually: display all the questions defined in the assessment.</p></li></ul></div></li></ul></div><div class="screenshot"><div class="mediaobject"><img src="resources/set_params.JPG"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s04.html">Prev</a>&nbsp;</td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right">&nbsp;<a accesskey="n" href="ch02s06.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.&nbsp;Branch Triggers&nbsp;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&nbsp;6.&nbsp;Trigger Administration</td></tr></table></div></body></html>
\ No newline at end of file
Index: openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html,v
diff -u -r1.8.2.1 -r1.8.2.2
--- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html	17 Aug 2019 09:29:28 -0000	1.8.2.1
+++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html	1 Aug 2024 07:38:16 -0000	1.8.2.2
@@ -97,10 +97,10 @@
     <ul>
       <li>Availability: 2 date widgets (from, and to). This will set the
 time the time the survey will become visible for the respondees. It is
-overridden by the parameter enabled (if a assessment is not enabled, it
+overridden by the parameter enabled (if an assessment is not enabled, it
 will never be visible, regardless of date).
       </li>
-      <li>How often can a assessment be taken: Number of times a survey
+      <li>How often can an assessment be taken: Number of times a survey
 can be taken by a respondee.
       </li>
       <li>How long has a user to pause: Number of hours a respondee has
@@ -256,7 +256,7 @@
       </li>
       <li>File: file (file for import)
       </li>
-      <li>Download file name: short_text. Filename for the download of
+      <li>Download filename: short_text. Filename for the download of
 the export.
       </li>
     </ul>
Index: openacs-4/packages/assessment/www/doc/user_interface/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/index.html,v
diff -u -r1.7.2.2 -r1.7.2.3
--- openacs-4/packages/assessment/www/doc/user_interface/index.html	5 Oct 2019 13:43:47 -0000	1.7.2.2
+++ openacs-4/packages/assessment/www/doc/user_interface/index.html	1 Aug 2024 07:38:16 -0000	1.7.2.3
@@ -70,7 +70,7 @@
 test results. In addition to this, it will provide functionality to
 other packages to allow rating of their contents (one example of this
 would be Lars Rating package, that would be used as a basis for this).
-In general it should provide a very flexible way of adding scores into
+In general, it should provide a very flexible way of adding scores into
 the system, either automatically (as described above) or manually (e.g.
 this student did a good oral exam).
 <p>In addition to the possibility to enter scores/rates, the grading
@@ -117,7 +117,7 @@
 would be to treat the /pvt/home page as a collection of assessment data
 and the "change basic information" as one assessment among many.</p>
 <p>With a little bit of tweaking and the possibility to add instant
-gratification, a.k.a. aggregated result display, it could include the poll
+gratification, aka aggregated result display, it could include the poll
 package and make it redundant.</p>
 <p>Last but not least with the ability to display questions in a multi
 dimensional way to the user, the assessment system is useful for
Index: openacs-4/packages/assessment/www/doc/user_interface/tests.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/tests.html,v
diff -u -r1.8.2.2 -r1.8.2.3
--- openacs-4/packages/assessment/www/doc/user_interface/tests.html	5 Oct 2019 13:43:47 -0000	1.8.2.2
+++ openacs-4/packages/assessment/www/doc/user_interface/tests.html	1 Aug 2024 07:38:16 -0000	1.8.2.3
@@ -154,7 +154,7 @@
 with it. This can also be negative. For each option the user choose he
 will get the according percentage. If negative points are allowed, the
 user will get a negative percentage. In any case, a user can never get
-more than 100% or less then -100%.
+more than 100% or less than -100%.
       </li>
     </ul>
   </li>
Index: openacs-4/packages/assessment/www/doc/user_interface/user_experience.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/user_experience.html,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/assessment/www/doc/user_interface/user_experience.html	15 Apr 2019 13:35:58 -0000	1.3.2.1
+++ openacs-4/packages/assessment/www/doc/user_interface/user_experience.html	1 Aug 2024 07:38:16 -0000	1.3.2.2
@@ -26,7 +26,7 @@
   </li>
   <li>Starttime of the response will be logged
   </li>
-  <li>First section will be delivered to the user for anwering.
+  <li>First section will be delivered to the user for answering.
   </li>
 </ul>
 Depending on the settings, the display of the assessment will vary:
@@ -60,7 +60,7 @@
   <li>Allow for chancellation of the test with a chancel button. The
 result will not be stored but the test will be marked as taken.
   </li>
-  <li>If immediate answer validation (a.k.a.. ad_form check) for a
+  <li>If immediate answer validation (aka. ad_form check) for a
 question is true, check the answer if it is valid, otherwise notify the
 user that it is not and do not store the result.
   </li>
Index: openacs-4/packages/file-storage/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/file-storage/www/doc/design.html,v
diff -u -r1.6.2.2 -r1.6.2.3
--- openacs-4/packages/file-storage/www/doc/design.html	5 Oct 2019 13:43:48 -0000	1.6.2.2
+++ openacs-4/packages/file-storage/www/doc/design.html	1 Aug 2024 07:38:16 -0000	1.6.2.3
@@ -192,7 +192,7 @@
 
 The main objects of File Storage are "folders" and "files". A "folder"
 is analogous to a subdirectory in the Unix/Windows-world filesystem.
-Folder objects are stored as Content Repostory folders, thus folders
+Folder objects are stored as Content Repository folders, thus folders
 are stored "as is" in the Content Repository.
 
 <p>