Merge pull request w3c#1555 from w3c/add-rfc2119-keywords

add missing rfc-2119 keyowrds

Author: sebastiankb

index.html

@@ -6454,7 +6454,7 @@ <h3>Composition</h3>
     A single TD can also be generated which contains the interaction definitions of the top level/parent
     <a>Thing Model</a> and all interaction definitions of all sub/child <a>Thing Models</a>. 
     <span class="rfc2119-assertion" id="tm-compose-name-collision">
-       To avoid name collisions of the sub/child interaction names it is recommended to rename the JSON name to the <code>instanceName</code> followed with <code>'_'</code> and the interaction name of the sub/child <a>Thing Model</a>.
+       To avoid name collisions of the sub/child interaction names SHOULD rename the JSON name to the <code>instanceName</code> followed with <code>'_'</code> and the interaction name of the sub/child <a>Thing Model</a>.
     </span> 
     The following example shows a generated (self-contained) <a>Thing Description</a> of the Smart Ventilator Thing Model.
 </p>
@@ -6808,7 +6808,7 @@ <h2>Derivation of Thing Description Instances</h2>
          <p>Please note that a TD can only be an instance of one TM at a time. 
              That means for Thing Descriptions:
          <span class="rfc2119-assertion" id="tm-rel-type-maximum">
-            The <code>links</code> array can use the entry with <code>"rel" : "type"</code> a maximum of once.</span> 
+            The <code>links</code> array MUST use the entry with <code>"rel" : "type"</code> a maximum of once.</span> 
         If it is desired to reflect all relationships to other Things in a Thing Description, the composition mechanism in TMs can be considered (see Section <a href="#thing-model-composition"></a>). 
     </p>
 

index.template.html

@@ -5184,7 +5184,7 @@ <h3>Composition</h3>
     A single TD can also be generated which contains the interaction definitions of the top level/parent
     <a>Thing Model</a> and all interaction definitions of all sub/child <a>Thing Models</a>. 
     <span class="rfc2119-assertion" id="tm-compose-name-collision">
-       To avoid name collisions of the sub/child interaction names it is recommended to rename the JSON name to the <code>instanceName</code> followed with <code>'_'</code> and the interaction name of the sub/child <a>Thing Model</a>.
+       To avoid name collisions of the sub/child interaction names SHOULD rename the JSON name to the <code>instanceName</code> followed with <code>'_'</code> and the interaction name of the sub/child <a>Thing Model</a>.
     </span> 
     The following example shows a generated (self-contained) <a>Thing Description</a> of the Smart Ventilator Thing Model.
 </p>
@@ -5538,7 +5538,7 @@ <h2>Derivation of Thing Description Instances</h2>
          <p>Please note that a TD can only be an instance of one TM at a time. 
              That means for Thing Descriptions:
          <span class="rfc2119-assertion" id="tm-rel-type-maximum">
-            The <code>links</code> array can use the entry with <code>"rel" : "type"</code> a maximum of once.</span> 
+            The <code>links</code> array MUST use the entry with <code>"rel" : "type"</code> a maximum of once.</span> 
         If it is desired to reflect all relationships to other Things in a Thing Description, the composition mechanism in TMs can be considered (see Section <a href="#thing-model-composition"></a>). 
     </p>