Adjusted fallback order of large example text to use NoToFu font first.

Addressed #190

index.html

@@ -11,7 +11,7 @@
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
           specStatus:				"ED",
-          publishDate:  			"2018-09-25",
+          publishDate:  			"2019-01-19",
           previousPublishDate:  	"2015-11-19",
           previousMaturity:  		"WD",
 
@@ -26,7 +26,7 @@
           // only "name" is required
           editors:  [
               { name: "Addison Phillips", 
-                company: "Invited Expert",
+                company: "Amazon.com",
 				w3cid: 33573 },
           ],
 
@@ -927,26 +927,9 @@ <h4>Canonical vs. Compatibility Equivalence</h4>
         </section>
         <section id="composition_decomposition">
           <h4>Composition vs. Decomposition</h4>
-          <p>These two types of Unicode-defined equivalence are then grouped by
-            another pair of variations: "decomposition" and "composition". In
-            "decomposition", separable logical parts of a visual character are
-            broken out into a sequence of base characters and combining marks
-            and the resulting code points are put into a fixed, canonical order.
-            In "composition", the decomposition is performed and then any
-            combining marks are recombined, if possible, with their base
-            characters. Note that this does <strong>not</strong> mean that all
-            of the combining marks have been removed from the resulting
-            normalized text. </p>
+          <p>These two types of Unicode-defined equivalence are then grouped by another pair of variations: "decomposition" and "composition". In "decomposition", separable logical parts of a visual character are broken out into a sequence of base characters and combining marks and the resulting code points are put into a fixed, canonical order. In "composition", the decomposition is performed and then combining marks are recombined to the extent possible with their base characters. Note that this does <strong>not</strong> mean that all of the combining marks have been removed from the resulting normalized text. </p>
           <div class="note">
-            <p>Roughly speaking, <abbr title="Normalization Form C">NFC</abbr>
-              is defined such that each combining character sequence (a base
-              character followed by one or more combining characters) is
-              replaced, as far as possible, by a canonically equivalent
-              precomposed character. Text in a Unicode character encoding form
-              (such as UTF-8 or UTF-16) is said to be in NFC if it doesn't
-              contain any combining sequence that could be replaced with a
-              precomposed character and if any remaining combining sequence is
-              in canonical order.</p>
+            <p>Roughly speaking, <abbr title="Normalization Form C">NFC</abbr> is defined such that each combining character sequence (a base character followed by one or more combining characters) is replaced, as far as possible, by a canonically equivalent precomposed character.</p>
             <p>Users are cautioned that the resulting character sequence can still contain combining marks: not all character sequences have a precomposed equivalent and some scripts depend on combining marks for encoding. There are even cases where a given base character and combining mark is not replaced with a precomposed character because the combination is "blocked" by another combining mark in the sequence. </p>
           </div>
         </section>

local.css

@@ -207,7 +207,7 @@ div.exampleBox {
 
 .exampleChar {
     font-size: 36pt;
-    font-family: "Palatino", "Times", "Times New Roman", "Verdana", "NoToFu", serif;
+    font-family: "NoToFu", "Palatino", "Times", "Times New Roman", "Verdana", serif;
 }
 
 .bidiExample {