From 55ed5114695e364290eb402a39e26108fc64f64c Mon Sep 17 00:00:00 2001
From: "@aphillips" <addison@lab126.com>
Date: Mon, 16 Jul 2018 13:30:43 -0700
Subject: [PATCH] Addressed #163 (typo)

---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 59aa236..d5fa18d 100644
--- a/index.html
+++ b/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-07-15",
+          publishDate:  			"2018-07-16",
           previousPublishDate:  	"2015-11-19",
           previousMaturity:  		"WD",
 
@@ -731,7 +731,7 @@ <h3>Unicode Normalization</h3>
         <section id="canonical_compatibility">
           <h4>Canonical vs. Compatibility Equivalence</h4>
           <p>Unicode defines two types of equivalence between characters: <em>canonical equivalence</em> and <em>compatibility equivalence</em>.</p>
-          <p><dfn>Canonical equivalence</dfn> is a fundamental equivalency between Unicode characters or sequences of Unicode characters that represent the same abstract character. Equivaent sequences, ideally should have the same visual appearance (although there are many factors that can cause them to appear somewhat differently) and they should be treated and processed equivalently. Generally speaking, two canonically equivalent Unicode texts should be considered to be identical as text. Unicode defines a process called <em>canonical decomposition</em> that removes these primary distinctions between two differently-encoded but canonically equivalent texts.</p>
+          <p><dfn>Canonical equivalence</dfn> is a fundamental equivalency between Unicode characters or sequences of Unicode characters that represent the same abstract character. Equivalent sequences ideally should have the same visual appearance (although there are many factors that can cause them to appear somewhat differently) and they should be treated and processed equivalently. Generally speaking, two canonically equivalent Unicode texts should be considered to be identical as text. Unicode defines a process called <em>canonical decomposition</em> that removes these primary distinctions between two differently-encoded but canonically equivalent texts.</p>
           <p>Examples of canonical equivalence defined by Unicode include:</p>
           <ul class="dropExampleList">
             <li class="dropExampleItem"><span class="dropExample">Ç<span style="font-size:75%">