From 48ce19c111ba54b0c9ddacf097cd28a8bd1ef5f8 Mon Sep 17 00:00:00 2001
From: deyan <deyan.ginev@gmail.com>
Date: Wed, 23 Oct 2024 10:19:55 -0400
Subject: [PATCH] reuse unknown concept definition in concept list-matching
 explanation

---
 src/intent.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/intent.html b/src/intent.html
index 26a7369..0858406 100644
--- a/src/intent.html
+++ b/src/intent.html
@@ -92,7 +92,8 @@ <h3 id="mixing_intent_grammar">The Grammar for <code class="attribue">intent</co
       This may produce specific audio or braille renderings based on the speech hints
       given in the list.
       An <dfn id="intent_unknown_concept">unknown concept</dfn> is a concept not
-      currently known to the AT. These will be treated the same as a [=literal=], spoken as-is.
+      currently known to the AT. These will be treated the same as a [=literal=], spoken as-is
+      after normalizing each of `-`, `_` and `.` to an inter-word space.
       However, future updates of the AT and [=Intent Concept Dictionary=] may
       include additional concepts, at which time those concepts may also receive special treatment.</p>
     </li>
@@ -252,10 +253,9 @@ <h3 id="mixing_intent_dictionaries">Intent Concept Dictionaries</h3>
      If a match is found, the speech hint in the list
      should be used be used as a guide for the generation of suitable text
      for the <a href="#intent_known_concept">known concept</a>.
-     If the intent does not match any entries, then it is treated as
-     Unknown concept names should be read as a literal after normalizing each of `-`, `_` and `.`
-     to an inter-word space.
-    Both <a href="#intent_known_concept">known concepts</a> and
+     Recall that any concept not currently known to the AT is an <a href="#intent_unknown_concept">unknown concept</a> 
+     and treated as a <a href="#intent_literal">literal</a>.
+     Both <a href="#intent_known_concept">known concepts</a> and
     <a href="#intent_unknown_concept">unknown concepts</a> should be read in a manner
     consistent with any given or default fixity properties.
   </p>