From cab218977c6ce127abb930f26a91aca786c03b23 Mon Sep 17 00:00:00 2001
From: Warren Block <wblock@FreeBSD.org>
Date: Thu, 14 Jun 2012 12:04:00 +0000
Subject: [PATCH] Whitespace-only fixes: indentation and wrap long lines. 
 Translators, please ignore.

---
 .../handbook/advanced-networking/chapter.sgml | 104 +++++++++---------
 1 file changed, 53 insertions(+), 51 deletions(-)

diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
index 803f97f6da..c88959f570 100644
--- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
@@ -4635,62 +4635,64 @@ myhost.example.com:/b/tftpboot/FreeBSD/install       /         nfs      ro
 	</step>
 
 	<step>
-	  <para>Use the <filename role="package">net/wireshark</filename>
-	    port to debug the network traffic involved during the
+
+	  <para>Use the
+	    <filename role="package">net/wireshark</filename> port to
+	    debug the network traffic involved during the
 	    <acronym>PXE</acronym> booting process, which is
-	    illustrated in the diagram below.
-	    In <xref linkend="network-pxe-setting-up-dhcp">, an
-	    example configuration is shown where the
-	    <acronym>DHCP</acronym>, <acronym>TFTP</acronym>, and
-	    <acronym>NFS</acronym> servers are actually on the same
-	    machine.  However, these severs can be on separate
-	    machines.</para>
+	    illustrated in the diagram below.  In
+	    <xref linkend="network-pxe-setting-up-dhcp">, an example
+	    configuration is shown where the <acronym>DHCP</acronym>,
+	    <acronym>TFTP</acronym>, and <acronym>NFS</acronym>
+	    servers are actually on the same machine.  However, these
+	    severs can be on separate machines.</para>
 
 	  <figure>
 	    <title>PXE Booting process with NFS root mount</title>
+
 	    <mediaobjectco>
-		<imageobjectco>
-		  <areaspec units="calspair">
-		    <area id="co-pxenfs1" coords="2873,8133 3313,7266">
-		    <area id="co-pxenfs2" coords="3519,6333 3885,5500">
-		    <area id="co-pxenfs3" coords="4780,5866 5102,5200">
-		    <area id="co-pxenfs4" coords="4794,4333 5102,3600">
-		    <area id="co-pxenfs5" coords="3108,2666 3519,1800">
-		  </areaspec>
-		  <imageobject>
-		    <imagedata fileref="advanced-networking/pxe-nfs">
-		  </imageobject>
-		  <calloutlist>
-		    <callout arearefs="co-pxenfs1">
-		      <para>Client broadcasts DHCPDISCOVER.</para>
-		    </callout>
-		    <callout arearefs="co-pxenfs2">
-		      <para>DHCP server responds with IP address,
-			<literal>next-server</literal>,
-			<literal>filename</literal>, and
-			<literal>root-path</literal>.</para>
-		    </callout>
-		    <callout arearefs="co-pxenfs3">
-		      <para>Client sends <acronym>TFTP</acronym>
-			request to <literal>next-server</literal>
-			asking to retrieve
-			<literal>filename</literal>.</para>
-		    </callout>
-		    <callout arearefs="co-pxenfs4">
-		      <para>TFTP server responds and sends
-			<literal>filename</literal> to client.</para>
-		    </callout>
-		    <callout arearefs="co-pxenfs5">
-		      <para>Client executes
-			<literal>filename</literal> which is
-			&man.pxeboot.8;.  &man.pxeboot.8; loads the
-			kernel.  When the kernel executes, the root
-			filesystem specified by
-			<literal>root-path</literal> is mounted over
-			<acronym>NFS</acronym>.</para>
-		    </callout>
-		  </calloutlist>
-		</imageobjectco>
+	      <imageobjectco>
+		<areaspec units="calspair">
+		  <area id="co-pxenfs1" coords="2873,8133 3313,7266">
+		  <area id="co-pxenfs2" coords="3519,6333 3885,5500">
+		  <area id="co-pxenfs3" coords="4780,5866 5102,5200">
+		  <area id="co-pxenfs4" coords="4794,4333 5102,3600">
+		  <area id="co-pxenfs5" coords="3108,2666 3519,1800">
+		</areaspec>
+		<imageobject>
+		  <imagedata fileref="advanced-networking/pxe-nfs">
+		</imageobject>
+		<calloutlist>
+		  <callout arearefs="co-pxenfs1">
+		    <para>Client broadcasts DHCPDISCOVER.</para>
+		  </callout>
+		  <callout arearefs="co-pxenfs2">
+		    <para>DHCP server responds with IP address,
+		      <literal>next-server</literal>,
+		      <literal>filename</literal>, and
+		      <literal>root-path</literal>.</para>
+		  </callout>
+		  <callout arearefs="co-pxenfs3">
+		    <para>Client sends <acronym>TFTP</acronym>
+		      request to <literal>next-server</literal>
+		      asking to retrieve
+		      <literal>filename</literal>.</para>
+		  </callout>
+		  <callout arearefs="co-pxenfs4">
+		    <para>TFTP server responds and sends
+		      <literal>filename</literal> to client.</para>
+		  </callout>
+		  <callout arearefs="co-pxenfs5">
+		    <para>Client executes
+		      <literal>filename</literal> which is
+		      &man.pxeboot.8;.  &man.pxeboot.8; loads the
+		      kernel.  When the kernel executes, the root
+		      filesystem specified by
+		      <literal>root-path</literal> is mounted over
+		      <acronym>NFS</acronym>.</para>
+		  </callout>
+		</calloutlist>
+	      </imageobjectco>
 	    </mediaobjectco>
 	  </figure>
 	</step>