Define and use the term _embedded context_ to describe the context contained within a term definition.

Author: gkellogg

spec/latest/json-ld/index.html

@@ -2405,7 +2405,7 @@ <h2>Reverse Properties</h2>
   <h2>Scoped Contexts</h2>
 
   <p>An <a>expanded term definition</a> can include a <code>@context</code>
-    property, which defines a <a>context</a> for <a data-lt="JSON-LD
+    property, which defines a <a>context</a> (an <dfn>embedded context</dfn>) for <a data-lt="JSON-LD
     value">values</a> of properties defined using that <a>term</a>. This allows
     values to use <a>term definitions</a>, <a>base IRI</a>,
     <a>vocabulary mapping</a> or <a>default language</a> which is different from the
@@ -2436,7 +2436,7 @@ <h2>Scoped Contexts</h2>
 
   <p>In this case, the social profile is defined using the schema.org vocabulary, but interest is imported from FOAF, and is used to define a node describing one of Manu's interests where those properties now come from the FOAF vocabulary.</p>
 
-  <p>Expanding this document, uses a combination of terms defined in the outer context, and those defined specifically for that term.</p>
+  <p>Expanding this document, uses a combination of terms defined in the outer context, and those defined specifically for that term in an <a>embedded context</a>.</p>
 
   <pre class="example nohighlight" data-transform="updateExample"
        title="Expanded document using a scoped context">
@@ -2482,15 +2482,15 @@ <h2>Scoped Contexts</h2>
   <p>Scoping on <code>@type</code> is useful when common properties are used to
     relate things of different types, where the vocabularies in use within
     different entities calls for different context scoping. For example,
-    `hasPart`/`partOf` may be common terms used in a document, but mean
+    <code>hasPart</code>/<code>partOf</code> may be common terms used in a document, but mean
     different things depending on the context.</p>
 
   <p>When expanding, each value of <code>@type</code> is considered
     (ordering them lexographically) where that value is also a <a>term</a> in
-    the <a>active context</a> having its own <a>context</a>. If so, that
-    <a>context</a> as applied to the <a>active context</a>. When compacting, if
+    the <a>active context</a> having its own <a>embedded context</a>. If so, that
+    <a>embedded context</a> is applied to the <a>active context</a>. When compacting, if
     a <a>term</a> is chosen to represent an IRI used as a value of <code>@type</code> where that
-    <a>term definition</a> also has a <a>context</a>, it is then applied to the
+    <a>term definition</a> also has an <a>embedded context</a>, it is then applied to the
     <a>active context</a> to affect further compaction.</p>
 
   <p class="note">The values of <code>@type</code> are unordered, so if multiple