Italian translation updated

17 files changed, 580 insertions, 396 deletions

diff --git a/it/install-methods/automatic-install.xml b/it/install-methods/automatic-install.xml
index 0728df35b..b70b4964a 100644
--- a/it/install-methods/automatic-install.xml
+++ b/it/install-methods/automatic-install.xml
@@ -7,13 +7,15 @@
  <title>Installazione automatizzata</title>
 <para>
 
-<!-- For installing on multiple computers it's possible to do fully
+<!--
+For installing on multiple computers it's possible to do fully
 automatic installations. Debian packages intended for this include
 <classname>fai</classname> (which uses an install server),
 <classname>replicator</classname>,
 <classname>systemimager</classname>,
 <classname>autoinstall</classname>, and
-the Debian Installer itself. -->
+the Debian Installer itself.
+-->
 
 È possibile effettuare installazioni su parecchi computer attraverso procedure
 completamente automatizzate. I pacchetti Debian adatti a questo scopo sono
@@ -28,15 +30,17 @@ completamente automatizzate. I pacchetti Debian adatti a questo scopo sono
   <title>Installazione automatizzata usando l'Installatore Debian</title>
 <para>
 
-<!-- The Debian Installer supports automating installs via preconfiguration
+<!--
+The Debian Installer supports automating installs via preconfiguration
 files. A preconfiguration file can be loaded from the network or from
 removable media, and used to fill in answers to questions asked during the
-installation process. -->
+installation process.
+-->
 
 L'Installatore Debian supporta le installazioni automatizzate tramite dei
 file di preconfigurazione. Un file di preconfigurazione può essere caricato
 dalla rete o da un supporto rimovibile ed è usato per rispondere alle
-domande che sarebbero normalmente poste durante il processo di installazione.
+domande che sarebbero normalmente poste durante il processo d'installazione.
 
 </para><para>
 
@@ -45,7 +49,7 @@ Full documentation on preseeding including a working example that you can
 edit is in <xref linkend="appendix-preseed"/>.
 -->
 
-La documentazione completa sulla preconfigurazione che comprende anche
+La documentazione completa sulla preconfigurazione comprende anche
 un esempio funzionante, che è possibile modificare, si trova in
 <xref linkend="appendix-preseed"/>.
 
diff --git a/it/install-methods/boot-drive-files.xml b/it/install-methods/boot-drive-files.xml
index 76b76924a..5056fa034 100644
--- a/it/install-methods/boot-drive-files.xml
+++ b/it/install-methods/boot-drive-files.xml
@@ -4,24 +4,27 @@
 
  <sect1 condition="bootable-disk" id="boot-drive-files">
  <!-- <title>Preparing Files for Hard Disk Booting</title> -->
- <title>Preparare i file per l'avvio da disco fisso</title>
-
+ <title>Preparazione dei file per l'avvio da disco fisso</title>
 <para>
 
-<!-- The installer may be booted using boot files placed on an
+<!--
+The installer may be booted using boot files placed on an
 existing hard drive partition, either launched from another operating
-system or by invoking a boot loader directly from the BIOS. -->
+system or by invoking a boot loader directly from the BIOS.
+-->
 
-L'installatore può essere fatto partire usando i file di avvio scritti su
+L'installatore può essere fatto partire usando i file d'avvio scritti su
 una partizione già esistente del disco fisso, lanciandoli da un altro
 sistema operativo o richiamando un bootloader direttamente dal BIOS.
 
 </para><para>
 
-<!-- A full, <quote>pure network</quote> installation can be achieved using this
+<!--
+A full, <quote>pure network</quote> installation can be achieved using this
 technique. This avoids all hassles of removable media, like finding
 and burning CD images or struggling with too numerous and
-unreliable floppy disks. -->
+unreliable floppy disks.
+-->
 
 Usando questo metodo è possibile realizzare una installazione completa
 puramente da rete evitando tutte le noie dei supporti rimovibili come la
@@ -30,20 +33,24 @@ e inaffidabili dischetti.
 
 </para><para arch="i386">
 
-<!-- The installer cannot boot from files on an NTFS file system. -->
+<!--
+The installer cannot boot from files on an NTFS file system.
+-->
 
 L'installatore non può essere avviato usando file su un filesystem NTFS.
 
 </para><para arch="powerpc">
 
-<!-- The installer cannot boot from files on an HFS+ file system.  MacOS
+<!--
+The installer cannot boot from files on an HFS+ file system.  MacOS
 System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all
 use HFS+. To determine whether your existing file system is HFS+,
 select <userinput>Get Info</userinput> for the volume in question. HFS
 file systems appear as <userinput>Mac OS Standard</userinput>, while
 HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must
 have an HFS partition in order to exchange files between MacOS and
-Linux, in particular the installation files you download. -->
+Linux, in particular the installation files you download.
+-->
 
 L'installatore non può essere avviato usando file su un file system HFS+.
 MacOS System 8.1 e successivi potrebbero usare un filesystem HFS+, tutti i
@@ -52,13 +59,15 @@ scegliere <userinput>Get Info</userinput> per il volume in questione, i
 file system HFS sono mostrati come <userinput>Mac OS Standard</userinput>,
 invece i filesystem HFS+ sono mostrati come <userinput>Mac OS
 Extended</userinput>. È necessario avere una partizione HFS per poter
-scambiare file fra MacOS e Linux, in particolare per i file di installazione.
+scambiare file fra MacOS e Linux, in particolare per i file d'installazione.
 
 </para><para arch="powerpc">
 
-<!-- Different programs are used for hard disk installation system booting,
+<!--
+Different programs are used for hard disk installation system booting,
 depending on whether the system is a <quote>NewWorld</quote> or an
-<quote>OldWorld</quote> model. -->
+<quote>OldWorld</quote> model.
+-->
 
 Per far partire l'installazione da disco fisso si possono usare diversi
 programmi a seconda che si disponga di un sistema <quote>NewWorld</quote>
@@ -71,31 +80,36 @@ o <quote>OldWorld</quote>.
   <command>GRUB</command></title> -->
   <title>Avvio dell'installatore da disco fisso con <command>LILO</command> o
   <command>GRUB</command></title>
-
 <para>
 
-<!-- This section explains how to add to or even replace an existing linux
+<!--
+This section explains how to add to or even replace an existing linux
 installation using either <command>LILO</command> or
-<command>GRUB</command>. -->
+<command>GRUB</command>.
+-->
 
 Questa sezione spiega come aggiungere o sostituire una installazione di Linux
 esistente usando <command>LILO</command> o <command>GRUB</command>.
 
 </para><para>
 
-<!-- At boot time, both bootloaders support loading in memory not
+<!--
+At boot time, both bootloaders support loading in memory not
 only the kernel, but also a disk image. This RAM disk can be used as
-the root file-system by the kernel. -->
+the root file-system by the kernel.
+-->
 
 All'avvio entrambi i bootloader supportano il caricamento in memoria non
-solo del kernel ma anche di una immagine del disco. Questo RAM disk può
+solo del kernel ma anche di un'immagine del disco. Questo RAM disk può
 essere usato come filesystem di root dal kernel.
 
 </para><para>
 
-<!-- Copy the following files from the Debian archives to a
+<!--
+Copy the following files from the Debian archives to a
 convenient location on your hard drive, for instance to
-<filename>/boot/newinstall/</filename>. -->
+<filename>/boot/newinstall/</filename>.
+-->
 
 Copiare i seguenti file dagli archivi Debian in una directory del proprio
 disco fisso, per esempio <filename>/boot/newinstall/</filename>.
@@ -103,14 +117,18 @@ disco fisso, per esempio <filename>/boot/newinstall/</filename>.
 <itemizedlist>
 <listitem><para>
 
-<!-- <filename>vmlinuz</filename> (kernel binary) -->
+<!--
+<filename>vmlinuz</filename> (kernel binary)
+-->
 
 <filename>vmlinuz</filename> (kernel)
 
 </para></listitem>
 <listitem><para>
 
-<!-- <filename>initrd.gz</filename> (ramdisk image) -->
+<!--
+<filename>initrd.gz</filename> (ramdisk image)
+-->
 
 <filename>initrd.gz</filename> (immagine del ramdisk)
 
@@ -119,8 +137,10 @@ disco fisso, per esempio <filename>/boot/newinstall/</filename>.
 
 </para><para>
 
-<!-- Finally, to configure the bootloader proceed to
-<xref linkend="boot-initrd"/>. -->
+<!--
+Finally, to configure the bootloader proceed to
+<xref linkend="boot-initrd"/>.
+-->
 
 Infine, per configurare il bootloader procedere con
 <xref linkend="boot-initrd"/>.
@@ -132,10 +152,10 @@ Infine, per configurare il bootloader procedere con
   <sect2 arch="powerpc" id="files-oldworld">
   <!-- <title>Hard Disk Installer Booting for OldWorld Macs</title> -->
   <title>Avvio dell'installatore da disco fisso su Mac OldWorld</title>
-
 <para>
 
-<!-- The <filename>boot-floppy-hfs</filename> floppy uses
+<!--
+The <filename>boot-floppy-hfs</filename> floppy uses
 <application>miBoot</application> to launch Linux installation, but
 <application>miBoot</application> cannot easily be used for hard disk
 booting. <application>BootX</application>, launched from MacOS,
@@ -144,7 +164,8 @@ disk. <application>BootX</application> can also be used to dual-boot
 MacOS and Linux after your Debian installation is complete. For the
 Performa 6360, it appears that <command>quik</command> cannot make the
 hard disk bootable.  So <application>BootX</application> is required
-on that model. -->
+on that model.
+-->
 
 Il dischetto <filename>boot-floppy-hfs</filename> utilizza
 <application>miBoot</application> per lanciare l'installazione di Linux,
@@ -159,7 +180,8 @@ l'avvio da disco fisso e quindi su questo modello è necessario usare
 
 </para><para>
 
-<!-- Download and unstuff the <application>BootX</application>
+<!--
+Download and unstuff the <application>BootX</application>
 distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>,
 or in the
 <filename>dists/woody/main/disks-powerpc/current/powermac</filename>
@@ -171,7 +193,8 @@ archive. Within the package, there is an empty folder called
 <filename>ramdisk.image.gz</filename> from the
 <filename>disks-powerpc/current/powermac</filename> folder, and place
 them in the <filename>Linux Kernels</filename> folder. Then place the
-<filename>Linux Kernels</filename> folder in the active System Folder. -->
+<filename>Linux Kernels</filename> folder in the active System Folder.
+-->
 
 Scaricare e decomprimere <application>BootX</application>, disponibile da
 <ulink url="&url-powerpc-bootx;"></ulink> o nella directory
@@ -191,17 +214,18 @@ Kernels</filename>. Copiare <filename>linux.bin</filename> e
   <sect2 arch="powerpc" id="files-newworld">
   <!-- <title>Hard Disk Installer Booting for NewWorld Macs</title> -->
   <title>Avvio dell'installatore da disco fisso su Mac NewWorld</title>
-
 <para>
 
-<!-- NewWorld PowerMacs support booting from a network or an ISO9660
+<!--
+NewWorld PowerMacs support booting from a network or an ISO9660
 CD-ROM, as well as loading ELF binaries directly from the hard
 disk. These machines will boot Linux directly via
 <command>yaboot</command>, which supports loading a kernel and RAMdisk
 directly from an ext2 partition, as well as dual-booting with
 MacOS. Hard disk booting of the installer is particularly appropriate
 for newer machines without floppy drives. <command>BootX</command> is
-not supported and must not be used on NewWorld PowerMacs. -->
+not supported and must not be used on NewWorld PowerMacs.
+-->
 
 I PowerMac NewWorld gestiscono l'avvio dalla rete, da un CD-ROM ISO9660 e
 anche leggendo direttamente i binari ELF dal disco fisso. Queste macchine
@@ -214,15 +238,17 @@ non è supportato e non deve essere usato sui PowerMac NewWorld.
 
 </para><para>
 
-<!-- <emphasis>Copy</emphasis> (not move) the following four files which
+<!--
+<emphasis>Copy</emphasis> (not move) the following four files which
 you downloaded earlier from the Debian archives, onto the root level
 of your hard drive (this can be accomplished by
-<keycap>option</keycap>-dragging each file to the hard drive icon). -->
+<keycap>option</keycap>-dragging each file to the hard drive icon).
+-->
 
 <emphasis>Copiare</emphasis> (non spostare) i seguenti quattro file, che
 devono essere preventivamente scaricati dagli archivi Debian, nella directory
 principale del disco fisso (questo si può fare trascinando ciascun file
-sull'icona del disco mentre si tiene premuto <keycap>option</keycap>)."
+sull'icona del disco mentre si tiene premuto <keycap>option</keycap>).
 
 <itemizedlist>
 <listitem><para>
@@ -249,11 +275,13 @@ sull'icona del disco mentre si tiene premuto <keycap>option</keycap>)."
 
 </para><para>
 
-<!-- Make a note of the partition number of the MacOS partition where you
+<!--
+Make a note of the partition number of the MacOS partition where you
 place these files. If you have the MacOS <command>pdisk</command>
 program, you can use the L command to check for the partition
 number. You will need this partition number for the command you type
-at the Open Firmware prompt when you boot the installer. -->
+at the Open Firmware prompt when you boot the installer.
+-->
 
 Prendere nota del numero della partizione MacOS su cui si copiano questi
 file. Se si dispone del programma MacOS <command>pdisk</command> si può
@@ -263,7 +291,9 @@ l'installatore.
 
 </para><para>
 
-<!-- To boot the installer, proceed to <xref linkend="boot-newworld"/>. -->
+<!--
+To boot the installer, proceed to <xref linkend="boot-newworld"/>.
+-->
 
 Per avviare l'installatore procedere con <xref linkend="boot-newworld"/>.
 
diff --git a/it/install-methods/boot-usb-files.xml b/it/install-methods/boot-usb-files.xml
index 07ea983cb..05aa1a132 100644
--- a/it/install-methods/boot-usb-files.xml
+++ b/it/install-methods/boot-usb-files.xml
@@ -1,19 +1,21 @@
 <!-- retain these comments for translator revision tracking -->
 <!-- original version: 32124 -->
 
+
  <sect1 condition="bootable-usb" id="boot-usb-files">
  <!-- <title>Preparing Files for USB Memory Stick Booting</title> -->
- <title>Preparare i file per l'avvio da penne USB</title>
-
+ <title>Preparazione dei file per l'avvio da penne USB</title>
 <para>
 
-<!-- For preparing the USB stick you will need a system where GNU/Linux is
+<!--
+For preparing the USB stick you will need a system where GNU/Linux is
 already running and where USB is supported. You should ensure that the
 usb-storage kernel module is loaded (<userinput>modprobe
 usb-storage</userinput>) and try to find out which SCSI device the USB
 stick has been mapped to (in this example
 <filename>/dev/sda</filename> is used). To write to your stick, you
-will probably have to turn off its write protection switch. -->
+will probably have to turn off its write protection switch.
+-->
 
 Per preparare la penna USB è necessario un sistema GNU/Linux con supporto
 USB già funzionante. Si deve controllare che il modulo del kernel usb-storage
@@ -24,8 +26,10 @@ necessario disattivare la protezione dalla scrittura.
 
 </para><para>
 
-<!-- Note, that the USB stick should be at least 128 MB in size (smaller
-setups are possible if you follow <xref linkend="usb-copy-flexible"/>). -->
+<!--
+Note, that the USB stick should be at least 128 MB in size (smaller
+setups are possible if you follow <xref linkend="usb-copy-flexible"/>).
+-->
 
 Notare che la penna USB deve essere da almeno 128&nbsp;MB (è possibile fare
 anche installazioni più piccole seguendo <xref linkend="usb-copy-flexible"/>).
@@ -33,15 +37,16 @@ anche installazioni più piccole seguendo <xref linkend="usb-copy-flexible"/>).
 </para>
 
   <sect2 id="usb-copy-easy">
-  <!--<title>Copying the files &mdash; the easy way</title> -->
+  <!-- <title>Copying the files &mdash; the easy way</title> -->
   <title>Copia dei file &mdash; il modo semplice</title>
-
 <para arch="i386">
 
-<!-- There is an all-in-one file <filename>hd-media/boot.img.gz</filename>
+<!--
+There is an all-in-one file <filename>hd-media/boot.img.gz</filename>
 which contains all the installer files (including the kernel) as well
 as <command>SYSLINUX</command> and its configuration file. You only
-have to extract it directly to your USB stick: -->
+have to extract it directly to your USB stick:
+-->
 
 C'è un file all-in-one <filename>hd-media/boot.img.gz</filename> che
 contiene non solo tutti i file dell'installatore (kernel compreso) ma
@@ -54,19 +59,21 @@ sufficiente estrarlo direttamente sulla penna USB:
 
 </para><para arch="powerpc">
 
-<!-- There is an all-in-one file <filename>hd-media/boot.img.gz</filename>
+<!--
+There is an all-in-one file <filename>hd-media/boot.img.gz</filename>
 which contains all the installer files (including the kernel) as well
 as <command>yaboot</command> and its configuration file. Create a
 partition of type "Apple_Bootstrap" on your USB stick using
 <command>mac-fdisk</command>'s <userinput>C</userinput> command and
-extract the image directly to that: -->
+extract the image directly to that:
+-->
 
 C'è un file all-in-one <filename>hd-media/boot.img.gz</filename> che
 contiene non solo tutti i file dell'installatore (kernel compreso) ma
 anche <command>yaboot</command> e il suo file di configurazione. Creare
-una partizione di tipo "Apple_Bootstrap" sulla penna USB usando il comando
-<userinput>C</userinput> di <command>mac-fdisk</command> ed estrarre
-l'immagine direttamente sulla penna USB:
+una partizione di tipo <quote>Apple_Bootstrap</quote> sulla penna USB
+usando il comando <userinput>C</userinput> di <command>mac-fdisk</command>
+ed estrarre l'immagine direttamente sulla penna USB:
 
 <informalexample><screen>
 # zcat boot.img.gz &gt; /dev/<replaceable>sda2</replaceable>
@@ -86,7 +93,8 @@ fare attenzione a usare il nome corretto per il device della penna USB.
 </para></warning>
 <para>
 
-<!-- After that, mount the USB memory stick (<userinput>mount
+<!--
+After that, mount the USB memory stick (<userinput>mount
 <replaceable arch="i386">/dev/sda</replaceable>
 <replaceable arch="powerpc">/dev/sda2</replaceable>
 /mnt</userinput>), which will now have
@@ -94,7 +102,8 @@ fare attenzione a usare il nome corretto per il device della penna USB.
 <phrase arch="powerpc">an HFS filesystem</phrase>
 on it, and copy a Debian netinst or businesscard ISO image to it.
 Please note that the file name must end in <filename>.iso</filename>.
-Unmount the stick (<userinput>umount /mnt</userinput>) and you are done. -->
+Unmount the stick (<userinput>umount /mnt</userinput>) and you are done.
+-->
 
 Poi montare la penna USB (<userinput>mount
 <replaceable arch="i386">/dev/sda</replaceable>
@@ -112,11 +121,12 @@ penna (<userinput>umount /mnt</userinput>).
   <sect2 id="usb-copy-flexible">
   <!-- <title>Copying the files &mdash; the flexible way</title> -->
   <title>Copia dei file &mdash; il modo flessibile</title>
-
 <para>
 
-<!-- If you like more flexibility or just want to know what's going on, you
-should use the following method to put the files on your stick. -->
+<!--
+If you like more flexibility or just want to know what's going on, you
+should use the following method to put the files on your stick.
+-->
 
 Se si preferisce avere più flessibilità o semplicemente si vuole capire
 cosa si sta facendo si deve usare questo metodo per scrivere i file sulla
@@ -129,13 +139,14 @@ penna.
 
    <sect3>
    <!-- <title>Adding an ISO image</title> -->
-   <title>Aggiungere una immagine ISO</title>
-
+   <title>Aggiungere un'immagine ISO</title>
 <para>
 
-<!-- Now you should put any Debian ISO image (businesscard, netinst or even
+<!--
+Now you should put any Debian ISO image (businesscard, netinst or even
 a full one) onto your stick (if it fits). The file name of such an
-image must end in <filename>.iso</filename>. -->
+image must end in <filename>.iso</filename>.
+-->
 
 Adesso si deve copiare una qualsiasi immagine ISO (businesscard, netinst o
 persino una completa se c'entra) sulla propria penna. Il nome del file
@@ -143,12 +154,14 @@ immagine deve avere estensione <filename>.iso</filename>.
 
 </para><para>
 
-<!-- If you want to install over the network, without using an ISO image,
+<!--
+If you want to install over the network, without using an ISO image,
 you will of course skip the previous step. Moreover you will have to
 use the initial ramdisk from the <filename>netboot</filename>
 directory instead of the one from <filename>hd-media</filename>,
 because <filename>hd-media/initrd.gz</filename> does not have network
-support. -->
+support.
+-->
 
 Se si vuole installare usando la rete, senza usare una immagine ISO, si deve
 saltare il passo precedente ma è necessario usare il ramdisk iniziale nella
@@ -158,8 +171,10 @@ non c'è il supporto per la rete.
 
 </para><para>
 
-<!-- When you are done, unmount the USB memory stick (<userinput>umount
-/mnt</userinput>) and activate its write protection switch. -->
+<!--
+When you are done, unmount the USB memory stick (<userinput>umount
+/mnt</userinput>) and activate its write protection switch.
+-->
 
 Conclusa la copia dei file, smontare la penna USB (<userinput>umount
 /mnt</userinput>) e attivare la protezione dalla scrittura.
@@ -171,13 +186,14 @@ Conclusa la copia dei file, smontare la penna USB (<userinput>umount
    <sect3 arch="i386">
    <!-- <title>Booting the USB stick</title> -->
    <title>Avvio dalla penna USB</title>
-
 <warning><para>
 
-<!-- If your system refuses to boot from the memory stick, the stick may
+<!--
+If your system refuses to boot from the memory stick, the stick may
 contain an invalid master boot record (MBR). To fix this, use the
 <command>install-mbr</command> command from the package
-<classname>mbr</classname>: -->
+<classname>mbr</classname>:
+-->
 
 Se il proprio sistema rifiuta di partire dalla penna, la penna potrebbe
 contenere un MBR (master boot record) non valido. Per risolvere questo
diff --git a/it/install-methods/create-floppy.xml b/it/install-methods/create-floppy.xml
index 765889be8..67dc8e4ea 100644
--- a/it/install-methods/create-floppy.xml
+++ b/it/install-methods/create-floppy.xml
@@ -4,41 +4,47 @@
 
  <sect1 condition="supports-floppy-boot" id="create-floppy">
  <!-- <title>Creating Floppies from Disk Images</title> -->
- <title>Creare i dischetti partendo dalle immagini dei dischi</title>
-
+ <title>Creazione dei dischetti partendo dalle immagini dei dischi</title>
 <para>
 
-<!-- Bootable floppy disks are generally used as a last resort to boot the
-installer on hardware that cannot boot from CD or by other means. -->
+<!--
+Bootable floppy disks are generally used as a last resort to boot the
+installer on hardware that cannot boot from CD or by other means.
+-->
 
-I dischetti di avvio sono generalmente l'ultima risorsa per far partire
+I dischetti d'avvio sono generalmente l'ultima risorsa per far partire
 l'installatore sull'hardware che non può essere avviato da CD o da altri
 supporti.
 
 </para><para arch="powerpc">
 
-<!-- Floppy disk booting reportedly fails on Mac USB floppy drives. -->
+<!--
+Floppy disk booting reportedly fails on Mac USB floppy drives.
+-->
 
-È stato riscontrato che l'avvio dal dischetto non funziona con i lettori USB
-su Mac.
+È stato riscontrato che su Mac l'avvio dal dischetto non funziona con
+i lettori USB.
 
 </para><para arch="m68k">
 
-<!-- Floppy disk booting is not supported on Amigas or
-68k Macs. -->
+<!--
+Floppy disk booting is not supported on Amigas or 68k Macs.
+-->
 
 L'avvio dal dischetto non è supportato su Amiga e sui Mac 68k.
 
 </para><para>
 
-<!-- Disk images are files containing the complete contents of a floppy
+<!--
+Disk images are files containing the complete contents of a floppy
 disk in <emphasis>raw</emphasis> form.  Disk images, such as
 <filename>boot.img</filename>, cannot simply be copied to floppy
 drives.  A special program is used to write the image files to floppy
 disk in <emphasis>raw</emphasis> mode.  This is required because these
 images are raw representations of the disk; it is required to do a
 <emphasis>sector copy</emphasis> of the data from the file onto the
-floppy. -->
+floppy.
+-->
 
 Le immagini del disco sono dei file che hanno tutto il contenuto di un
 dischetto in formato <emphasis>raw</emphasis>. Le immagini dei dischi, come
@@ -46,13 +52,15 @@ dischetto in formato <emphasis>raw</emphasis>. Le immagini dei dischi, come
 dischetto. Per scrivere i file immagine in formato <emphasis>raw</emphasis>
 è necessario usare un programma speciale perché le immagini sono la
 rappresentazione grezza del disco e quindi si deve fare una <emphasis>copia
-dei settori</emphasis> dei dati dal file sul dischetto.
+per settori</emphasis> dei dati dal file sul dischetto.
 
 </para><para>
 
-<!-- There are different techniques for creating floppies from disk images,
+<!--
+There are different techniques for creating floppies from disk images,
 which depend on your platform.  This section describes how to create
-floppies from disk images on different platforms. -->
+floppies from disk images on different platforms.
+-->
 
 Ci sono varie tecniche per creare i dischetti dalle immagini, a seconda
 della piattaforma usata. In questa sezione è descritto come creare i
@@ -60,9 +68,11 @@ dischetti a partire dalle immagini su diverse piattaforme.
 
 </para><para>
 
-<!-- No matter which method you use to create your floppies, you should
+<!--
+No matter which method you use to create your floppies, you should
 remember to flip the write-protect tab on the floppies once you have
-written them, to ensure they are not damaged unintentionally. -->
+written them, to ensure they are not damaged unintentionally.
+-->
 
 Indipendentemente dal metodo usato per creare i dischetti è importante
 ricordarsi di spostare la linguetta di protezione dalla scrittura una
@@ -72,14 +82,15 @@ inavvertitamente.
 </para>
 
   <sect2>
-  <!--<title>Writing Disk Images From a Linux or Unix System</title>-->
-  <title>Scrivere le immagini dei dischi da sistemi Linux o Unix</title>
-
+  <!-- <title>Writing Disk Images From a Linux or Unix System</title> -->
+  <title>Scrittura delle immagini dei dischi da sistemi Linux o Unix</title>
 <para>
 
-<!-- To write the floppy disk image files to the floppy disks, you will
+<!--
+To write the floppy disk image files to the floppy disks, you will
 probably need root access to the system.  Place a good, blank floppy
-in the floppy drive.  Next, use the command -->
+in the floppy drive.  Next, use the command
+-->
 
 Per scrivere i file con le immagini dei dischetti potrebbe essere necessario
 avere accesso al sistema come root. Inserire un dischetto vergine nel lettore
@@ -89,7 +100,8 @@ e poi usare il comando
 $ dd if=<replaceable>nomefile</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync
 </screen></informalexample>
 
-<!-- where <replaceable>filename</replaceable> is one of the floppy disk image
+<!--
+where <replaceable>filename</replaceable> is one of the floppy disk image
 files (see <xref linkend="downloading-files"/> for what
 <replaceable>filename</replaceable> should be).
 <filename>/dev/fd0</filename> is a commonly used name of the floppy
@@ -103,7 +115,8 @@ is out and the disk has stopped revolving before you remove it from
 the drive. On some systems, you'll have to run a command to eject the
 floppy from the drive
 <phrase arch="sparc">(on Solaris, use <command>eject</command>, see
-the manual page)</phrase>. -->
+the manual page)</phrase>.
+-->
 
 dove <replaceable>nomefile</replaceable> è uno dei file immagine del
 dischetto (si consulti <xref linkend="downloading-files"/> per un elenco dei
@@ -119,11 +132,13 @@ Solaris usare <command>eject</command>, si consulti la pagina man)</phrase>.
 
 </para><para>
 
-<!-- Some systems attempt to automatically mount a floppy disk when you
+<!--
+Some systems attempt to automatically mount a floppy disk when you
 place it in the drive. You might have to disable this feature before
 the workstation will allow you to write a floppy in <emphasis>raw
 mode</emphasis>.  Unfortunately, how to accomplish this will vary
-based on your operating system. -->
+based on your operating system.
+-->
 
 Alcuni sistemi tentano di montare automaticamente il dischetto appena lo
 si inserisce nel lettore; è opportuno disattivare questa funzione in modo
@@ -133,7 +148,8 @@ operativo.
 
 <phrase arch="sparc">
 
-<!-- On Solaris, you can work around
+<!--
+On Solaris, you can work around
 volume management to get raw access to the floppy.  First, make sure
 that the floppy is auto-mounted (using <command>volcheck</command> or
 the equivalent command in the file manager). Then use a
@@ -143,7 +159,8 @@ the equivalent command in the file manager). Then use a
 where <replaceable>floppy_name</replaceable> is the name the floppy
 disk was given when it was formatted (unnamed floppies default to the
 name <filename>unnamed_floppy</filename>).  On other systems, ask your
-system administrator. -->
+system administrator.
+-->
 
 Su Solaris si può aggirare la gestione del volume per avere l'accesso diretto
 al dischetto. Per prima cosa assicurarsi che il dischetto sia stato montato
@@ -160,16 +177,17 @@ amministratore.
 
 </para><para arch="powerpc">
 
-<!-- If writing a floppy on powerpc Linux, you will need to eject it. The
+<!--
+If writing a floppy on powerpc Linux, you will need to eject it. The
 <command>eject</command> program handles this nicely; you might need
-to install it. -->
+to install it.
+-->
 
 Per scrivere un dischetto da Linux/powerpc è necessario prima espellerlo.
 Il programma <command>eject</command> gestisce questa funzione in modo
 corretto; è consigliabile installarlo.
 
 </para>
-
   </sect2>
 
 &floppy-i386.xml; <!-- can be used for other arches -->
@@ -177,4 +195,3 @@ corretto; è consigliabile installarlo.
 &floppy-powerpc.xml;
 
  </sect1>
-
diff --git a/it/install-methods/download/alpha.xml b/it/install-methods/download/alpha.xml
index 330ef9352..3ad42c7f3 100644
--- a/it/install-methods/download/alpha.xml
+++ b/it/install-methods/download/alpha.xml
@@ -4,18 +4,19 @@
 
    <sect3 arch="alpha">
    <!-- <title>Alpha Installation Files</title> -->
-   <title>File di installazione per Alpha</title>
-
+   <title>File d'installazione per Alpha</title>
 <para>
 
-<!-- If you choose to boot from ARC console firmware using
+<!--
+If you choose to boot from ARC console firmware using
 <command>MILO</command>, you will also need to prepare a disk
 containing <command>MILO</command> and <command>LINLOAD.EXE</command>
 from the provided disk images. See <xref linkend="alpha-firmware"/>
 for more information on Alpha
 firmware and boot loaders. The floppy images can be found in the
 <filename>MILO</filename> directory as
-<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>. -->
+<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>.
+-->
 
 Se si sceglie di avviare dalla console firmware ARC usando
 <command>MILO</command> è necessario preparare un disco contenente
@@ -27,7 +28,8 @@ possono essere trovate nella directory <filename>MILO</filename> con nome
 
 </para><para>
 
-<!-- Unfortunately, these <command>MILO</command> images could not be
+<!--
+Unfortunately, these <command>MILO</command> images could not be
 tested and might not work for all subarchitectures. If you find it
 doesn't work for you, try copying the appropriate
 <command>MILO</command> binary onto the floppy
@@ -35,7 +37,8 @@ doesn't work for you, try copying the appropriate
 Note that those <command>MILO</command>s don't support ext2 <quote>sparse
 superblocks</quote>, so you can't use them to load kernels from newly
 generated ext2 file systems. As a workaround, you can put your kernel
-onto the FAT partition next to the <command>MILO</command>. -->
+onto the FAT partition next to the <command>MILO</command>.
+-->
 
 Sfortunatamente queste immagini <command>MILO</command> non possono
 essere testate e potrebbero non funzionare su tutte le sottoarchitetture. Se
@@ -43,15 +46,17 @@ si scopre che quella per la propria sottoarchitettura non funziona, provare
 a copiare il corretto binario di <command>MILO</command> sul dischetto
 (<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>). Notare
 che questi <command>MILO</command> non supportano gli <quote>sparse
-superblocks</quote> di ext2 e quindi non si possono usare per caricare il
+superblock</quote> di ext2 e quindi non si possono usare per caricare il
 kernel da filesystem ext2 appena creati. Come rimedio si può copiare il
 kernel insieme a <command>MILO</command> su una partizione FAT.
 
 </para><para>
 
-<!-- <command>MILO</command> binaries are platform-specific.  See
+<!--
+<command>MILO</command> binaries are platform-specific.  See
 <xref linkend="alpha-cpus"/> to determine the appropriate
-<command>MILO</command> image for your Alpha platform. -->
+<command>MILO</command> image for your Alpha platform.
+-->
 
 Gli eseguibili di <command>MILO</command> sono specifici per la piattaforma.
 Consultare <xref linkend="alpha-cpus"/> per determinare l'immagine di
diff --git a/it/install-methods/download/m68k.xml b/it/install-methods/download/m68k.xml
index c2281674c..337427726 100644
--- a/it/install-methods/download/m68k.xml
+++ b/it/install-methods/download/m68k.xml
@@ -5,26 +5,29 @@
    <sect3 arch="m68k" id="kernel-22">
    <!-- <title>Choosing a Kernel</title> -->
    <title>Scegliere un kernel</title>
-
 <para>
 
-<!--Some m68k subarchs have a choice of kernels to install. In general we
+<!--
+Some m68k subarchs have a choice of kernels to install. In general we
 recommend trying the most recent version first. If your subarch or
 machine needs to use a 2.2.x kernel, make sure you choose one of the
-images that supports 2.2.x kernels (see the <ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>). -->
+images that supports 2.2.x kernels (see the <ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>).
+-->
 
 Alcune delle sottoarchitetture m68k consentono la scelta dei kernel da
 installare. In generale si raccomanda di provare prima l'uso della versione
-pi&ugrave; recente. Se la propria sottoarchitettura o macchina necessita
+più recente. Se la propria sottoarchitettura o macchina necessita
 di un kernel 2.2 assicuratevi di usare una delle immagini che
-supportano i kernel 2.2.x (si consulti
-<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>).
+supportano i kernel 2.2.x (si consulti <ulink
+url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>).
 
 </para>
 <para>
 
-<!-- All of the m68k images for use with 2.2.x kernels, require the kernel
-parameter &ramdisksize;. -->
+<!--
+All of the m68k images for use with 2.2.x kernels, require the kernel
+parameter &ramdisksize;.
+-->
 
 Tutte le immagini per m68k che usano un kernel 2.2.x richiedono il parametro
 del kernel &ramdisksize;.
diff --git a/it/install-methods/downloading-files.xml b/it/install-methods/downloading-files.xml
index b6cf4fd04..7ac0c5f14 100644
--- a/it/install-methods/downloading-files.xml
+++ b/it/install-methods/downloading-files.xml
@@ -3,12 +3,13 @@
 
  <sect1 id="downloading-files">
  <!-- <title>Downloading Files from Debian Mirrors</title> -->
- <title>Scaricare i file dai mirror Debian</title>
-
+ <title>Recupero dei file dai mirror Debian</title>
 <para>
 
-<!-- To find the nearest (and thus probably the fastest) mirror, see the
-<ulink url="&url-debian-mirrors;">list of Debian mirrors</ulink>. -->
+<!--
+To find the nearest (and thus probably the fastest) mirror, see the
+<ulink url="&url-debian-mirrors;">list of Debian mirrors</ulink>.
+-->
 
 Per scoprire qual è il mirror più vicino (e quindi probabilmente il più
 veloce) si consulti l'<ulink url="&url-debian-mirrors;">elenco dei mirror
@@ -16,9 +17,11 @@ Debian</ulink>.
 
 </para><para>
 
-<!-- When downloading files from a Debian mirror, be sure to download the
+<!--
+When downloading files from a Debian mirror, be sure to download the
 files in <emphasis>binary</emphasis> mode, not text or automatic
-mode. -->
+mode.
+-->
 
 Quando si scaricano dei file da uno dei mirror Debian assicurarsi di
 scaricare in modalità <emphasis>binaria</emphasis> e non in modalità testo
@@ -27,17 +30,18 @@ o automatica.
 </para>
 
   <sect2 id="where-files">
-  <!--<title>Where to Find Installation Images</title> -->
-  <title>Dove trovare le immagini di installazione</title>
-
+  <!-- <title>Where to Find Installation Images</title> -->
+  <title>Dove trovare le immagini per l'installazione</title>
 <para>
 
-<!-- The installation images are located on each Debian mirror in the directory
+<!--
+The installation images are located on each Debian mirror in the directory
 <ulink url="&url-debian-installer;/images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink>
 &mdash; the <ulink url="&url-debian-installer;/images/MANIFEST">MANIFEST</ulink>
-lists each image and its purpose. -->
+lists each image and its purpose.
+-->
 
-Le immagini di installazione sono su tutti i mirror Debian nella directory
+Le immagini per l'installazione sono su tutti i mirror Debian nella directory
 <ulink url="&url-debian-installer;/images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink>;
 in <ulink url="&url-debian-installer;/images/MANIFEST">MANIFEST</ulink> sono
 elencate tutte le immagini e il loro scopo.
diff --git a/it/install-methods/floppy/i386.xml b/it/install-methods/floppy/i386.xml
index 0a3f46332..4cc02297a 100644
--- a/it/install-methods/floppy/i386.xml
+++ b/it/install-methods/floppy/i386.xml
@@ -6,24 +6,27 @@
 <!--  access to a PC in order to make a floppy for other arches. -->
 
   <sect2>
-  <!--<title>Writing Disk Images From DOS, Windows, or OS/2</title>-->
-  <title>Scrivere le immagini dei dischi da DOS, Windows o OS/2</title>
-
+  <!-- <title>Writing Disk Images From DOS, Windows, or OS/2</title> -->
+  <title>Scrittura delle immagini dei dischi da DOS, Windows o OS/2</title>
 <para>
 
-<!--If you have access to an i386 machine, you can use one of the
-following programs to copy images to floppies. -->
+<!--
+If you have access to an i386 machine, you can use one of the
+following programs to copy images to floppies.
+-->
 
-Se si ha accesso a una macchina i386 si pu&ograve; usare uno dei seguenti
+Se si ha accesso a una macchina i386 si può usare uno dei seguenti
 programmi per copiare le immagini sui dischetti.
 
 </para><para>
 
-<!--The <command>rawrite1</command> and <command>rawrite2</command> programs
+<!--
+The <command>rawrite1</command> and <command>rawrite2</command> programs
 can be used under MS-DOS. To use these programs, first make sure that you
 are booted into DOS. Trying to use these programs from within a DOS box in
 Windows, or double-clicking on these programs from the Windows Explorer is
-<emphasis>not</emphasis> expected to work. -->
+<emphasis>not</emphasis> expected to work.
+-->
 
 Su MS-DOS si possono usare i programmi <command>rawrite1</command> e
 <command>rawrite2</command>. Prima di usarli assicurarsi di aver avviato
@@ -33,18 +36,22 @@ su Windows o facendo doppio clic su questi programmi da Windows Explorer
 
 </para><para>
 
-<!--The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000,
+<!--
+The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000,
 ME, XP and probably later versions. To use it you will need to unpack
-diskio.dll in the same directory. -->
+diskio.dll in the same directory.
+-->
 
 Il programma <command>rwwrtwin</command> funziona su Windows 95, NT, 98,
 2000, ME, XP e probabilmente anche sulle versioni successive. Per usarlo
-&egrave; necessario scompattare diskio.dll nella stessa directory.
+è necessario scompattare diskio.dll nella stessa directory.
 
 </para><para>
 
-<!--These tools can be found on the Official Debian CD-ROMs under the
-<filename>/tools</filename> directory. -->
+<!--
+These tools can be found on the Official Debian CD-ROMs under the
+<filename>/tools</filename> directory.
+-->
 
 Questi programmi possono essere trovati sui CD-ROM Ufficiali Debian nella
 directory <filename>/tools</filename>.
diff --git a/it/install-methods/floppy/m68k.xml b/it/install-methods/floppy/m68k.xml
index f79b893db..54a7f1535 100644
--- a/it/install-methods/floppy/m68k.xml
+++ b/it/install-methods/floppy/m68k.xml
@@ -3,44 +3,44 @@
 
 
   <sect2 arch="m68k">
-  <!--<title>Writing Disk Images on Atari Systems</title>-->
-  <title>Scrivere le immagini dei dischi su sistemi Atari</title>
-
+  <!-- <title>Writing Disk Images on Atari Systems</title> -->
+  <title>Scrittura delle immagini dei dischi su sistemi Atari</title>
 <para>
 
-<!--You'll find the &rawwrite.ttp; program in the same directory as the
+<!--
+You'll find the &rawwrite.ttp; program in the same directory as the
 floppy disk images.  Start the program by double clicking on the
 program icon, and type in the name of the floppy image file you want
-written to the floppy at the TOS program command line dialog box. -->
+written to the floppy at the TOS program command line dialog box.
+-->
 
-Nella stessa directory delle immagini dei dischetti c'&egrave; il programma
+Nella stessa directory delle immagini dei dischetti c'è il programma
 &rawwrite.ttp;. Avviare il programma facendo doppio clic sulla sua icona e
 inserire il nome del file immagine che si vuole scrivere sul dischetto nella
 riga di comando TOS della finestra di dialogo.
 
 </para>
-
   </sect2>
 
   <sect2 arch="m68k">
-  <!--<title>Writing Disk Images on Macintosh Systems</title>-->
-  <title>Scrivere le immagini dei dischi su sistemi Macintosh</title>
-
+  <!-- <title>Writing Disk Images on Macintosh Systems</title> -->
+  <title>Scrittura delle immagini dei dischi su sistemi Macintosh</title>
 <para>
 
-<!--There is no MacOS application to write images to floppy disks
+<!--
+There is no MacOS application to write images to floppy disks
 (and there would be no point in doing this as you can't use these
 floppies to boot the installation system or install kernel and modules
 from on Macintosh).  However, these files are needed for the
 installation of the operating system and modules, later in the
-process. -->
+process.
+-->
 
-Non c'&egrave; nessuna applicazione MacOS per scrivere file immagine sui dischetti
+Non c'è nessuna applicazione MacOS per scrivere file immagine sui dischetti
 (e non avrebbe neanche senso dato che non si possono usare questi dischetti
 per avviare il sistema d'installazione o per installare kernel e moduli su
 Macintosh). Comunque questi file sono necessari in seguito durante il
 processo d'installazione del sistema operativo e dei moduli.
 
 </para>
-
   </sect2>
diff --git a/it/install-methods/floppy/powerpc.xml b/it/install-methods/floppy/powerpc.xml
index 5f7d97dce..4468461da 100644
--- a/it/install-methods/floppy/powerpc.xml
+++ b/it/install-methods/floppy/powerpc.xml
@@ -3,67 +3,73 @@
 
 
   <sect2 arch="powerpc">
-  <!--<title>Writing Disk Images From MacOS</title>-->
-  <title>Scrivere le immagini dei dischi da MacOS</title>
-
+  <!-- <title>Writing Disk Images From MacOS</title> -->
+  <title>Scrittura delle immagini dei dischi da MacOS</title>
 <para>
 
-<!--An AppleScript, <application>Make Debian Floppy</application>, is
+<!--
+An AppleScript, <application>Make Debian Floppy</application>, is
 available for burning floppies from the provided disk image files. It
 can be downloaded from
 <ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>. To
 use it, just unstuff it on your desktop, and then drag any floppy
 image file to it. You must have Applescript installed and enabled in
 your extensions manager. Disk Copy will ask you to confirm that you
-wish to erase the floppy and proceed to write the file image to it. -->
+wish to erase the floppy and proceed to write the file image to it.
+-->
 
-&Egrave; disponibile un AppleScript, <application>Make Debian Floppy</application>,
-per creare i dischetti dai file immagine forniti. Pu&ograve; essere scaricato da
+È disponibile un AppleScript, <application>Make Debian Floppy</application>,
+per creare i dischetti dai file immagine forniti. Può essere scaricato da
 <ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>.
-Per usarlo &egrave; sufficiente copiarlo sul desktop e poi trascinarci sopra
-ciascun file immagine. &Egrave; necessario che AppleScript sia installato e
+Per usarlo è sufficiente copiarlo sul desktop e poi trascinarci sopra
+ciascun file immagine. È necessario che AppleScript sia installato e
 attivato dal gestore delle estensioni. Disk Copy chiede conferma prima di
 cancellare il dischetto e di procedere alla scrittura del file immagine.
 
 </para><para>
 
-<!--You can also use the MacOS utility <command>Disk Copy</command>
+<!--
+You can also use the MacOS utility <command>Disk Copy</command>
 directly, or the freeware utility <command>suntar</command>. The
 <filename>root.bin</filename> file is an example of a floppy
 image. Use one of the following methods to create a floppy from the
-floppy image with these utilities. -->
+floppy image with these utilities.
+-->
 
-Si pu&ograve; anche usare direttamente il programma di MacOS <command>Disk
+Si può anche usare direttamente il programma per MacOS <command>Disk
 Copy</command> oppure il programma freeware <command>suntar</command>.
-<filename>root.bin</filename> &Egrave; un file immagine di esempio. Usate uno
+Per esempio, <filename>root.bin</filename> è un file immagine. Usare uno
 dei seguenti metodi per creare un dischetto dal file immagine con questi
-programmi .
+programmi.
 
 </para>
 
    <sect3>
-<!--<title>Writing Disk Images with <command>Disk Copy</command></title>-->
+   <!-- <title>Writing Disk Images with <command>Disk Copy</command></title> -->
    <title>Scrivere le immagini dei dischi con <command>Disk Copy</command></title>
 <para>
 
-<!--If you are creating the floppy image from files which were originally
+<!--
+If you are creating the floppy image from files which were originally
 on the official &debian; CD, then the Type and Creator are already set
 correctly. The following <command>Creator-Changer</command> steps are
-only necessary if you downloaded the image files from a Debian mirror. -->
+only necessary if you downloaded the image files from a Debian mirror.
+-->
 
 Se si stanno creando i dischetti dai file immagine che sono sul CD
-&debian; ufficiale allora "Type" e "Creator" sono gi&agrave; impostati
-correttamente. I prossimi passaggi con <command>Creator-Changer</command>
-sono necessari solo se si sono scaricati i file immagine da uno dei
-mirror Debian.
+&debian; ufficiale allora <quote>Type</quote> e <quote>Creator</quote>
+sono già impostati correttamente. I prossimi passaggi con
+<command>Creator-Changer</command> sono necessari solo se si sono scaricati
+i file immagine da uno dei mirror Debian.
 
 </para>
 <orderedlist>
 <listitem><para>
 
-<!--Obtain
-<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
-and use it to open the <filename>root.bin</filename> file. -->
+<!--
+Obtain <ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
+and use it to open the <filename>root.bin</filename> file.
+-->
 
 Procurarsi
 <ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
@@ -72,23 +78,27 @@ e usarlo per aprire il file <filename>root.bin</filename>.
 </para></listitem>
 <listitem><para>
 
-<!--Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the
+<!--
+Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the
 Type to <userinput>DDim</userinput> (binary floppy image). The case is
-sensitive for these fields. -->
+sensitive for these fields.
+-->
 
-Modificare "Creator" con <userinput>ddsk</userinput> (Disk Copy) e
-"Type" con <userinput>DDim</userinput> (immagine di dischetto binaria).
-Questi campi considerano come differenti i caratteri in maiuscolo da
-quelli in minuscolo.
+Modificare <quote>Creator</quote> con <userinput>ddsk</userinput> (Disk
+Copy) e <quote>Type</quote> con <userinput>DDim</userinput> (immagine di
+dischetto binaria). Questi campi considerano come differenti i caratteri
+in maiuscolo da quelli in minuscolo.
 
 </para></listitem>
 <listitem><para>
 
-<!--<emphasis>Important:</emphasis> In the Finder, use <userinput>Get
+<!--
+<emphasis>Important:</emphasis> In the Finder, use <userinput>Get
 Info</userinput> to display the Finder information about the floppy
 image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so
 that MacOS will be unable to remove the boot blocks if the image is
-accidentally mounted. -->
+accidentally mounted.
+-->
 
 <emphasis>Importante:</emphasis> Nel Finder usare <userinput>Get
 Info</userinput> per visualizzare le informazioni Finder sull'immagine
@@ -99,12 +109,14 @@ che l'immagine venga accidentalmente montata.
 </para></listitem>
     <listitem><para>
 
-<!--Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it
+<!--
+Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it
 will very likely be there already, otherwise try
-<ulink url="&url-powerpc-diskcopy;"></ulink>. -->
+<ulink url="&url-powerpc-diskcopy;"></ulink>.
+-->
 
 Procurarsi <command>Disk Copy</command>; se si dispone di un sistema
-MacOS o del CD molto probabilmente &egrave; gi&agrave; presente, altrimenti si
+MacOS o del CD molto probabilmente è già presente, altrimenti si
 veda <ulink url="&url-powerpc-diskcopy;"></ulink>.
 
 </para></listitem>
@@ -116,31 +128,33 @@ Run <command>Disk Copy</command>, and select <menuchoice>
 </menuchoice>, then select the
 <emphasis>locked</emphasis> image file from the resulting dialog. It
 will ask you to insert a floppy, then ask if you really want to erase
-it. When done it should eject the floppy. -->
+it. When done it should eject the floppy.
+-->
 
 Lanciare <command>Disk Copy</command> e scegliere <menuchoice>
 <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem>
 </menuchoice>, poi selezionare il file immagine
 <emphasis>bloccato</emphasis> nella successiva finestra di dialogo.
-Prima verr&agrave; chiesto di inserire un dischetto e poi se si vuole davvero
+Prima verrà chiesto di inserire un dischetto e poi se si vuole davvero
 cancellarlo. Quando ha finito dovrebbe far uscire il dischetto.
 
 </para></listitem>
 </orderedlist>
-
    </sect3>
 
    <sect3>
-<!--<title>Writing Disk Images with <command>suntar</command></title>-->
+   <!-- <title>Writing Disk Images with <command>suntar</command></title> -->
    <title>Scrivere le immagini dei dischi con <command>suntar</command></title>
 <para>
 
 <orderedlist>
 <listitem><para>
 
-<!--Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;">
+<!--
+Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;">
 </ulink>. Start the <command>suntar</command> program and select
-<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu. -->
+<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu.
+-->
 
 Procurarsi <command>suntar</command> da
 <ulink url="&url-powerpc-suntar;"></ulink>. Avviare il programma
@@ -150,8 +164,10 @@ dal menu <userinput>Special</userinput>.
 </para></listitem>
 <listitem><para>
 
-<!--Insert the floppy disk as requested, then hit &enterkey; (start at
-sector 0). -->
+<!--
+Insert the floppy disk as requested, then hit &enterkey; (start at
+sector 0).
+-->
 
 Inserire, come richiesto, un dischetto e poi premere &enterkey; (inizia
 dal settore 0).
@@ -159,8 +175,10 @@ dal settore 0).
 </para></listitem>
 <listitem><para>
 
-<!--Select the <filename>root.bin</filename> file in the file-opening
-dialog. -->
+<!--
+Select the <filename>root.bin</filename> file in the file-opening
+dialog.
+-->
 
 Scegliere il file <filename>root.bin</filename> nella finestra di dialogo
 di selezione del file da aprire.
@@ -175,7 +193,7 @@ If there are any errors writing the floppy, simply toss that floppy and
 try another.
 -->
 
-Una volta che il dischetto &egrave; stato creato con successo, scegliere
+Una volta che il dischetto è stato creato con successo, scegliere
 <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem>
 </menuchoice>. Se si verificano degli errori durante la scrittura sul
 dischetto, buttare quel dischetto e provare con un altro.
@@ -183,13 +201,15 @@ dischetto, buttare quel dischetto e provare con un altro.
 </para></listitem>
 </orderedlist>
 
-<!--Before using the floppy you created, <emphasis>set the write protect
+<!--
+Before using the floppy you created, <emphasis>set the write protect
 tab</emphasis>!  Otherwise if you accidentally mount it in MacOS,
-MacOS will helpfully ruin it. -->
+MacOS will helpfully ruin it.
+-->
 
 Prima di usare i dischetti appena creati <emphasis>spostare la linguetta
 per proteggere il dischetto dalla scrittura</emphasis>! Altrimenti, se
-accidentalmente si monta il dischetto sotto MacOS, MacOS lo roviner&agrave;.
+accidentalmente si monta il dischetto sotto MacOS, MacOS lo rovinerà.
 
 </para>
    </sect3>
diff --git a/it/install-methods/install-methods.xml b/it/install-methods/install-methods.xml
index c887ba27a..0d145f851 100644
--- a/it/install-methods/install-methods.xml
+++ b/it/install-methods/install-methods.xml
@@ -1,9 +1,10 @@
 <!-- retain these comments for translator revision tracking -->
 <!-- original version: 11648 -->
 
+
 <chapter id="install-methods">
- <!-- <title>Obtaining System Installation Media</title> -->
- <title>Recupero dei supporti per il sistema di installazione</title>
+<!-- <title>Obtaining System Installation Media</title> -->
+<title>Recupero dei supporti per il sistema d'installazione</title>
 
 &official-cdrom.xml;
 &downloading-files.xml;
diff --git a/it/install-methods/install-tftp.xml b/it/install-methods/install-tftp.xml
index c0b24bcb8..b2ceb98a4 100644
--- a/it/install-methods/install-tftp.xml
+++ b/it/install-methods/install-tftp.xml
@@ -4,26 +4,30 @@
 
  <sect1 condition="supports-tftp" id="install-tftp">
  <!-- <title>Preparing Files for TFTP Net Booting</title> -->
- <title>Preparare i file per l'avvio TFTP da rete</title>
+ <title>Preparazione dei file per l'avvio TFTP da rete</title>
 <para>
 
-<!-- If your machine is connected to a local area network, you may be able
+<!--
+If your machine is connected to a local area network, you may be able
 to boot it over the network from another machine, using TFTP. If you
 intend to boot the installation system from another machine, the
 boot files will need to be placed in specific locations on that machine,
-and the machine configured to support booting of your specific machine. -->
+and the machine configured to support booting of your specific machine.
+-->
 
 Se la propria macchina è connessa a una rete locale allora è possibile
 avviarla tramite TFTP da un'altra macchina. Se si vuole
-avviare il sistema di installazione da un'altra macchina è necessario che
-i file di avvio siano contenuti in particolari directory di questa macchina
+avviare il sistema d'installazione da un'altra macchina è necessario che
+i file d'avvio siano contenuti in particolari directory di questa macchina
 e che sia configurata per gestire l'avvio della propria macchina.
 
 </para><para>
 
-<!-- You need to setup a TFTP server, and for many machines, a BOOTP server
+<!--
+You need to setup a TFTP server, and for many machines, a BOOTP server
 <phrase condition="supports-rarp">, or RARP server</phrase>
-<phrase condition="supports-dhcp">, or DHCP server</phrase>. -->
+<phrase condition="supports-dhcp">, or DHCP server</phrase>.
+-->
 
 È necessario attivare un server TFTP e, per più macchine, un server
 BOOTP<phrase condition="supports-rarp"> o un server
@@ -31,32 +35,40 @@ RARP</phrase><phrase condition="supports-dhcp"> o un server DHCP</phrase>.
 
 </para><para>
 
-<!-- <phrase condition="supports-rarp">The Reverse Address Resolution
+<!--
+<phrase condition="supports-rarp">The Reverse Address Resolution
 Protocol (RARP) is one way to tell your client what IP address to use for
-itself. Another way is to use the BOOTP protocol. </phrase> -->
+itself. Another way is to use the BOOTP protocol. </phrase>
+-->
 
 <phrase condition="supports-rarp">Il RARP (Reverse Address Resolution
 Protocol) è un metodo per comunicare ai client quale indirizzo IP usare.
 In alternativa è possibile usare il protocollo BOOTP. </phrase>
 
-<!-- <phrase condition="supports-bootp">BOOTP is an IP protocol that
+<!--
+<phrase condition="supports-bootp">BOOTP is an IP protocol that
 informs a computer of its IP address and where on the network to obtain
-a boot image. </phrase> -->
+a boot image. </phrase>
+-->
 
 <phrase condition="supports-bootp">BOOTP è un protocollo IP che comunica a
 un computer qual è il proprio indirizzo IP e dove può recuperare dalla rete
 un'immagine per l'avvio. </phrase>
 
-<!-- <phrase arch="m68k"> Yet another alternative exists on VMEbus
-systems: the IP address can be manually configured in boot ROM. </phrase> -->
+<!--
+<phrase arch="m68k"> Yet another alternative exists on VMEbus
+systems: the IP address can be manually configured in boot ROM. </phrase>
+-->
 
 <phrase arch="m68k">Sui sistemi VMEbus esiste un'altra alternativa:
 l'indirizzo IP può essere configurato manualmente nella ROM di avvio.
 </phrase>
 
-<!-- <phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration
+<!--
+<phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration
 Protocol) is a more flexible, backwards-compatible extension of BOOTP.
-Some systems can only be configured via DHCP. </phrase> -->
+Some systems can only be configured via DHCP. </phrase>
+-->
 
 <phrase condition="supports-dhcp">Il DHCP (Dynamic Host Configuration
 Protocol) è una estensione più flessibile ma compatibile all'indietro di
@@ -64,9 +76,11 @@ BOOTP. Alcuni sistemi possono essere configurati solo tramite DHCP. </phrase>
 
 </para><para arch="powerpc">
 
-<!-- For PowerPC, if you have a NewWorld Power Macintosh machine, it is a
+<!--
+For PowerPC, if you have a NewWorld Power Macintosh machine, it is a
 good idea to use DHCP instead of BOOTP.  Some of the latest machines
-are unable to boot using BOOTP. -->
+are unable to boot using BOOTP.
+-->
 
 Su PowerPC, se si possiede una macchina Power Macintosh NewWorld, è
 consigliabile usare DHCP anziché BOOTP. Alcune delle macchine più recenti
@@ -74,10 +88,12 @@ non sono capaci di fare l'avvio usando BOOTP.
 
 </para><para arch="alpha">
 
-<!-- Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM
+<!--
+Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM
 console will <emphasis>not</emphasis> use RARP to obtain its IP
 address, and therefore you must use BOOTP for net booting your
-Alpha<footnote> -->
+Alpha<footnote>
+-->
 
 Diversamente dall'Open Firmware presente sulle macchine Sparc e PowerPC, la
 console SRM <emphasis>non</emphasis> usa RARP per procurarsi l'indirizzo IP
@@ -86,10 +102,12 @@ Alpha<footnote>
 
 <para>
 
-<!-- Alpha systems can also be net-booted using the DECNet MOP (Maintenance
+<!--
+Alpha systems can also be net-booted using the DECNet MOP (Maintenance
 Operations Protocol), but this is not covered here.  Presumably, your
 local OpenVMS operator will be happy to assist you should you have
-some burning need to use MOP to boot Linux on your Alpha. -->
+some burning need to use MOP to boot Linux on your Alpha.
+-->
 
 I sistemi Alpha possono essere avviati dalla rete anche usando DECNet MOP
 (Maintenance Operations Protocol) ma questo metodo non è trattato in questo
@@ -98,15 +116,18 @@ prestare il proprio aiuto per poter usare MOP per l'avvio di Linux su Alpha.
 
 </para>
 
-<!-- </footnote>. You can also enter the IP configuration for network
-interfaces directly in the SRM console. -->
+<!--
+</footnote>. You can also enter the IP configuration for network
+interfaces directly in the SRM console.
+-->
 
 </footnote>. È anche possibile inserire la configurazione IP per le
 interfacce di rete direttamente dalla console SRM.
 
 </para><para arch="hppa">
 
-<!-- Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP.
+<!--
+Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP.
 There is an <classname>rbootd</classname> package available in Debian.
 -->
 
@@ -116,11 +137,13 @@ BOOTP, in Debian è disponibile il pacchetto <classname>rbootd</classname>.
 
 </para><para>
 
-<!-- The Trivial File Transfer Protocol (TFTP) is used to serve the boot
+<!--
+The Trivial File Transfer Protocol (TFTP) is used to serve the boot
 image to the client.  Theoretically, any server, on any platform,
 which implements these protocols, may be used.  In the examples in
 this section, we shall provide commands for SunOS 4.x, SunOS 5.x
-(a.k.a. Solaris), and GNU/Linux. -->
+(a.k.a. Solaris), and GNU/Linux.
+-->
 
 Il TFTP (Trivial File Transfer Protocol) è usato per fornire l'immagine di
 avvio al client. Teoricamente si può usare un qualsiasi server, su qualsiasi
@@ -130,11 +153,13 @@ Solaris) e GNU/Linux.
 
 <note arch="i386"><para>
 
-<!-- To use the Pre-boot Execution Environment (PXE) method of TFTP
+<!--
+To use the Pre-boot Execution Environment (PXE) method of TFTP
 booting, you will need a TFTP server with <userinput>tsize</userinput>
 support.  On a &debian; server, the <classname>atftpd</classname> and
 <classname>tftpd-hpa</classname> packages qualify; we recommend
-<classname>tftpd-hpa</classname>. -->
+<classname>tftpd-hpa</classname>.
+-->
 
 Per usare il metodo di avvio PXE (Pre-boot Execution Environment) di TFTP
 è necessario un server TFTP con supporto per <userinput>tsize</userinput>.
@@ -152,12 +177,14 @@ consiglia l'uso di quest'ultimo.
 
   <sect2 id="tftpd">
   <!-- <title>Enabling the TFTP Server</title> -->
-  <title>Attivare il server TFTP</title>
+  <title>Attivazione del server TFTP</title>
 <para>
 
-<!-- To get the TFTP server ready to go, you should first make sure that
+<!--
+To get the TFTP server ready to go, you should first make sure that
 <command>tftpd</command> is enabled.  This is usually enabled by having
-something like the following line in <filename>/etc/inetd.conf</filename>: -->
+something like the following line in <filename>/etc/inetd.conf</filename>:
+-->
 
 Per avere un server TFTP pronto all'uso è necessario assicurarsi che
 <command>tftpd</command> sia attivo. Di solito viene attivato da una riga
@@ -167,15 +194,18 @@ simile a questa in <filename>/etc/inetd.conf</filename>:
 tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot
 </screen></informalexample>
 
-<!-- Debian packages will in general set this up correctly by default when they
-are installed. -->
+<!--
+Debian packages will in general set this up correctly by default when they
+are installed.
+-->
 
 Solitamente i pacchetti Debian impostano correttamente il server durante
 l'installazione.
 
 </para><para>
 
-<!-- Look in that file and remember the directory which is used as the
+<!--
+Look in that file and remember the directory which is used as the
 argument of <command>in.tftpd</command>; you'll need that below.  The
 <userinput>-l</userinput> argument enables some versions of
 <command>in.tftpd</command> to log all requests to the system logs;
@@ -185,7 +215,8 @@ running <command>inetd</command> process that the file has changed.
 On a Debian machine, run <userinput>/etc/init.d/inetd
 reload</userinput>; on other machines,
 find out the process ID for <command>inetd</command>, and run
-<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. -->
+<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>.
+-->
 
 Cercare all'interno di questo file la directory usata come argomento di
 <command>in.tftpd</command> e prenderne nota, sarà necessaria in seguito.
@@ -201,9 +232,11 @@ processo <command>inetd</command> ed eseguire <userinput>kill -HUP
 
 </para><para arch="mips">
 
-<!-- If you intend to install Debian on an SGI machine and your TFTP server
+<!--
+If you intend to install Debian on an SGI machine and your TFTP server
 is a GNU/Linux box running Linux 2.4, you'll need to set the following on
-your server: -->
+your server:
+-->
 
 Se si intende installare Debian su una macchina SGI e il server TFTP è su una
 macchina GNU/Linux con Linux 2.4 è necessario eseguire comando seguente sul
@@ -213,11 +246,13 @@ server:
 # echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc
 </screen></informalexample>
 
-<!-- to turn off Path MTU discovery, otherwise the SGI's PROM can't
+<!--
+to turn off Path MTU discovery, otherwise the SGI's PROM can't
 download the kernel. Furthermore, make sure TFTP packets are sent from
 a source port no greater than 32767, or the download will stall after
 the first packet.  Again, it's Linux 2.4.X tripping this bug in the
-PROM, and you can avoid it by setting -->
+PROM, and you can avoid it by setting
+-->
 
 per disattivare il Path MTU discovery, in caso contrario la PROM delle SGI
 non può scaricare il kernel. Inoltre, assicurarsi che i pacchetti TFTP siano
@@ -229,7 +264,9 @@ aggirato con Linux 2.4.X eseguendo il comando seguente
 # echo "2048 32767" &gt; /proc/sys/net/ipv4/ip_local_port_range
 </screen></informalexample>
 
-<!-- to adjust the range of source ports the Linux TFTP server uses. -->
+<!--
+to adjust the range of source ports the Linux TFTP server uses.
+-->
 
 per regolare l'intervallo delle porte sorgente usate sul server TFTP Linux.
 
@@ -241,13 +278,15 @@ per regolare l'intervallo delle porte sorgente usate sul server TFTP Linux.
   <title>Posizionamento delle immagini TFTP</title>
 <para>
 
-<!-- Next, place the TFTP boot image you need, as found in
+<!--
+Next, place the TFTP boot image you need, as found in
 <xref linkend="where-files"/>, in the <command>tftpd</command>
 boot image directory.  Generally, this directory will be
 <filename>/tftpboot</filename>.  You'll have to make a link from that
 file to the file which <command>tftpd</command> will use for booting a
 particular client.  Unfortunately, the file name is determined by the
-TFTP client, and there are no strong standards. -->
+TFTP client, and there are no strong standards.
+-->
 
 Spostare le immagini TFTP di cui si ha bisogno (come descritto in
 <xref linkend="where-files"/>) nella directory delle immagini di avvio per
@@ -259,12 +298,14 @@ esiste uno standard.
 
 </para><para arch="powerpc">
 
-<!-- On NewWorld Power Macintosh machines, you will need to set up the
+<!--
+On NewWorld Power Macintosh machines, you will need to set up the
 <command>yaboot</command> boot loader as the TFTP boot image.
 <command>Yaboot</command> will then retrieve the kernel and RAMdisk
 images via TFTP itself.  For net booting, use the
 <filename>yaboot-netboot.conf</filename>.  Just rename this to
-<filename>yaboot.conf</filename> in the TFTP directory. -->
+<filename>yaboot.conf</filename> in the TFTP directory.
+-->
 
 Sulle macchine Power Machintosh NewWorld è necessario configurare il
 bootloader <command>yaboot</command> come immagine di avvio TFTP. Sarà poi
@@ -275,11 +316,13 @@ TFTP e poi rinominarlo in <filename>yaboot.conf</filename>.
 
 </para><para arch="i386">
 
-<!-- For PXE booting, everything you should need is set up in the
+<!--
+For PXE booting, everything you should need is set up in the
 <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this
 tarball into the <command>tftpd</command> boot image directory. Make sure
 your dhcp server is configured to pass <filename>/pxelinux.0</filename>
-to <command>tftpd</command> as the filename to boot. -->
+to <command>tftpd</command> as the filename to boot.
+-->
 
 Per l'avvio PXE tutte le operazioni necessarie sono già state fatte in
 <filename>netboot/netboot.tar.gz</filename>. Estrarre questo tarball nella
@@ -289,12 +332,14 @@ come file da avviare a <command>tftpd</command>.
 
 </para><para arch="ia64">
 
-<!-- For PXE booting, everything you should need is set up in the
+<!--
+For PXE booting, everything you should need is set up in the
 <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this
 tarball into the <command>tftpd</command> boot image directory. Make sure
 your dhcp server is configured to pass
 <filename>/debian-installer/ia64/elilo.efi</filename>
-to <command>tftpd</command> as the filename to boot. -->
+to <command>tftpd</command> as the filename to boot.
+-->
 
 Per l'avvio PXE tutte le operazioni necessarie sono già state fatte in
 <filename>netboot/netboot.tar.gz</filename>. Estrarre questo tarball nella
@@ -310,12 +355,14 @@ a <command>tftpd</command>.
    <title>Immagini TFTP per DECstation</title>
 <para>
 
-<!-- For DECstations, there are tftpimage files for each subarchitecture,
+<!--
+For DECstations, there are tftpimage files for each subarchitecture,
 which contain both kernel and installer in one file. The naming
 convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img.
 Copy the tftpimage file you would like to use to
 <userinput>/tftpboot/tftpboot.img</userinput> if you work with the
-example BOOTP/DHCP setups described above. -->
+example BOOTP/DHCP setups described above.
+-->
 
 Per le DECstation esistono più file tftpimage, uno per ciascuna
 sottoarchitettura, che contengono sia il kernel che l'installatore.
@@ -327,13 +374,15 @@ il file tftpimage che si vuole usare come
 
 </para><para>
 
-<!-- The DECstation firmware boots by TFTP with the command <userinput>boot
+<!--
+The DECstation firmware boots by TFTP with the command <userinput>boot
 <replaceable>#</replaceable>/tftp</userinput>, where
 <replaceable>#</replaceable> is the number of the TurboChannel device
 from which to boot. On most DECstations this is <quote>3</quote>.  If the
 BOOTP/DHCP server does not supply the filename or you need to pass
 additional parameters, they can optionally be appended with the
-following syntax: -->
+following syntax:
+-->
 
 Il firmware DECstation fa l'avvio del sistema con TFTP usando il comando
 <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, dove
@@ -344,17 +393,20 @@ passare altri parametri, si possono aggiungere usando questa sintassi:
 
 </para><para>
 
-<!-- <userinput>boot #/tftp/filename param1=value1 param2=value2
-...</userinput> -->
+<!--
+<userinput>boot #/tftp/filename param1=value1 param2=value2 ...</userinput>
+-->
 
 <userinput>boot #/tftp/nomefile param1=valore1 param2=valore2 ...</userinput>
 
 </para><para>
 
-<!-- Several DECstation firmware revisions show a problem with regard to
+<!--
+Several DECstation firmware revisions show a problem with regard to
 net booting: the transfer starts, but after some time it stops with
 an <computeroutput>a.out err</computeroutput>. This can have several
-reasons: -->
+reasons:
+-->
 
 Parecchie versioni del firmware DECstation hanno un problema relativo
 all'avvio da rete: il trasferimento inizia ma dopo un po' si ferma restituendo
@@ -364,7 +416,8 @@ cause:
 <orderedlist>
 <listitem><para>
 
-<!-- The firmware does not respond to ARP requests during a TFTP
+<!--
+The firmware does not respond to ARP requests during a TFTP
 transfer. This leads to an ARP timeout and the transfer stops.  The
 solution is to add the MAC address of the Ethernet card in the
 DECstation statically to the ARP table of the TFTP server.  This is
@@ -373,7 +426,8 @@ done by running <userinput>arp -s
 <replaceable>MAC-address</replaceable></userinput> as root on the
 machine acting as TFTP server. The MAC-address of the DECstation can
 be read out by entering <command>cnfg</command> at the DECstation
-firmware prompt. -->
+firmware prompt.
+-->
 
 Il firmware non risponde alle richieste ARP durante i trasferimenti TFTP.
 Questo può comportare un timeout ARP e il blocco del trasferimento. La
@@ -388,8 +442,9 @@ letto inserendo <command>cnfg</command> al prompt del firmware DECstation.
 </para></listitem>
 <listitem><para>
 
-<!-- The firmware has a size limit on the files that can be booted
-by TFTP. -->
+<!--
+The firmware has a size limit on the files that can be booted by TFTP.
+-->
 
 Il firmware ha un limite sulla dimensione dei file che possono essere avviati
 tramite TFTP.
@@ -397,10 +452,12 @@ tramite TFTP.
 </para></listitem>
 </orderedlist>
 
-<!-- There are also firmware revisions that cannot boot via TFTP at all. An
+<!--
+There are also firmware revisions that cannot boot via TFTP at all. An
 overview about the different firmware revisions can be found at the
 NetBSD web pages:
-<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>. -->
+<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>.
+-->
 
 Ci sono delle versioni del firmware che non possono essere assolutamente
 avviate tramite TFTP. Una panoramica sulle varie versioni del firmware può
@@ -415,7 +472,8 @@ essere trovata nelle pagine web di NetBSD:
    <title>Avvio TFTP di macchine Alpha</title>
 <para>
 
-<!-- On Alpha, you must specify the filename (as a relative path to the
+<!--
+On Alpha, you must specify the filename (as a relative path to the
 boot image directory) using the <userinput>-file</userinput> argument
 to the SRM <userinput>boot</userinput> command, or by setting the
 <userinput>BOOT_FILE</userinput> environment variable.  Alternatively,
@@ -423,7 +481,8 @@ the filename can be given via BOOTP (in ISC <command>dhcpd</command>,
 use the <userinput>filename</userinput> directive).  Unlike Open
 Firmware, there is <emphasis>no default filename</emphasis> on SRM, so
 you <emphasis>must</emphasis> specify a filename by either one of
-these methods. -->
+these methods.
+-->
 
 Su Alpha si deve specificare il nome del file (come percorso relativo alla
 directory con l'immagine di avvio) usando l'opzione
@@ -444,14 +503,16 @@ appena descritti.
    <title>Avvio TFTP di macchine SPARC</title>
 <para>
 
-<!-- SPARC architectures for instance use the subarchitecture names, such
+<!--
+SPARC architectures for instance use the subarchitecture names, such
 as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the
 architecture is left blank, so the file the client looks for is just
 <filename>client-ip-in-hex</filename>.  Thus, if your system
 subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename
 would be <filename>C0A80103.SUN4C</filename>. An easy way to determine
 this is to enter the following command in a shell (assuming the
-machine's intended IP is 10.0.0.4). -->
+machine's intended IP is 10.0.0.4).
+-->
 
 Le architetture SPARC usano dei nomi per le sottoarchitetture, per esempio
 <quote>SUN4M</quote> o <quote>SUN4C</quote> e in alcuni casi non c'è il nome
@@ -467,9 +528,11 @@ sia 10.0.0.4).
 $ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4
 </screen></informalexample>
 
-<!-- This will spit out the IP in hexadecimal; to get to the correct
+<!--
+This will spit out the IP in hexadecimal; to get to the correct
 filename, you will need to change all letters to uppercase and
-if necessary append the subarchitecture name. -->
+if necessary append the subarchitecture name.
+-->
 
 Questo comando restituisce l'IP in esadecimale; per ottenere il corretto
 nome del file è necessario cambiare tutte le lettere in maiuscole e, se
@@ -477,10 +540,12 @@ necessario, aggiungere il nome della sottoarchitettura.
 
 </para><para>
 
-<!-- You can also force some sparc systems to look for a specific file name
+<!--
+You can also force some sparc systems to look for a specific file name
 by adding it to the end of the OpenPROM boot command, such as
 <userinput>boot net my-sparc.image</userinput>. This must still reside
-in the directory that the TFTP server looks in. -->
+in the directory that the TFTP server looks in.
+-->
 
 È anche possibile forzare alcuni sistemi sparc a cercare un particolare file
 aggiungendone il nome alla fine del comando boot di OpenPROM, per esempio
@@ -495,19 +560,23 @@ nella directory in cui il server TFTP ricerca i file.
    <title>Avvio TFTP di macchine BVM/Motorola</title>
 <para>
 
-<!-- For BVM and Motorola VMEbus systems copy the files
-&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. -->
+<!--
+For BVM and Motorola VMEbus systems copy the files
+&bvme6000-tftp-files; to <filename>/tftpboot/</filename>.
+-->
 
 Per i sistemi BVM e Motorola VMEbus copiare i file &bvme6000-tftp-files;
 in <filename>/tftpboot/</filename>.
 
 </para><para>
 
-<!-- Next, configure your boot ROMs or BOOTP server to initially load the
+<!--
+Next, configure your boot ROMs or BOOTP server to initially load the
 <filename>tftplilo.bvme</filename> or
 <filename>tftplilo.mvme</filename> files from the TFTP server.  Refer
 to the <filename>tftplilo.txt</filename> file for your subarchitecture
-for additional system-specific configuration information. -->
+for additional system-specific configuration information.
+-->
 
 Poi configurare le ROM di avvio o il server BOOTP per caricare inizialmente i
 file <filename>tftplilo.bvme</filename> o <filename>tftplilo.mvme</filename>
diff --git a/it/install-methods/ipl-tape.xml b/it/install-methods/ipl-tape.xml
index c81d072fe..0ab3ba051 100644
--- a/it/install-methods/ipl-tape.xml
+++ b/it/install-methods/ipl-tape.xml
@@ -4,11 +4,11 @@
 
  <sect1 arch="s390" id="ipl-tape">
  <!-- <title>Creating an IPL tape</title> -->
- <title>Creare un nastro IPL</title>
-
+ <title>Creazione un nastro IPL</title>
 <para>
 
-<!-- If you can't boot (IPL) from the CD-ROM and you are not using VM
+<!--
+If you can't boot (IPL) from the CD-ROM and you are not using VM
 you need to create an IPL tape first. This is described in section
 3.4.3 in the
 <ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">
@@ -19,12 +19,13 @@ need to write to the tape are (in this order):
 <filename>parmfile.debian</filename> and
 <filename>initrd.debian</filename>. The files can be downloaded
 from the <filename>tape</filename> sub-directory, see
-<xref linkend="where-files"/>, -->
+<xref linkend="where-files"/>,
+-->
 
 Se non è possibile avviare (IPL) da CD-ROM e non si usa VM è necessario
 per prima cosa creare un nastro IPL. Questa procedura è descritta nella
-sezione 3.4.3 del Redbook
-<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">Linux
+sezione 3.4.3 del Redbook <ulink
+url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">Linux
 for IBM eServer zSeries and S/390: Distributions</ulink>. I file che è
 necessario scrivere sul nastro sono (nell'ordine):
 <filename>kernel.debian</filename>, <filename>parmfile.debian</filename>
diff --git a/it/install-methods/official-cdrom.xml b/it/install-methods/official-cdrom.xml
index c5d145dc9..0dd4f68f9 100644
--- a/it/install-methods/official-cdrom.xml
+++ b/it/install-methods/official-cdrom.xml
@@ -5,10 +5,10 @@
  <sect1 id="official-cdrom">
  <!-- <title>Official &debian; CD-ROM Sets</title> -->
  <title>Set ufficiale di CD-ROM &debian;</title>
-
 <para>
 
-<!-- By far the easiest way to install &debian; is from an Official
+<!--
+By far the easiest way to install &debian; is from an Official
 Debian CD-ROM Set. You can buy a set from a vendor (see the
 <ulink url="&url-debian-cd-vendors;">CD vendors page</ulink>).
 You may also download the CD-ROM images from a Debian mirror and make
@@ -21,7 +21,8 @@ the files most people need are there on the CD. Although a full set of
 binary packages requires several CDs, it is unlikely you will need
 packages on the third CD and above. You may also consider using the
 DVD version, which saves a lot of space on your shelf and you avoid
-the CD shuffling marathon. -->
+the CD shuffling marathon.
+-->
 
 Da sempre il modo più semplice per installare &debian; è usare un set
 ufficiale di CD-ROM Debian. Si può comprare il set da uno dei distributori
@@ -41,39 +42,29 @@ e di evitare fastidiosi sparpagliamenti di CD.
 
 </para><para>
 
-<!-- If your machine doesn't support CD booting, but you do have a CD set,
-you can use an alternative strategy such as -->
+<!--
+If your machine doesn't support CD booting, but you do have a CD set,
+you can use an alternative strategy such as 
+<phrase condition="supports-floppy-boot">floppy disk,</phrase>
+<phrase arch="s390">tape, emulated tape,</phrase>
+<phrase condition="bootable-disk">hard disk,</phrase>
+<phrase condition="bootable-usb">usb stick,</phrase>
+<phrase condition="supports-tftp">net boot,</phrase>
+or manually loading the kernel from the CD to initially boot the
+system installer. The files you need for booting by another means are
+also on the CD; the Debian network archive and CD folder organization
+are identical. So when archive file paths are given below for
+particular files you need for booting, look for those files in the
+same directories and subdirectories on your CD.
+-->
 
 Se la propria macchina non supporta l'avvio da CD ma si possiede un set
 di CD è possibile usare una strategia alternativa come
-
-<!-- <phrase condition="supports-floppy-boot">floppy disk,</phrase> -->
-
 <phrase condition="supports-floppy-boot">dischetti,</phrase>
-
-<!-- <phrase arch="s390">tape, emulated tape,</phrase> -->
-
 <phrase arch="s390">nastro, nastro emulato,</phrase>
-
-<!-- <phrase condition="bootable-disk">hard disk,</phrase> -->
-
 <phrase condition="bootable-disk">disco fisso,</phrase>
-
-<!-- <phrase condition="bootable-usb">usb stick,</phrase> -->
-
 <phrase condition="bootable-usb">penna USB,</phrase>
-
-<!-- <phrase condition="supports-tftp">net boot,</phrase> -->
-
 <phrase condition="supports-tftp">avvio da rete,</phrase>
-
-<!-- or manually loading the kernel from the CD to initially boot the
-system installer. The files you need for booting by another means are
-also on the CD; the Debian network archive and CD folder organization
-are identical. So when archive file paths are given below for
-particular files you need for booting, look for those files in the
-same directories and subdirectories on your CD. -->
-
 oppure caricare manualmente il kernel dal CD per avviare il sistema di
 installazione. Sul CD ci sono anche i file necessari per l'avvio da altri
 supporti. La struttura dell'archivio Debian in rete e quella delle cartelle
@@ -83,44 +74,35 @@ o sottodirectory sul proprio CD.
 
 </para><para>
 
-<!-- Once the installer is booted, it will be able to obtain all the other
-files it needs from the CD. -->
+<!--
+Once the installer is booted, it will be able to obtain all the other
+files it needs from the CD.
+-->
 
 Una volta che l'installatore è partito, è in grado di recuperare tutti
 gli altri file necessari dal CD.
 
 </para><para>
 
-<!-- If you don't have a CD set, then you will need to download the
-installer system files and place them on the -->
+<!--
+If you don't have a CD set, then you will need to download the
+installer system files and place them on the
+<phrase arch="s390">installation tape</phrase>
+<phrase condition="supports-floppy-boot">floppy disk or</phrase>
+<phrase condition="bootable-disk">hard disk or</phrase>
+<phrase condition="bootable-usb">usb stick or</phrase>
+<phrase condition="supports-tftp">a connected computer</phrase>
+so they can be used to boot the installer.
+-->
 
 Se non si possiede un set di CD è necessario scaricare i file
 dell'installatore e copiarli su
-
-<!-- <phrase arch="s390">installation tape</phrase> -->
-
 <phrase arch="s390">un nastro di installazione,</phrase>
-
-<!-- <phrase condition="supports-floppy-boot">floppy disk or</phrase> -->
-
 <phrase condition="supports-floppy-boot">un dischetto,</phrase>
-
-<!-- <phrase condition="bootable-disk">hard disk or</phrase> -->
-
 <phrase condition="bootable-disk">un disco fisso,</phrase>
-
-<!-- <phrase condition="bootable-usb">usb stick or</phrase> -->
-
 <phrase condition="bootable-usb">una penna usb,</phrase>
-
-<!-- <phrase condition="supports-tftp">a connected computer</phrase> -->
-
 <phrase condition="supports-tftp">un computer in rete,</phrase>
-
-<!-- so they can be used to boot the installer. -->
-
 in modo da essere usati per avviare l'installatore.
 
 </para>
-
  </sect1>
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
diff --git a/it/install-methods/tftp/dhcp.xml b/it/install-methods/tftp/dhcp.xml
index dfb6bdbc3..06d5aa332 100644
--- a/it/install-methods/tftp/dhcp.xml
+++ b/it/install-methods/tftp/dhcp.xml
@@ -4,14 +4,15 @@
 
   <sect2 condition="supports-dhcp" id="dhcpd">
   <!-- <title>Setting up a DHCP server</title> -->
-  <title>Attivare un server DHCP</title>
-
+  <title>Attivazione di un server DHCP</title>
 <para>
 
-<!-- One free software DHCP server is ISC <command>dhcpd</command>.
+<!--
+One free software DHCP server is ISC <command>dhcpd</command>.
 In &debian;, this is available in the <classname>dhcp</classname>
 package. Here is a sample configuration file for it (usually
-<filename>/etc/dhcpd.conf</filename>): -->
+<filename>/etc/dhcpd.conf</filename>):
+-->
 
 Un server DHCP libero è <command>dhcpd</command> di ISC. In &debian; è
 disponibile nel pacchetto <classname>dhcp</classname>. Questo è un esempio
@@ -40,33 +41,39 @@ host clientname {
 }
 </screen></informalexample>
 
-<!-- Note: the new (and preferred) <classname>dhcp3</classname> package uses
-<filename>/etc/dhcp3/dhcpd.conf</filename>. -->
+<!--
+Note: the new (and preferred) <classname>dhcp3</classname> package uses
+<filename>/etc/dhcp3/dhcpd.conf</filename>.
+-->
 
 Nota: il nuovo (e da preferire) pacchetto <classname>dhcp3</classname> usa il
 file <filename>/etc/dhcp3/dhcpd.conf</filename>.
 
 </para><para>
 
-<!-- In this example, there is one server
+<!--
+In this example, there is one server
 <replaceable>servername</replaceable> which performs all of the work
 of DHCP server, TFTP server, and network gateway.  You will almost
 certainly need to change the domain-name options, as well as the
 server name and client hardware address.  The
 <replaceable>filename</replaceable> option should be the name of the
-file which will be retrieved via TFTP. -->
+file which will be retrieved via TFTP.
+-->
 
 In questo esempio c'è una macchina <replaceable>servername</replaceable>
 che fa da server DHCP, da server TFTP e da gateway di rete. Sicuramente è
-necessario cambiare le opzioni domain-name e anche il nome del server e
+necessario cambiare le opzioni domain-name, il nome del server e anche
 l'indirizzo hardware del client. Il valore dell'opzione
 <replaceable>filename</replaceable> deve essere il nome del file che
 verrà recuperato tramite TFTP.
 
 </para><para>
 
-<!-- After you have edited the <command>dhcpd</command> configuration file,
-restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. -->
+<!--
+After you have edited the <command>dhcpd</command> configuration file,
+restart it with <userinput>/etc/init.d/dhcpd restart</userinput>.
+-->
 
 Dopo aver modificato il file di configurazione di <command>dhcpd</command>
 riavviarlo con <userinput>/etc/init.d/dhcpd restart</userinput>.
@@ -76,11 +83,12 @@ riavviarlo con <userinput>/etc/init.d/dhcpd restart</userinput>.
    <sect3 arch="i386">
    <!-- <title>Enabling PXE Booting in the DHCP configuration</title> -->
    <title>Abilitare l'avvio PXE nella configurazione di DHCP</title>
-
 <para>
 
-<!-- Here is another example for a <filename>dhcp.conf</filename> using the
-Pre-boot Execution Environment (PXE) method of TFTP. -->
+<!--
+Here is another example for a <filename>dhcp.conf</filename> using the
+Pre-boot Execution Environment (PXE) method of TFTP.
+-->
 
 Questo è un altro esempio di <filename>dhcp.conf</filename> che usa il
 metodo PXE (Pre-boot Execution Environment) di TFTP.
@@ -115,9 +123,11 @@ group {
 }
 </screen></informalexample>
 
-<!-- Note that for PXE booting, the client filename
+<!--
+Note that for PXE booting, the client filename
 <filename>pxelinux.0</filename> is a boot loader, not a kernel image
-(see <xref linkend="tftp-images"/> below). -->
+(see <xref linkend="tftp-images"/> below).
+-->
 
 Notare che con l'avvio PXE, il nome del file client
 <filename>pxelinux.0</filename> è il bootloader, non l'immagine del kernel
diff --git a/it/install-methods/tftp/rarp.xml b/it/install-methods/tftp/rarp.xml
index 679186fb1..02c81b8b9 100644
--- a/it/install-methods/tftp/rarp.xml
+++ b/it/install-methods/tftp/rarp.xml
@@ -4,37 +4,34 @@
 
   <sect2 condition="supports-rarp" id="tftp-rarp">
   <!-- <title>Setting up RARP server</title> -->
-  <title>Attivare un server RARP</title>
-
+  <title>Attivazione di un server RARP</title>
 <para>
 
-<!-- To setup RARP, you need to know the Ethernet address (a.k.a. the MAC
+<!--
+To setup RARP, you need to know the Ethernet address (a.k.a. the MAC
 address) of the client computers to be installed.
-If you don't know this information, you can -->
+If you don't know this information, you can
+<phrase arch="sparc"> pick it off the initial OpenPROM boot messages,
+use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase>
+boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the
+command <userinput>/sbin/ifconfig eth0</userinput>.
+-->
 
 Per impostare RARP è necessario conoscere l'indirizzo Ethernet (noto anche
 come indirizzo MAC) dei computer client da installare. Se non si conoscono
 queste informazioni è possibile
-
-<!-- <phrase arch="sparc"> pick it off the initial OpenPROM boot messages,
-use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> -->
-
 <phrase arch="sparc">leggerlo nei primi messaggi durante l'avvio di OpenPROM,
 usare il comando <userinput>.enet-addr</userinput> di OpenBoot oppure</phrase>
-
-<!--
-boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the
-command <userinput>/sbin/ifconfig eth0</userinput>.
--->
-
 avviare in modalità <quote>Ripristino</quote> (p.e. da un dischetto di
 ripristino) e usare il comando <userinput>/sbin/ifconfig eth0</userinput>.
 
 </para><para>
 
-<!-- On a RARP server system using a Linux 2.2.x kernel,
+<!--
+On a RARP server system using a Linux 2.2.x kernel,
 you need to populate the kernel's RARP table.
-To do this, run the following commands: -->
+To do this, run the following commands:
+-->
 
 Su un sistema con Linux 2.2.x e un server RARP è necessario popolare la
 tabella RARP del kernel. Per farlo usare i seguenti comandi:
@@ -49,7 +46,9 @@ tabella RARP del kernel. Per farlo usare i seguenti comandi:
 <replaceable>client-enet-addr</replaceable></userinput>
 </screen></informalexample>
 
-<!-- If you get -->
+<!--
+If you get
+-->
 
 Se si ottiene
 
@@ -57,9 +56,11 @@ Se si ottiene
 SIOCSRARP: Invalid argument
 </screen></informalexample>
 
-<!-- you probably need to load the RARP kernel module or else recompile the
+<!--
+you probably need to load the RARP kernel module or else recompile the
 kernel to support RARP.  Try <userinput>modprobe rarp</userinput> and
-then try the <command>rarp</command> command again. -->
+then try the <command>rarp</command> command again.
+-->
 
 probabilmente si deve caricare il modulo del kernel RARP oppure
 ricompilare il kernel inserendo il supporto RARP. Eseguire
@@ -68,11 +69,13 @@ comando <command>rarp</command>.
 
 </para><para>
 
-<!-- On a RARP server system using a Linux 2.4.x kernel,
+<!--
+On a RARP server system using a Linux 2.4.x kernel,
 there is no RARP module, and
 you should instead use the <command>rarpd</command> program.  The
 procedure is similar to that used under SunOS in the following
-paragraph. -->
+paragraph.
+-->
 
 Su un sistema con Linux 2.4.x e un server RARP non esiste il modulo RARP e
 al suo posto si deve usare il programma <command>rarpd</command>. La
@@ -81,13 +84,15 @@ paragrafo.
 
 </para><para>
 
-<!-- Under SunOS, you need to ensure that the Ethernet hardware address for
+<!--
+Under SunOS, you need to ensure that the Ethernet hardware address for
 the client is listed in the <quote>ethers</quote> database (either in the
 <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the
 <quote>hosts</quote> database. Then you need to start the RARP daemon.  In SunOS
 4, issue the command (as root):
 <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use
-<userinput>/usr/sbin/rarpd -a</userinput>. -->
+<userinput>/usr/sbin/rarpd -a</userinput>.
+-->
 
 Sotto SunOS ci si deve assicurare che l'indirizzo Ethernet del
 client sia elencato nel database <quote>ethers</quote> (nel file