Merge pull request #792 from aaaaalbert/fix-typos-in-ODD-tutorial

Fix typos, formatting, formulations in ODD tutorial

Author: musicEnfanthen

_tutorials/180_understanding_odd/180_understanding_odd-03.html

@@ -1,6 +1,6 @@
 <div>    
     <p>
-        Despite it's name, the setup for working with ODD usually requires at least <u>two</u> <em>logical</em> files (though these may spread 
+        Despite its name, the setup for working with ODD usually requires at least <u>two</u> <em>logical</em> files (though these may spread 
         across many more files in the file system, as shown in the following step of this tutorial). The first of these files is the 
         so-called <em>source</em>: It holds the full specification of the format, in this case MEI. In our repository, it is located in the
         <a href="https://github.com/music-encoding/music-encoding/blob/develop/source/mei-source.xml" target="_blank" rel="noopener, noreferrer">mei-source.xml</a> file. 

_tutorials/180_understanding_odd/180_understanding_odd-06.html

@@ -70,7 +70,7 @@
     <pre class="codeblock">&lt;elementSpec ident="dedicatee" module="MEI.shared"&gt;
     &lt;desc&gt;Entity to whom a creative work is formally offered.&lt;/desc&gt;
     &lt;classes&gt;
-        &lt;-- other memberShips removed for brevity --&gt;
+        &lt;!-- other memberShips removed for brevity --&gt;
         &lt;memberOf key="model.textPhraseLike.limited"/&gt;
     &lt;/classes&gt;
     &lt;content&gt;
@@ -81,7 +81,7 @@
             &lt;/rng:choice&gt;
         &lt;/rng:zeroOrMore&gt;
     &lt;/content&gt;
-    &lt;-- constraintSpec removed for brevity--&gt;
+    &lt;!-- constraintSpec removed for brevity--&gt;
 &lt;/elementSpec&gt;</pre>
     <p>
         The element has a <em>&lt;memberOf&gt;</em> element, which uses its <strong>@key</strong> attribute to reference the 

_tutorials/180_understanding_odd/180_understanding_odd-07.html

@@ -20,7 +20,7 @@
         applicable). 
     </p>
     <p>
-        Now let's have a look for these <em>&lt;attDef&gt;</em> elements are located. Even though that's not really the preferred solution, sometimes
+        Now let's have a look where these <em>&lt;attDef&gt;</em> elements are located. Even though that's not really the preferred solution, sometimes
         attributes are defined at the element where they need to be used, as with the <em>@type</em> attribute on 
         <a href="/guidelines/v5/elements/meiHead.html" target="_blank" rel="noopener, noreferrer">&lt;meiHead&gt;</a>:
     </p>
@@ -108,13 +108,13 @@
     &lt;/classes&gt;
 &lt;/classSpec&gt;</pre>
     <p>
-        Again, it is through the use of a <em>&lt;memberOf</em> element with the proper <em>@key</em> how membership in different classes is achieved in 
+        Again, it is through the use of a <em>&lt;memberOf&gt;</em> element with the proper <em>@key</em> how membership in different classes is achieved in 
         MEI, so this mechanism should be familiar already. And just like with <em>model classes</em>, <em>attribute classes</em> are used from rather generic
         classes to very specific sets of well-aligned attributes. By subscribing to the right attribute class(es), an element may thus get just the right set of 
         attributes, and it becomes possible to selectively add or remove attributes to new or existing elements by modifying these memberships.  
     </p>
     <p>
-        In specs for <em>att.common</em> above reveal another attribute class <em>att.typed</em> which provides an attribute 
+        The specs for <em>att.common</em> above reveal another attribute class <em>att.typed</em> which provides an attribute 
         <em>@type</em>. Obviously, this hasn't been used on <em>&lt;meiHead&gt;</em>, as seen above. The reason is that the attribute class
         provides a <em>@type</em> attribute which has only a very generic description: <em>Designation which characterizes the element 
             in some sense, using any convenient classification scheme or typology that employs single-token labels.</em> 

_tutorials/180_understanding_odd/180_understanding_odd-08.html

@@ -16,7 +16,7 @@
         RelaxNG. The <em>@maxOccurs</em> and <em>@minOccurs</em> attributes define how often a value of this type may be given. An 
         example for other values can be found for the <em>@staff</em> attribute defined in <em>att.staffIdent</em>. This attribute
         is used to associate 
-        <a href="/guidelines/v5/content/introduction.html#eventsControlevents" target="_blank" rel="noopener, noreferrer">controlevents</a>
+        <a href="/guidelines/v5/content/introduction.html#eventsControlevents" target="_blank" rel="noopener, noreferrer">ControlEvents</a>
         with one or more staves, and may hold one or more integers. It uses 
         <a href="/guidelines/v5/attribute-classes/att.staffIdent.html" target="_blank" rel="noopener, noreferrer">the following markup</a> to achieve this:
     </p>
@@ -156,4 +156,4 @@
         <em>attribute classes</em>, data types are often considered to be more accessible when getting into ODD – there is 
         surely less to learn. So let's move on to <em>Macros</em>.
     </p>
-</div>
+</div>