Index: openacs-4/packages/assessment/lib/assessment.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/lib/assessment.tcl,v
diff -u -r1.33.2.1 -r1.33.2.2
--- openacs-4/packages/assessment/lib/assessment.tcl	12 Apr 2019 21:26:56 -0000	1.33.2.1
+++ openacs-4/packages/assessment/lib/assessment.tcl	17 Aug 2019 09:29:28 -0000	1.33.2.2
@@ -534,7 +534,7 @@
 
     set after_submit "{
         \# NOTE the code just incrementes section order so when the section order
-        \# is greate than the number of items in the list of sections
+        \# is greater than the number of items in the list of sections
         \# we know we are done and should finish the assessment
         if { \$new_section_order ne \"\" && \$new_section_order <= \[llength \$section_list\]} {
             # go to next section
Index: openacs-4/packages/assessment/www/doc/as_items.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_items.adp,v
diff -u -r1.9 -r1.9.2.1
--- openacs-4/packages/assessment/www/doc/as_items.adp	4 Aug 2018 09:34:07 -0000	1.9
+++ openacs-4/packages/assessment/www/doc/as_items.adp	17 Aug 2019 09:29:28 -0000	1.9.2.1
@@ -57,7 +57,7 @@
 as_item-related subsystems, including the as_item Display subsystem
 described <a style="font-family: monospace;" href="display_types">here</a>.<br>
 </span></p>
-<center><p><span class="context"><img alt="Data modell graphic" src="images/assessment-itemfocus.jpg" style="width: 752px; height: 1121px;"></span></p></center>
+<center><p><span class="context"><img alt="Data model graphic" src="images/assessment-itemfocus.jpg" style="width: 752px; height: 1121px;"></span></p></center>
 <h2><span class="context">Core Function: as_items<br>
 </span></h2>
 <ul><li>
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 -r1.16.2.1
--- openacs-4/packages/assessment/www/doc/as_items.html	4 Aug 2018 09:34:07 -0000	1.16
+++ openacs-4/packages/assessment/www/doc/as_items.html	17 Aug 2019 09:29:28 -0000	1.16.2.1
@@ -69,7 +69,7 @@
  style="font-family: monospace;" href="display_types.html">here</a>.<br>
 </p>
 <center>
-<p><img alt="Data modell graphic" src="images/assessment-itemfocus.jpg"
+<p><img alt="Data model graphic" src="images/assessment-itemfocus.jpg"
  style="width: 752px; height: 1121px;"></p>
 </center>
 <p>
Index: openacs-4/packages/assessment/www/doc/data-modell.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/Attic/data-modell.adp,v
diff -u -r1.3 -r1.3.2.1
--- openacs-4/packages/assessment/www/doc/data-modell.adp	5 Apr 2018 14:44:08 -0000	1.3
+++ openacs-4/packages/assessment/www/doc/data-modell.adp	17 Aug 2019 09:29:28 -0000	1.3.2.1
@@ -1,6 +1,6 @@
 
-<property name="context">{/doc/assessment {Assessment}} {Assessment Data Modell Overview}</property>
-<property name="doc(title)">Assessment Data Modell Overview</property>
+<property name="context">{/doc/assessment {Assessment}} {Assessment Data Model Overview}</property>
+<property name="doc(title)">Assessment Data Model Overview</property>
 <master>
 <h2>Overview</h2>
 <p>At its core, the Assessment package defines a hierarchical
@@ -84,5 +84,5 @@
 system</li>
 </ul>
 <center>
-<a href="http://openacs.org/storage/download/assessment.graffle?version_id=187542"></a><p><img alt="Data Modell Graphic" src="images/assessment.jpg" style="width: 1076px; height: 1442px;"></p>
+<a href="http://openacs.org/storage/download/assessment.graffle?version_id=187542"></a><p><img alt="Data Model Graphic" src="images/assessment.jpg" style="width: 1076px; height: 1442px;"></p>
 </center>
Index: openacs-4/packages/assessment/www/doc/data-modell.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/Attic/data-modell.html,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/assessment/www/doc/data-modell.html	5 Apr 2018 14:44:08 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/data-modell.html	17 Aug 2019 09:29:28 -0000	1.2.2.1
@@ -3,7 +3,7 @@
 <head>
   <meta content="text/html; charset=ISO-8859-1"
  http-equiv="content-type">
-  <title>Assessment Data Modell Overview</title>
+  <title>Assessment Data Model Overview</title>
 </head>
 <body>
 <h2>Overview</h2>
@@ -104,7 +104,7 @@
 </ul>
 <center><a
  href="http://openacs.org/storage/download/assessment.graffle?version_id=187542"></a>
-<p><img alt="Data Modell Graphic" src="images/assessment.jpg"
+<p><img alt="Data Model Graphic" src="images/assessment.jpg"
  style="width: 1076px; height: 1442px;"></p>
 </center>
 </body>
Index: openacs-4/packages/assessment/www/doc/data_collection.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/data_collection.adp,v
diff -u -r1.5.2.1 -r1.5.2.2
--- openacs-4/packages/assessment/www/doc/data_collection.adp	11 Mar 2019 08:43:27 -0000	1.5.2.1
+++ openacs-4/packages/assessment/www/doc/data_collection.adp	17 Aug 2019 09:29:28 -0000	1.5.2.2
@@ -5,7 +5,7 @@
 <h2>Overview</h2>
 <p>The schema for the entities that actually collect, store and
 retrieve Assessment data parallels the hierarchical structure of
-the <a href="data-modell">Metadata Data Model</a>. In the
+the <a href="data-model">Metadata Data Model</a>. In the
 antecedent "complex survey" and "questionnaire"
 systems, this schema was simple two-level structure:</p>
 <ul>
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.1 -r1.9.2.2
--- openacs-4/packages/assessment/www/doc/data_collection.html	15 Apr 2019 13:35:58 -0000	1.9.2.1
+++ openacs-4/packages/assessment/www/doc/data_collection.html	17 Aug 2019 09:29:28 -0000	1.9.2.2
@@ -10,7 +10,7 @@
     <p>
       The schema for the entities that actually collect, store and retrieve
       Assessment data parallels the hierarchical structure of the <a
-        href="data-modell.html">Metadata Data Model</a>. In the antecedent
+        href="data-model.html">Metadata Data Model</a>. In the antecedent
       "complex survey" and "questionnaire" systems, this schema was simple
       two-level structure:
     </p>
Index: openacs-4/packages/assessment/www/doc/display_types.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.adp,v
diff -u -r1.7 -r1.7.2.1
--- openacs-4/packages/assessment/www/doc/display_types.adp	4 Aug 2018 09:34:07 -0000	1.7
+++ openacs-4/packages/assessment/www/doc/display_types.adp	17 Aug 2019 09:29:28 -0000	1.7.2.1
@@ -144,7 +144,7 @@
 <ul>
 <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 DATAMODELL FROM PAGINATION_STYLE. How many questions shall
+IN THE DATA MODEL FROM PAGINATION_STYLE. How many questions shall
 be 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
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 -r1.9.2.1
--- openacs-4/packages/assessment/www/doc/display_types.html	4 Aug 2018 09:34:07 -0000	1.9
+++ openacs-4/packages/assessment/www/doc/display_types.html	17 Aug 2019 09:29:28 -0000	1.9.2.1
@@ -176,7 +176,7 @@
 <ul>
   <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 DATAMODELL FROM PAGINATION_STYLE. How many questions shall be
+THE DATA MODEL FROM PAGINATION_STYLE. How many questions shall be
 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>
Index: openacs-4/packages/assessment/www/doc/grouping.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/grouping.adp,v
diff -u -r1.8 -r1.8.2.1
--- openacs-4/packages/assessment/www/doc/grouping.adp	4 Aug 2018 09:34:07 -0000	1.8
+++ openacs-4/packages/assessment/www/doc/grouping.adp	17 Aug 2019 09:29:28 -0000	1.8.2.1
@@ -6,7 +6,7 @@
 package that organizes Items into Sections and whole
 Assessments:<br>
 </p>
-<center><p><img alt="Data modell graphic" src="images/assessment-groupingfocus.jpg" style="width: 797px; height: 565px;"></p></center>
+<center><p><img alt="Data model graphic" src="images/assessment-groupingfocus.jpg" style="width: 797px; height: 565px;"></p></center>
 <h2>Review of Specific Entities</h2>
 <ul>
 <li>Assessments (as_assessments) are the highest-level container in
@@ -34,7 +34,7 @@
 surveys), or if it provides an "assessment service" to
 another OpenACS app, or a "web service" via SOAP etc</li><li>editable_p - whether the response to the assessment is editable
 once an item has been responded to by the user.</li><li><span class="context"><span class="reg">anonymous_p - This
-shows whether the creator of the accessment will have the
+shows whether the creator of the assessment will have the
 possibility to see the personal details of the respondee or not. In
 particular this will exclude the user_id from the CSV files. It
 shall still be possible to see the user that have not finished the
@@ -89,7 +89,7 @@
 </li><li>custom_footer<br>
 </li><li>form_template - Style (form_template) that will be used for
 this assessment. You can either select an existing one or upload a
-new style as well as edit the currently chosen one (no datamodell
+new style as well as edit the currently chosen one (no data model
 but UI thought).<br>
 </li><li>
 <span class="context"><span class="reg">progress_bar: What kind
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 -r1.7.2.1
--- openacs-4/packages/assessment/www/doc/grouping.html	4 Aug 2018 09:34:07 -0000	1.7
+++ openacs-4/packages/assessment/www/doc/grouping.html	17 Aug 2019 09:29:28 -0000	1.7.2.1
@@ -11,7 +11,7 @@
 that organizes Items into Sections and whole Assessments:<br>
 </p>
 <center>
-<p><img alt="Data modell graphic"
+<p><img alt="Data model graphic"
  src="images/assessment-groupingfocus.jpg"
  style="width: 797px; height: 565px;"></p>
 </center>
@@ -55,7 +55,7 @@
       <li>editable_p - whether the response to the assessment is
 editable once an item has been responded to by the user. </li>
       <li><span class="context"><span class="reg">anonymous_p - This
-shows whether the creator of the accessment will have
+shows whether the creator of the assessment will have
 the possibility to see the personal details of the respondee or not. In
 particular this will exclude the user_id from the CSV files. It shall
 still be possible to see the user that have not finished the survey
@@ -128,7 +128,7 @@
     <li>form_template - Style (form_template) that will be
 used for this assessment. You can either select an existing one or
 upload a new style as well as edit the currently chosen one (no
-datamodell but UI thought). <br>
+data model but UI thought). <br>
     </li>
     <li><span class="context"><span class="reg">progress_bar: What
 kind of progress bar shall be
Index: openacs-4/packages/assessment/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/index.adp,v
diff -u -r1.5 -r1.5.2.1
--- openacs-4/packages/assessment/www/doc/index.adp	4 Aug 2018 09:34:07 -0000	1.5
+++ openacs-4/packages/assessment/www/doc/index.adp	17 Aug 2019 09:29:28 -0000	1.5.2.1
@@ -131,7 +131,7 @@
 The API will be defined during the development phase.<br>
 <h2>Data model</h2>
 
-The data model is described in detail in the <a href="data-modell">design descriptions</a>
+The data model is described in detail in the <a href="data-model">design descriptions</a>
 .<br>
 <h2><a href="user_interface/index">User Interface</a></h2>
 
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 -r1.9.2.1
--- openacs-4/packages/assessment/www/doc/index.html	4 Aug 2018 09:34:07 -0000	1.9
+++ openacs-4/packages/assessment/www/doc/index.html	17 Aug 2019 09:29:28 -0000	1.9.2.1
@@ -182,7 +182,7 @@
 The API will be defined during the development phase.<br>
 <h2>Data model</h2>
 The data model is described in detail in the <a
- href="data-modell.html">design descriptions</a>. <br>
+ href="data-model.html">design descriptions</a>. <br>
 <h2><a href="user_interface/index.html">User Interface</a></h2>
 The UI for Assessment divides into a number of primary functional
 areas, with the entry page located <a href="user_interface/index.html">here</a>.
Index: openacs-4/packages/assessment/www/doc/item_types.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/item_types.adp,v
diff -u -r1.4 -r1.4.2.1
--- openacs-4/packages/assessment/www/doc/item_types.adp	4 Aug 2018 09:34:07 -0000	1.4
+++ openacs-4/packages/assessment/www/doc/item_types.adp	17 Aug 2019 09:29:28 -0000	1.4.2.1
@@ -126,7 +126,7 @@
 <ul>
 <li>Allow Multiple: boolean (yes/no). This will determine if the
 respondee has the option to choose multiple possible answers for
-his response. In the datamodell this information is stored with the
+his response. In the data model this information is stored with the
 as_item_display_* object (e.g. along with the checkbox /
 select).</li><li>Increasing: boolean (all or nothing / increasing). All or
 nothing will either give 100%, if all correct answers are given, or
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 -r1.6.2.1
--- openacs-4/packages/assessment/www/doc/item_types.html	4 Aug 2018 09:34:07 -0000	1.6
+++ openacs-4/packages/assessment/www/doc/item_types.html	17 Aug 2019 09:29:28 -0000	1.6.2.1
@@ -166,7 +166,7 @@
           <li>Allow Multiple: boolean (yes/no). This will determine if
 the
 respondee has the option to choose multiple possible answers for his
-response. In the datamodell this information is stored with the
+response. In the data model this information is stored with the
 as_item_display_* object (e.g. along with the checkbox / select). </li>
           <li>Increasing: boolean (all or nothing /
 increasing).
Index: openacs-4/packages/assessment/www/doc/page_flow.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/page_flow.adp,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/assessment/www/doc/page_flow.adp	7 Aug 2017 23:48:04 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/page_flow.adp	17 Aug 2019 09:29:28 -0000	1.2.2.1
@@ -79,5 +79,5 @@
 interrelate:</li>
 </ul>
 <center>
-<a href="http://openacs.org/storage/download/assessment-page-flow.graffle?version_id=166250"></a><p><img alt="data modell" src="images/assessment-page-flow.jpg" style="width: 950px; height: 1058px;"></p>
+<a href="http://openacs.org/storage/download/assessment-page-flow.graffle?version_id=166250"></a><p><img alt="data model" src="images/assessment-page-flow.jpg" style="width: 950px; height: 1058px;"></p>
 </center>
Index: openacs-4/packages/assessment/www/doc/page_flow.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/page_flow.html,v
diff -u -r1.2 -r1.2.16.1
--- openacs-4/packages/assessment/www/doc/page_flow.html	29 Jul 2004 09:35:11 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/page_flow.html	17 Aug 2019 09:29:28 -0000	1.2.16.1
@@ -94,7 +94,7 @@
 interrelate:
 <center><a
  href="http://openacs.org/storage/download/assessment-page-flow.graffle?version_id=166250"></a>
-<p><img alt="data modell" src="images/assessment-page-flow.jpg"
+<p><img alt="data model" src="images/assessment-page-flow.jpg"
  style="width: 950px; height: 1058px;"></p>
 </center>
 </body>
Index: openacs-4/packages/assessment/www/doc/policies.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/policies.adp,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/assessment/www/doc/policies.adp	7 Aug 2017 23:48:04 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/policies.adp	17 Aug 2019 09:29:28 -0000	1.2.2.1
@@ -43,7 +43,7 @@
 enrolled in a trial or the beginning of a term</li><li>optimal_days_pre - along with the next attribute, defines a
 range of dates when the Assessment should be performed (if zero,
 then the date must be exact)</li><li>optimal_days_post</li><li>required_days_pre - as above, only the range within which the
-Assessment must be performed</li><li>required_days_post</li><li style="font-family: monospace;"><center><p><img alt="Data modell" src="images/assessment-schedfocus.jpg" style="width: 716px; height: 653px;"></p></center></li>
+Assessment must be performed</li><li>required_days_post</li><li style="font-family: monospace;"><center><p><img alt="Data model" src="images/assessment-schedfocus.jpg" style="width: 716px; height: 653px;"></p></center></li>
 </ul>
 </li>
 </ul>
Index: openacs-4/packages/assessment/www/doc/policies.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/policies.html,v
diff -u -r1.1 -r1.1.16.1
--- openacs-4/packages/assessment/www/doc/policies.html	13 Jun 2004 23:20:44 -0000	1.1
+++ openacs-4/packages/assessment/www/doc/policies.html	17 Aug 2019 09:29:28 -0000	1.1.16.1
@@ -113,7 +113,7 @@
       <li> required_days_post</li>
       <li style="font-family: monospace;">
         <center>
-        <p><img alt="Data modell" src="images/assessment-schedfocus.jpg"
+        <p><img alt="Data model" src="images/assessment-schedfocus.jpg"
  style="width: 716px; height: 653px;">
         </p>
         </center>
Index: openacs-4/packages/assessment/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/requirements.adp,v
diff -u -r1.6.2.1 -r1.6.2.2
--- openacs-4/packages/assessment/www/doc/requirements.adp	11 Mar 2019 08:43:27 -0000	1.6.2.1
+++ openacs-4/packages/assessment/www/doc/requirements.adp	17 Aug 2019 09:29:28 -0000	1.6.2.2
@@ -250,7 +250,7 @@
 two sections only 30% towards the total score. Each section
 consists of multiple questions that have a different weight (in
 percent) for the total score of the section. The sum of the weights
-has to be 100%, otherwise the author of the section get&#39;s a
+has to be 100%, otherwise the author of the section gets a
 warning. Some of the questions are multiple choice questions, that
 get different percentages for each answer. As the computer science
 department wants to discourage students from giving wrong answers,
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.1 -r1.6.2.2
--- openacs-4/packages/assessment/www/doc/requirements.html	15 Apr 2019 13:35:58 -0000	1.6.2.1
+++ openacs-4/packages/assessment/www/doc/requirements.html	17 Aug 2019 09:29:28 -0000	1.6.2.2
@@ -243,7 +243,7 @@
 sections only 30% towards the total score. Each section consists of
 multiple questions that have a different weight (in percent) for the
 total score of the section. The sum of the weights has to be 100%,
-otherwise the author of the section get's a warning. Some of the
+otherwise the author of the section gets a warning. Some of the
 questions are multiple choice questions, that get different percentages
 for each answer. As the computer science department wants to discourage
 students from giving wrong answers, some wrong answers have a negative
Index: openacs-4/packages/assessment/www/doc/sequencing.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/sequencing.adp,v
diff -u -r1.4 -r1.4.2.1
--- openacs-4/packages/assessment/www/doc/sequencing.adp	4 Aug 2018 09:34:07 -0000	1.4
+++ openacs-4/packages/assessment/www/doc/sequencing.adp	17 Aug 2019 09:29:28 -0000	1.4.2.1
@@ -41,7 +41,7 @@
 <p>So how might we implement this in our datamodel? Consider the
 "sequencing" subsystem of the Assessment package:<br>
 </p>
-<center><p><img alt="Data Modell Graphic" src="images/assessment-sequencefocus.jpg" style="width: 711px; height: 707px;"></p></center>
+<center><p><img alt="Data Model Graphic" src="images/assessment-sequencefocus.jpg" style="width: 711px; height: 707px;"></p></center>
 <h2>Specific Entities</h2>
 <ul>
 <li>Item-checks (as_item_checks) define 1..n ordered evaluations of
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 -r1.5.2.1
--- openacs-4/packages/assessment/www/doc/sequencing.html	4 Aug 2018 09:34:07 -0000	1.5
+++ openacs-4/packages/assessment/www/doc/sequencing.html	17 Aug 2019 09:29:28 -0000	1.5.2.1
@@ -50,7 +50,7 @@
 </p>
 <p></p>
 <center>
-<p><img alt="Data Modell Graphic"
+<p><img alt="Data Model Graphic"
  src="images/assessment-sequencefocus.jpg"
  style="width: 711px; height: 707px;"></p>
 </center>
Index: openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp,v
diff -u -r1.9 -r1.9.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp	3 Jul 2018 18:19:14 -0000	1.9
+++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp	17 Aug 2019 09:29:28 -0000	1.9.2.1
@@ -7,12 +7,12 @@
 determine the look and feel of the assessment along with the option
 to view the responses. This is a list of attributes the
 administrator can edit when creating an assessment. The grouping is
-based on the UI and not on the datamodell. So you should follow
+based on the UI and not on the data model. So you should follow
 this with regards to the UI:</span></span>
 <ul>
 <li><span class="context">Title: Title of the
-accessment</span></li><li><span class="context">Anonymous Accessment: boolean (yes/no).
-This shows whether the creator of the accessment will have the
+assessment</span></li><li><span class="context">Anonymous Assessment: boolean (yes/no).
+This shows whether the creator of the assessment will have the
 possibility to see the personal details of the respondee or not. In
 particular this will exclude the user_id from the CSV files. It
 shall still be possible to see the user that have not finished the
@@ -66,10 +66,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 accessment is not
-enabled, it will never be visible, regardless of date).</li><li>How often can a accessment be taken: Number of times a survey
+is overridden by the parameter enabled (if a 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
 can be taken by a respondee.</li><li>How long has a user to pause: Number of hours a respondee has
-to wait before he can take the accessment again.</li><li>Answer_time: integer: Time in minutes a respondee has to answer
+to wait before he can take the assessment again.</li><li>Answer_time: integer: Time in minutes a respondee has to answer
 a survey.</li>
 </ul>
 </li><li>Show comments to the user
@@ -87,10 +87,10 @@
 defined. Otherwise we will write a small page, that allows the
 admin to select exams and a minimum point number the student has to
 have achieved in that exam.</li><li>Bulk upload: file. Upload a CSV file with email addresses to
-allow access to the accessment. Add users to the system if not
+allow access to the assessment. Add users to the system if not
 already part of it. Notify users via email that they should take
-the accessment.</li><li>Password: short_text. Password that has to be typed in before
-the respondee get&#39;s access to the accessment. This should be
+the assessment.</li><li>Password: short_text. Password that has to be typed in before
+the respondee gets access to the assessment. This should be
 done by creating a registered filter that returns a 401 to popup an
 HTTP auth box. look in oacs_dav::authenticate for an example of how
 to check the username/password<br>
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 -r1.8.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html	3 Jul 2018 18:19:14 -0000	1.8
+++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html	17 Aug 2019 09:29:28 -0000	1.8.2.1
@@ -11,13 +11,13 @@
 determine the look and feel of the assessment along with the option to
 view the responses. This is a list of attributes the administrator can
 edit when creating an assessment. The grouping is based on the UI and
-not on the datamodell. So you should follow this with regards to the
+not on the data model. So you should follow this with regards to the
 UI:
 <ul>
-  <li>Title: Title of the accessment
+  <li>Title: Title of the Assessment
   </li>
-  <li>Anonymous Accessment: boolean (yes/no). This shows whether the
-creator of the accessment will have the possibility to see the personal
+  <li>Anonymous Assessment: boolean (yes/no). This shows whether the
+creator of the assessment will have the possibility to see the personal
 details of the respondee or not. In particular this will exclude the
 user_id from the CSV files. It shall still be possible to see the user
 that have not finished the survey though.
@@ -97,14 +97,14 @@
     <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 accessment is not enabled, it
+overridden by the parameter enabled (if a assessment is not enabled, it
 will never be visible, regardless of date).
       </li>
-      <li>How often can a accessment be taken: Number of times a survey
+      <li>How often can a 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
-to wait before he can take the accessment again.
+to wait before he can take the assessment again.
       </li>
       <li>Answer_time: integer: Time in minutes a respondee has to
 answer a survey.
@@ -136,11 +136,11 @@
 achieved in that exam.
       </li>
       <li>Bulk upload: file. Upload a CSV file with email addresses to
-allow access to the accessment. Add users to the system if not already
+allow access to the assessment. Add users to the system if not already
 part of it. Notify users via email that they should take the
-accessment. </li>
+assessment. </li>
       <li>Password: short_text. Password that has to be typed in before
-the respondee get's access to the accessment. This should be done by
+the respondee gets access to the assessment. This should be done by
 creating a registered filter that returns a 401 to popup an HTTP auth
 box. look in oacs_dav::authenticate for an example of how to check the
 username/password<br>
Index: openacs-4/packages/assessment/www/doc/user_interface/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/index.adp,v
diff -u -r1.8 -r1.8.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/index.adp	4 Aug 2018 09:34:07 -0000	1.8
+++ openacs-4/packages/assessment/www/doc/user_interface/index.adp	17 Aug 2019 09:29:28 -0000	1.8.2.1
@@ -114,7 +114,7 @@
 system to collect user information. When signing up to a site the
 user could be asked to fill out an assessment where part of the
 questions will be stored in the acs_users table, some other
-questions in other tables and the rest in the accessment package.
+questions in other tables and the rest in the assessment package.
 This way a quick view can be given about the user (aggregating user
 information in a flexible way). Best explanation would be to treat
 the /pvt/home page as a collection of assessment data and the
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 -r1.7.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/index.html	4 Aug 2018 09:34:07 -0000	1.7
+++ openacs-4/packages/assessment/www/doc/user_interface/index.html	17 Aug 2019 09:29:28 -0000	1.7.2.1
@@ -112,7 +112,7 @@
 information. When signing up to a site the user could be asked to fill
 out an assessment where part of the questions will be stored in the
 acs_users table, some other questions in other tables and the rest in
-the accessment package. This way a quick view can be given about the
+the assessment package. This way a quick view can be given about the
 user (aggregating user information in a flexible way). Best explanation
 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>
Index: openacs-4/packages/assessment/www/doc/user_interface/section_creation.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/section_creation.adp,v
diff -u -r1.6 -r1.6.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/section_creation.adp	4 Aug 2018 09:34:07 -0000	1.6
+++ openacs-4/packages/assessment/www/doc/user_interface/section_creation.adp	17 Aug 2019 09:29:28 -0000	1.6.2.1
@@ -4,7 +4,7 @@
 <master>
 <!-- START HEADER --><span class="context"><span class="reg">Section page. This page is for editing information about a
 section and adding questions to it. It contains a couple of
-subpages. Datamodell can be found <a href="http://sussdorff.de/assessment/doc/grouping.html">here.</a><br><br>
+subpages. Data model can be found <a href="http://sussdorff.de/assessment/doc/grouping.html">here.</a><br><br>
 On the Top of the page display the title and description along with
 the display type for information purposes. Below this put links to
 the following pages.<br><br>
Index: openacs-4/packages/assessment/www/doc/user_interface/section_creation.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/section_creation.html,v
diff -u -r1.5 -r1.5.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/section_creation.html	4 Aug 2018 09:34:07 -0000	1.5
+++ openacs-4/packages/assessment/www/doc/user_interface/section_creation.html	17 Aug 2019 09:29:28 -0000	1.5.2.1
@@ -8,7 +8,7 @@
 <body bgcolor="white" text="black">
 <!-- START HEADER --><span class="context"><span class="reg">
 Section page. This page is for editing information about a section and
-adding questions to it. It contains a couple of subpages. Datamodell
+adding questions to it. It contains a couple of subpages. Data model
 can be found <a href="http://sussdorff.de/assessment/doc/grouping.html">here.</a><br>
 <br>
 On the Top of the page display the title and description along with the
Index: openacs-4/packages/assessment/www/doc/user_interface/tests.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/tests.adp,v
diff -u -r1.8 -r1.8.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/tests.adp	4 Aug 2018 09:34:07 -0000	1.8
+++ openacs-4/packages/assessment/www/doc/user_interface/tests.adp	17 Aug 2019 09:29:28 -0000	1.8.2.1
@@ -3,7 +3,7 @@
 <property name="doc(title)">Tests</property>
 <master>
 <!-- START HEADER --><span class="context"><span class="reg">A
-test is a special kind of accessment that allows the
+test is a special kind of assessment that allows the
 respondee&#39;s answers to be rated immediately. Unless otherwise
 stated, all pages described are admin viewable only.</span></span>
 <ul>
@@ -100,7 +100,7 @@
 <li><span class="context">All or nothing. In this scenario it will
 be looked, if all correct answers have been chosen by the respondee
 and none of the incorrect ones. If this is the case, respondee
-get&#39;s 100%, otherwise nothing.</span></li><li><span class="context">Cumultative. Each answer has a certain
+gets 100%, otherwise nothing.</span></li><li><span class="context">Cumultative. Each answer has a certain
 percentage associated 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
@@ -109,7 +109,7 @@
 </ul>
 </li><li>
 <span class="context">Matching question</span><ul>
-<li><span class="context">All or nothing: User get&#39;s 100% if
+<li><span class="context">All or nothing: User gets 100% if
 all matches are correct, 0% otherwise.</span></li><li><span class="context">Equally weighted: Each match is worth
 100/{number of matches} percent. Each correct match will give the
 according percentage and the end result will be the sum of all
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 -r1.8.2.1
--- openacs-4/packages/assessment/www/doc/user_interface/tests.html	4 Aug 2018 09:34:07 -0000	1.8
+++ openacs-4/packages/assessment/www/doc/user_interface/tests.html	17 Aug 2019 09:29:28 -0000	1.8.2.1
@@ -7,7 +7,7 @@
 </head>
 <body bgcolor="white" text="black">
 <!-- START HEADER --><span class="context"><span class="reg">
-A test is a special kind of accessment that allows the respondee's
+A test is a special kind of assessment that allows the respondee's
 answers to be rated immediately. Unless otherwise stated, all pages
 described are admin viewable only.
 <ul>
@@ -148,7 +148,7 @@
       <li>All or nothing. In this scenario it will be looked, if all
 correct
 answers have been chosen by the respondee and none of the incorrect
-ones. If this is the case, respondee get's 100%, otherwise nothing.
+ones. If this is the case, respondee gets 100%, otherwise nothing.
       </li>
       <li>Cumultative. Each answer has a certain percentage associated
 with it. This can also be negative. For each option the user choose he
@@ -160,7 +160,7 @@
   </li>
   <li>Matching question
     <ul>
-      <li>All or nothing: User get's 100% if all matches are correct,
+      <li>All or nothing: User gets 100% if all matches are correct,
 0% otherwise.
       </li>
       <li>Equally weighted: Each match is worth 100/{number of matches}