address #630

I'm not entirely satisfied with the addition in common/terms.html,
as it seems too detailed for the terminology section. But...

...as pointed out in the comment of #630,
the API spec references to this definition in multiple places,
and many of those links are actually for instances of the internal representation,
*not* for instances of the strings or maps that represent term definition in JSON.

So the alternative would be to introduce a new name for those "internal term definition"
and patch all the algorithms... which seems laborious and error-prone.

@gkellogg I don't remember what's the process for synchronizing the files in common with other specs.

Author: pchampin

common/terms.html

@@ -382,7 +382,8 @@
     as a key, type, or elsewhere that a string is interpreted as a vocabulary item.
     Its value is either a string (<dfn data-cite="JSON-LD11#dfn-simple-term-definition" data-lt="simple term definition|simple term" data-lt-noDefault>simple term definition</dfn>),
     expanding to an <a>IRI</a>,
-    or a map (<a>expanded term definition</a>).
+    or a map (<a>expanded term definition</a>).<br/>
+    <span class="change">For <a data-cite="JSON-LD11-API#context-processing-algorithms">context processing</a>, <a>term definitions</a>' values are converted internally to a dedicated data structure</span> that is easier to process.
   </dd>
   <dt class="changed"><dfn data-cite="JSON-LD11#dfn-type-map">type map</dfn></dt><dd class="changed">
     A <a>type map</a> is a <a>map</a> value of a <a>term</a>

index.html

@@ -1074,7 +1074,7 @@ <h2>RDF Serialization/Deserialization</h2>
     <p>The <a>active context</a> consists of:</p>
     <ul>
       <li>the active <a>term definitions</a> which specify how
-        keys and values have to be interpreted (<a>array</a> of <a>term definitions</a>),</li>
+        keys and values have to be interpreted (<a class="change">map</a> of <a>term definitions</a>),</li>
       <li>the current <dfn data-lt="context-base-iri" data-lt-noDefault>base IRI</dfn> (<a>IRI</a>),</li>
       <li class="changed">the <dfn>original base URL</dfn> (<a>IRI</a>),</li>
       <li class="changed">an <dfn data-lt="context-inverse" data-lt-noDefault>inverse context</dfn> (<a>inverse context</a>),</li>
@@ -1085,7 +1085,7 @@ <h2>RDF Serialization/Deserialization</h2>
         used when a non-propagated <a>context</a> is defined.</li>
     </ul>
 
-    <p>Each <a>term definition</a> consists of:</p>
+    <p>Each <a>term definition</a><span class="change">'s value</span> consists of:</p>
     <ul>
       <li>an <dfn>IRI mapping</dfn> (<a>IRI</a>),</li>
       <li class="changed">a <dfn>prefix flag</dfn> (<a>boolean</a>),</li>