Fix PDF build errors

1 files changed, 12 insertions, 9 deletions

diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
index bf02a3bb3..5187a6a45 100644
--- a/en/appendix/preseed.xml
+++ b/en/appendix/preseed.xml
@@ -160,8 +160,6 @@ use the same template.
 
 The following types of templates are relevant for preseeding.
 
-</para>
-
 <itemizedlist>
 <listitem><para>
   string: allows the user to type any value
@@ -183,7 +181,7 @@ The following types of templates are relevant for preseeding.
 </para></listitem>
 </itemizedlist>
 
-<para>
+</para><para>
 
 In &d-i; templates are stored in a readable file
 <filename>/var/cache/debconf/templates.dat</filename>. This file contains all fixed
@@ -422,27 +420,32 @@ a line in a preconfiguration file is:
 
 There are a few rules to keep in mind when writing a preconfiguration file.
 
+</para>
+
 <itemizedlist>
-<listitem>
+<listitem><para>
   Put only a single space or tab between type and value: any additional
   whitespace will be interpreted as belonging to the value.
-</listitem><listitem>
+</para></listitem>
+<listitem><para>
   A line can be split into multiple lines by appending a backslash
   (<quote><literal>\</literal></quote>) as the line continuation character.
   A good place to split a line is after the template name; a bad place is
   between type and value.
-</listitem><listitem>
+</para></listitem>
+<listitem><para>
   Most templates need to be preseeded using the values valid in English and
   not the translated values. However, there are some templates (for example
   in <classname>partman</classname> where the translated values need to be
   used.
-</listitem><listitem>
+</para></listitem>
+<listitem><para>
   Some templates take a code as value instead of the English text that is
   shown during installation.
-</listitem>
+</para></listitem>
 </itemizedlist>
 
-</para><para>
+<para>
 
 The easiest way to create a preconfiguration file is to use the example file
 linked in <xref linkend="preseed-contents"/> as basis and work from there.