DocBook validation correction

adding a few </sect2> </listitem> and </para> closing tags to allow for
validation

LDP/howto/docbook/Debian-Jigdo.sgml

@@ -206,8 +206,8 @@
       were two ways of creating Debian CDs:</para>
 
 			<orderedlist>
-			<listitem><para>Downloading the entire ISO</para>
-			<listitem><para>Using the pseudo-image kit (PIK)</para>
+			<listitem><para>Downloading the entire ISO</para></listitem>
+			<listitem><para>Using the pseudo-image kit (PIK)</para></listitem>
 			</orderedlist>
 
       <para>This document is about the newer and better way of obtaining Debian ISO images, using a
@@ -1030,6 +1030,7 @@
       url="http://www.daemon-tools.cc">Daemon tools</ulink></application> and <application>Nero
       Image Drive</application> are both very popular.  See also <ulink
       url="http://tinyurl.com/c39zr">http://tinyurl.com/c39zr</ulink> for more options.</para>
+      </listitem>
 
 
       </itemizedlist>
@@ -1219,13 +1220,13 @@
 
       <para>You might find that under MS Windows, jigdo-lite will download some files but then fail
       to read their contents, which will produce a "<literal>No such file or directory</literal>"
-      error message.
+      error message.</para>
 
       <para>It seems that this occurs if the length of the filenames that jigdo processes exceeds a
       certain limit. The solution is to move the half-finished download up in the directory
       hierarchy, closer to the top-level directory of the drive.</para>
 
-
+        </sect2>
 
     <sect2><title>On MS Windows, why won't my image grow larger than 2GB?</title>
 
@@ -1297,7 +1298,7 @@
     <sect2 id="more-about-scan"><title>More About Scan Sources</title>
 
       <para>By now you know that when <application>jigdo-lite</application> asks for files to scan,
-      you can use 3 sources:
+      you can use 3 sources:</para>
 
 
       <itemizedlist mark='bullet'>