Split example 46 into separate examples.

Fixes #241.

Author: gkellogg

Gemfile.lock

@@ -1,6 +1,6 @@
 GIT
   remote: https://github.com/ruby-rdf/json-ld.git
-  revision: 172e0c960c9771fa9f963eca55d28fb63bce56b0
+  revision: adbd407fa4b5783c8a7f7b79653b6e38815ff854
   branch: develop
   specs:
     json-ld (3.0.2)
@@ -14,8 +14,8 @@ GIT
 GEM
   remote: https://rubygems.org/
   specs:
-    addressable (2.6.0)
-      public_suffix (>= 2.0.2, < 4.0)
+    addressable (2.7.0)
+      public_suffix (>= 2.0.2, < 5.0)
     bcp47 (0.3.3)
       i18n
     builder (3.2.3)
@@ -28,7 +28,7 @@ GEM
       sxp (~> 1.0)
     equivalent-xml (0.6.0)
       nokogiri (>= 1.4.3)
-    haml (5.1.1)
+    haml (5.1.2)
       temple (>= 0.8.0)
       tilt
     hamster (3.0.0)
@@ -37,7 +37,7 @@ GEM
     i18n (1.6.0)
       concurrent-ruby (~> 1.0)
     json-canonicalization (0.1.0)
-    json-ld-preloaded (3.0.3)
+    json-ld-preloaded (3.0.4)
       json-ld (~> 3.0)
       multi_json (~> 1.12)
       rdf (~> 3.0)
@@ -77,11 +77,11 @@ GEM
     multi_json (1.13.1)
     net-http-persistent (3.1.0)
       connection_pool (~> 2.2)
-    nokogiri (1.10.3)
+    nokogiri (1.10.4)
       mini_portile2 (~> 2.4.0)
     nokogumbo (1.5.0)
       nokogiri
-    public_suffix (3.1.1)
+    public_suffix (4.0.1)
     rack (2.0.7)
     rake (12.3.3)
     rdf (3.0.12)
@@ -135,7 +135,7 @@ GEM
     rdf-turtle (3.0.6)
       ebnf (~> 1.1)
       rdf (~> 3.0)
-    rdf-vocab (3.0.8)
+    rdf-vocab (3.0.10)
       rdf (~> 3.0, >= 3.0.11)
     rdf-xsd (3.0.1)
       rdf (~> 3.0)
@@ -160,8 +160,8 @@ GEM
       rdf (~> 3.0)
     sxp (1.0.2)
       rdf (~> 3.0)
-    temple (0.8.1)
-    tilt (2.0.9)
+    temple (0.8.2)
+    tilt (2.0.10)
 
 PLATFORMS
   ruby

index.html

@@ -3441,90 +3441,91 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     types are listed, the order that <a>type-scoped contexts</a> are applied is based on
     lexicographical ordering.</p>
 
-  <p>For example, consider the following semantically equivalent examples:</p>
+  <p>For example, consider the following semantically equivalent examples.
+    The first example, shows how properties and types can define their own
+    scoped contexts, which are included when expanding.</p>
 
-  <aside class="example" title="Expansion using embedded and scoped contexts">
-    <p>This example, shows how properties and types can define their own
-      scoped contexts, which are included when expanding.</p>
-    <pre data-transform="updateExample">
-    <!--
-    {
-      "@context": {
-        "@vocab": "http://example.com/vocab/"
-        "property": {
-          "@id": "http://example.com/vocab/property",
-          "@context": {
-            "term1": "http://example.com/vocab/term1"
-            #### ↑ Scoped context for "property" defines term1
-          },
-        },
-        "Type1": {
-          "@id": "http://example.com/vocab/Type1",
-          "@context": {
-            "term3": "http://example.com/vocab/term3"
-            #### ↑ Scoped context for "Type1" defines term3
-          },
-        },
-        "Type2": {
-          "@id": "http://example.com/vocab/Type2",
-          "@context": {
-            "term4": "http://example.com/vocab/term4"
-            #### ↑ Scoped context for "Type2" defines term4
-          },
-        },
-      },
+  <pre class="example" title="Expansion using embedded and scoped contexts" data-transform="updateExample">
+  <!--
+  {
+    "@context": {
+      "@version": 1.1,
+      "@vocab": "http://example.com/vocab/",
       "property": {
+        "@id": "http://example.com/vocab/property",
         "@context": {
-          "term2": "http://example.com/vocab/term2"
-            #### ↑ Embedded context defines term2
-        },
-        "@type": ["Type2", "Type1"],
-        "term1": "a",
-        "term2": "b",
-        "term3": "c",
-        "term4": "d",
-      }
-    }
-    -->
-    </pre>
-
-    <p>Contexts are processed depending on how they are defined. A <a>property-scoped context</a>
-      is processed first, followed by any <a>embedded context</a>,
-      followed lastly by the <a>type-scoped contexts</a>, in the appropriate order.
-      The previous example is logically equivalent to the following:</p>
-    <pre data-transform="updateExample">
-    <!--
-    {
-      "@context": {
-        "@vocab": "http://example.com/vocab/"
-        "property": "http://example.com/vocab/property",
-        "Type1": "http://example.com/vocab/Type1",
-        "Type2": "http://example.com/vocab/Type2",
+          "term1": "http://example.com/vocab/term1"
+          #### ↑ Scoped context for "property" defines term1####
+        }
       },
-      "property": {
-        "@context": [{
-            "term1": "http://example.com/vocab/term1"
-            #### ↑ Scoped context for "property" defines term1
-          }, {
-            "term2": "http://example.com/vocab/term2"
-            #### ↑ Embedded context defines term2
-          }, {
-            "term3": "http://example.com/vocab/term3"
-            #### ↑ Scoped context for "Type1" defines term3
-          }, {
+      "Type1": {
+        "@id": "http://example.com/vocab/Type1",
+        "@context": {
+          "term3": "http://example.com/vocab/term3"
+          #### ↑ Scoped context for "Type1" defines term3####
+        }
+      },
+      "Type2": {
+        "@id": "http://example.com/vocab/Type2",
+        "@context": {
           "term4": "http://example.com/vocab/term4"
-            #### ↑ Scoped context for "Type2" defines term4
-        }],
-        "@type": ["Type2", "Type1"],
-        "term1": "a",
-        "term2": "b",
-        "term3": "c",
-        "term4": "d",
+          #### ↑ Scoped context for "Type2" defines term4####
+        }
       }
+    },
+    "property": {
+      "@context": {
+        "term2": "http://example.com/vocab/term2"
+          #### ↑ Embedded context defines term2####
+      },
+      "@type": ["Type2", "Type1"],
+      "term1": "a",
+      "term2": "b",
+      "term3": "c",
+      "term4": "d"
     }
-    -->
-    </pre>
-  </aside>
+  }
+  -->
+  </pre>
+
+  <p>Contexts are processed depending on how they are defined.
+    A <a>property-scoped context</a> is processed first,
+    followed by any <a>embedded context</a>,
+    followed lastly by the <a>type-scoped contexts</a>,
+    in the appropriate order. The previous example is logically equivalent to the following:</p>
+
+  <pre class="example" title="Expansion using embedded and scoped contexts (embedding equivalent)" data-transform="updateExample">
+  <!--
+  {
+    "@context": {
+      "@vocab": "http://example.com/vocab/",
+      "property": "http://example.com/vocab/property",
+      "Type1": "http://example.com/vocab/Type1",
+      "Type2": "http://example.com/vocab/Type2"
+    },
+    "property": {
+      "@context": [{
+          "term1": "http://example.com/vocab/term1"
+          #### ↑ Previously scoped context for "property" defines term1####
+        }, {
+          "term2": "http://example.com/vocab/term2"
+          #### ↑ Embedded context defines term2####
+        }, {
+          "term3": "http://example.com/vocab/term3"
+          #### ↑ Previously scoped context for "Type1" defines term3####
+        }, {
+        "term4": "http://example.com/vocab/term4"
+          #### ↑ Previously scoped context for "Type2" defines term4####
+      }],
+      "@type": ["Type2", "Type1"],
+      "term1": "a",
+      "term2": "b",
+      "term3": "c",
+      "term4": "d"
+    }
+  }
+  -->
+  </pre>
 
   <p class="note">If a <a>term</a> defines a <a>scoped context</a>,
     and then that term is later re-defined,