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 -r1.10
--- openacs-4/packages/assessment/www/doc/data_collection.html	23 Mar 2018 23:53:01 -0000	1.9
+++ openacs-4/packages/assessment/www/doc/data_collection.html	3 Sep 2024 15:37:35 -0000	1.10
@@ -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>
@@ -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
@@ -249,7 +249,7 @@
     <ul>
       <li><span style="font-weight: bold;">Signing of content</span> allows
         to verify that the data submitted is actually from the person it is
-        pretended to be from. This assumes an public key environment where the
+        pretended to be from. This assumes a public key environment where the
         public key is stored along with the user information (e.g. with the
         users table) and the data stored in as_item_data is additionally stored
         in a signed version (signed with the secret key of the user). To verify