Allow underscores in debconf template names

[debian/debian-policy.git] / debconf_spec / debconf_specification.xml

diff --git a/debconf_spec/debconf_specification.xml b/debconf_spec/debconf_specification.xml
index ff762324aab578f7b86076c1ec748f12f227d0b9..ef8da7d7adfb7b342181126b5f7b847b8894babf 100644 (file)
--- a/debconf_spec/debconf_specification.xml
+++ b/debconf_spec/debconf_specification.xml
@@ -139,8 +139,8 @@
        So, what do we need to store in a variable template? Of course we
        need a name to identify the template. Template names are made up of
        components separated by the character `/' (slash).
-       Each component is limited to alphanumerics and `+' `-' `.'
-       (plus, minus, full stop).
+       Each component is limited to alphanumerics and `+' `-' `.' `_'
+       (plus, minus, full stop, underscore).
       </para>
       <para>
         A type is also needed so data can be verified. Here is a table
@@ -186,7 +186,7 @@ Description: domain for this computer
        For localization, the description field (and also the choices
        field of a select or multiselect type question, and the
        default field of a string or password type question) can be
-       supplimented with versions for other languages. These are
+       supplemented with versions for other languages. These are
        named <emphasis>Description-ll</emphasis>,
        <emphasis>Description-ll_LL</emphasis>,
        <emphasis>Description-ll_LL.encoding</emphasis> and so on.
@@ -280,7 +280,7 @@ Description: domain for this computer
       usually run <emphasis>before</emphasis> the preinst, and before
       the package is unpacked!
       <note>
-       <simpara>Plese see debconf-devel(8) for details.</simpara>
+       <simpara>Please see debconf-devel(7) for details.</simpara>
       </note>
       This is done to make sure that we can
       use the desired configuration in the preinst if necessary.