Move note on type coercion as distinct from specifying the type of a node.

Author: gkellogg

index.html

@@ -1548,11 +1548,6 @@ <h2>Specifying the Type</h2>
   <p class="changed">Typed values can also be defined implicitly, by specifying
     <code>@type</code> in an expanded term definition.
     This is covered more fully in <a class="sectionRef" href="#type-coercion"></a>.</p>
-
-  <p class="note">The ability coerce a value using a <a>term definition</a> is distinct
-    from setting one or more types on a <a>node object</a>, as the former does not result in
-    new data being added to the graph, while the later manages node types
-    through adding additional relationships to the graph.</p>
 </section>
 </section>
 
@@ -3692,6 +3687,11 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
   <a>compact IRI</a> or <a>absolute IRI</a> if a colon is present; otherwise, they are interpreted
   as <a>relative IRI</a>.</p>
 
+<p class="note">The ability coerce a value using a <a>term definition</a> is distinct
+  from setting one or more types on a <a>node object</a>, as the former does not result in
+  new data being added to the graph, while the later manages node types
+  through adding additional relationships to the graph.</p>
+
 <p><a>Terms</a> or <a>compact IRIs</a> used as the value of a
   <code>@type</code> key may be defined within the same context. This means that one may specify a
   <a>term</a> like <code>xsd</code> and then use <code>xsd:integer</code> within the same