Fix caption

Captions should be inside mediaobject

input/chapter00/chapter00.xml

@@ -326,20 +326,20 @@
           by device drivers with a file interface provided to a
           user.</phrase>
         </textobject>
+	<caption>
+          <para>File descriptors are an index into a file descriptor
+          table stored by the kernel.  The kernel creates a file
+          descriptor in response to an
+          <computeroutput>open</computeroutput> call and associates the
+          file descriptor with some abstraction of an underlying
+          file-like object, be that an actual hardware device, or a
+          file system or something else entirely.  Consequently a
+          process's <computeroutput>read</computeroutput> or
+          <computeroutput>write</computeroutput> calls that reference
+          that file descriptor are routed to the correct place by the
+          kernel to ultimately do something useful.</para>
+	</caption>
       </mediaobject>
-      <caption>
-        <para>File descriptors are an index into a file descriptor
-        table stored by the kernel.  The kernel creates a file
-        descriptor in response to an
-        <computeroutput>open</computeroutput> call and associates the
-        file descriptor with some abstraction of an underlying
-        file-like object, be that an actual hardware device, or a
-        file system or something else entirely.  Consequently a
-        process's <computeroutput>read</computeroutput> or
-        <computeroutput>write</computeroutput> calls that reference
-        that file descriptor are routed to the correct place by the
-        kernel to ultimately do something useful.</para>
-      </caption>
     </figure>
     <para>In short, the file descriptor is the gateway into the
     kernel's abstractions of underlying hardware.  An overall view of
@@ -531,15 +531,15 @@
 	  kernel which allows the output of one process to be consumed
 	  as the input to another.</phrase>
             </textobject>
+            <caption>
+              <para>The pipe is an in-memory buffer that connects two
+              processes together.  file descriptors point to the pipe
+              object, which buffers data sent to it (via a
+              <computeroutput>write</computeroutput>) to be
+              <emphasis>drained</emphasis> (via a
+              <computeroutput>read</computeroutput>).</para>
+            </caption>
           </mediaobject>
-          <caption>
-            <para>The pipe is an in-memory buffer that connects two
-            processes together.  file descriptors point to the pipe
-            object, which buffers data sent to it (via a
-            <computeroutput>write</computeroutput>) to be
-            <emphasis>drained</emphasis> (via a
-            <computeroutput>read</computeroutput>).</para>
-          </caption>
         </figure>
         <para>Writes to the pipe are stored by the kernel until a
         corresponding read from the other side

input/chapter02/chapter02.xml

@@ -145,11 +145,11 @@
             <imageobject role="html">
               <imagedata fileref="chapter02/figures/block.png" format="PNG"/>
             </imageobject>
+            <caption>
+              <para>The CPU is made up of many different
+	      sub-components, each doing a dedicated task.</para>
+            </caption>
           </mediaobject>
-          <caption>
-            <para>The CPU is made up of many different
-	  sub-components, each doing a dedicated task.</para>
-          </caption>
         </figure>
         <para><xref linkend="inside_the_cpu"/> shows a very
 	      simple block diagram illustrating some of the main parts
@@ -536,12 +536,12 @@
           <imageobject role="html">
             <imagedata fileref="chapter02/figures/sets.png" format="PNG"/>
           </imageobject>
-        </mediaobject>
-        <caption>
-          <para>
-	    A given cache line may find a valid home in one
+          <caption>
+            <para>
+	      A given cache line may find a valid home in one
 	    of the shaded entries.</para>
-        </caption>
+          </caption>
+        </mediaobject>
       </figure>
       <para>During normal operation the processor is constantly
 	      asking the cache to check if a particular address is
@@ -763,15 +763,15 @@ multiplex the output of the many sets, which can also add latency.
             <imageobject role="html">
               <imagedata fileref="chapter02/figures/interrupt.png" format="PNG"/>
             </imageobject>
+            <caption>
+              <para>A generic overview of handling an interrupt.  The
+	      device raises the interrupt to the interrupt controller,
+	      which passes the information onto the processor.  The
+	      processor looks at its descriptor table, filled out by the
+	      operating system, to find the code to handle the
+	      fault.</para>
+            </caption>
           </mediaobject>
-          <caption>
-            <para>A generic overview of handling an interrupt.  The
-	    device raises the interrupt to the interrupt controller,
-	    which passes the information onto the processor.  The
-	    processor looks at its descriptor table, filled out by the
-	    operating system, to find the code to handle the
-	    fault.</para>
-          </caption>
         </figure>
         <para>Most drivers will split up handling of interrupts into
 	<emphasis>bottom</emphasis> and <emphasis>top</emphasis>