1 files changed, 21 insertions, 11 deletions
diff --git a/it/install-methods/tftp/bootp.xml b/it/install-methods/tftp/bootp.xml
index 9384b1752..c33e61edd 100644
--- a/it/install-methods/tftp/bootp.xml
+++ b/it/install-methods/tftp/bootp.xml
@@ -4,14 +4,16 @@
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
   <!-- <title>Setting up BOOTP server</title> -->
-  <title>Attivare un server BOOTP</title>
+  <title>Attivazione di un server BOOTP</title>
 <para>
 
-<!-- There are two BOOTP servers available for GNU/Linux, the CMU
+<!--
+There are two BOOTP servers available for GNU/Linux, the CMU
 <command>bootpd</command> and the other is actually a DHCP server, ISC
 <command>dhcpd</command>, which are contained in the
 <classname>bootp</classname> and <classname>dhcp</classname> packages
-in &debian;. -->
+in &debian;.
+-->
 
 Per GNU/Linux sono disponibili due server BOOTP, <command>bootpd</command>
 di CMU e attualmente l'altro è un server DHCP, <command>dhcpd</command> di
@@ -20,12 +22,14 @@ ISC che sono rispettivamente contenuti nei pacchetti &debian;
 
 </para><para>
 
-<!-- To use CMU <command>bootpd</command>, you must first uncomment (or
+<!--
+To use CMU <command>bootpd</command>, you must first uncomment (or
 add) the relevant line in <filename>/etc/inetd.conf</filename>.  On
 &debian;, you can run <userinput>update-inetd -enable
 bootps</userinput>, then <userinput>/etc/init.d/inetd
 reload</userinput> to do so. Elsewhere, the line in question should
-look like: -->
+look like:
+-->
 
 Per usare <command>bootpd</command> di CMU è necessario togliere i commenti
 (o aggiungere) la relativa riga in <filename>/etc/inetd.conf</filename>.
@@ -38,14 +42,16 @@ essere simile a questa:
 bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
 </screen></informalexample>
 
-<!-- Now, you must create an <filename>/etc/bootptab</filename> file.  This
+<!--
+Now, you must create an <filename>/etc/bootptab</filename> file.  This
 has the same sort of familiar and cryptic format as the good old BSD
 <filename>printcap</filename>, <filename>termcap</filename>, and
 <filename>disktab</filename> files.  See the
 <filename>bootptab</filename> manual page for more information.  For
 CMU <command>bootpd</command>, you will need to know the hardware
 (MAC) address of the client.  Here is an example
-<filename>/etc/bootptab</filename>: -->
+<filename>/etc/bootptab</filename>:
+-->
 
 Adesso è necessario creare il file <filename>/etc/bootptab</filename>.
 Questo file ha lo stesso formato criptico dei file
@@ -78,11 +84,13 @@ l'indirizzo hardware del client. L'opzione <quote>bf</quote> specifica
 quale file deve essere recuperato dal client tramite TFTP; si consulti
 <xref linkend="tftp-images"/> per ulteriori dettagli.
 
-<!-- <phrase arch="mips">
+<!--
+<phrase arch="mips">
 On SGI machines you can just enter the command monitor and type
 <userinput>printenv</userinput>.  The value of the
 <userinput>eaddr</userinput> variable is the machine's MAC address.
-</phrase> -->
+</phrase>
+-->
 
 <phrase arch="mips">
 Sulle macchine SGI si può usare il commando monitor e inserire
@@ -92,7 +100,8 @@ Sulle macchine SGI si può usare il commando monitor e inserire
 
 </para><para>
 
-<!-- By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
+<!--
+By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
 really easy, because it treats BOOTP clients as a moderately special
 case of DHCP clients.  Some architectures require a complex
 configuration for booting clients via BOOTP.  If yours is one of
@@ -101,7 +110,8 @@ will probably be able to get away with simply adding the
 <userinput>allow bootp</userinput> directive to the configuration
 block for the subnet containing the client, and restart
 <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd
-restart</userinput>. -->
+restart</userinput>.
+-->
 
 Al contrario l'impostazione di BOOTP con <command>dhcpd</command> di ISC è
 veramente semplice poiché tratta i client BOOTP come un caso moderatamente