diff --git a/htdocs/ACIP_To_Tibetan_Converter.html b/htdocs/ACIP_To_Tibetan_Converter.html
index c827c21..d0c47f5 100644
--- a/htdocs/ACIP_To_Tibetan_Converter.html
+++ b/htdocs/ACIP_To_Tibetan_Converter.html
@@ -101,9 +101,9 @@
   <li>
     Some transliterations specified by the ACIP standard are not
     accepted (i.e., they cause <a href="#diagnostics">errors</a>)
-    because they are used too often improperly in Release IV texts
+    because they are used too often improperly in Release V texts
     (e.g., {\}); some non-standard transliteration is understood
-    because it is used in ACIP Release IV texts (e.g., {[DD1]}).
+    because it is used in ACIP Release V texts (e.g., {[DD1]}).
   </li>
   <li>
     Non-standard <a href="#escapes">Unicode character escapes</a> are
@@ -126,7 +126,7 @@
   <li>
     The <a href="#lex">&quot;lexical analyzer&quot;</a> and <a
     href="#parse">&quot;parser&quot;</a> handle every intricacy of
-    real ACIP Release IV texts.
+    real ACIP Release V texts.
   </li>
   <li>
     The knowledge regarding the TMW font has been verified by
@@ -636,7 +636,7 @@
   Now that the basic operation is clear from the above example, let's
   cover the fine points of how standard ACIP is handled.&nbsp; We'll
   also cover some non-standard constructs that appear commonly in
-  actual ACIP Release IV texts.
+  actual ACIP Release V texts.
 </p>
 
 <p>
@@ -771,7 +771,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"
 
 <p>
   The converter also supports several non-standard folio
-  markers.&nbsp; A review of ACIP Release IV texts determined that the
+  markers.&nbsp; A review of ACIP Release V texts determined that the
   following types of folio markers can appear:
 </p>
 
@@ -789,7 +789,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"
 </pre>
 
 <p>
-  Similarly, to support real ACIP Release IV texts, the converter
+  Similarly, to support real ACIP Release V texts, the converter
   treats {[DD1]}, {[DD2]}, {[ DD ]}, and {[DDD]} just like {[DD]}
   (which is specified in the ACIP standard).&nbsp; It treats {[ BP ]}
   and {[BLANK PAGE]} just like {[BP]}, also.
@@ -797,7 +797,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"
 
 <p>
   The lists above were created by a most fallible process of reviewing
-  a large number of ACIP Release IV texts.&nbsp; Your suggestions for
+  a large number of ACIP Release V texts.&nbsp; Your suggestions for
   additions to these lists are highly valued; please contact <a
   href="mailto:thdltools-devel@lists.sourceforge.net">the
   developers</a>.
@@ -866,7 +866,7 @@ GA
 
 <p>
   Though the ACIP standard does not mention it, it appears that some
-  ACIP Release IV texts use a period (i.e., {.}) to indicate a
+  ACIP Release V texts use a period (i.e., {.}) to indicate a
   non-breaking tsheg (i.e., U+0F0C).&nbsp; Search for {NGO.,},
   {....,DAM}, etc.&nbsp; Unless {,}, {.}, or a letter (i.e., a through
   z) follows the {.}, it is only grudingly interpreted as a
@@ -1472,7 +1472,7 @@ Nativeness</h2>
     href="http://sourceforge.net/tracker/index.php?func=detail&aid=855519&group_id=61934&atid=502515">855519</a>]
   </li>
   <li>
-    A folio marker {@0B1} can appear; it gives an error at present.
+    A folio marker {@0B1} can appear in ACIP Release V texts; it gives an error at present.
   </li>
   <li>
     The treatment of the very last line in an input text may be buggy
@@ -1483,6 +1483,12 @@ Nativeness</h2>
     incorrect; a <i>tsheg</i> is inserted right now after the
     visarga.<!-- DLC FIXME -->
   </li>
+  <li>
+    The ACIP {?} is treated questionably as being equivalent to
+    {\u003F}.&nbsp; This may indicated U+0F08; until the confusion is
+    resolved, this should cause an error.&nbsp; [<a
+    href="http://sourceforge.net/tracker/index.php?func=detail&aid=860192&group_id=61934&atid=502515">860192</a>]
+  </li>
 </ul>
 
 
@@ -1574,8 +1580,7 @@ Nativeness</h2>
   </li>
   <li>
     Default <a href="#sub">substitution</a> rules should handle
-    {KAsh}, which seems to always mean {K+sh} in ACIP Release IV
-    texts.
+    {KAsh}, which seems to always mean {K+sh} in ACIP Release V texts.
   </li>
 </ul>