Update italian d-i manual

5 files changed, 26 insertions, 20 deletions

diff --git a/it/preparing/bios-setup/arm.xml b/it/preparing/bios-setup/arm.xml
index 92eece206..2a13792f0 100644
--- a/it/preparing/bios-setup/arm.xml
+++ b/it/preparing/bios-setup/arm.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 69182 -->
+<!-- original version: 69220 -->
 
   <sect2 arch="arm" id="arm-firmware-overview">
   <!-- <title>ARM firmware</title> -->
@@ -109,7 +109,7 @@ To avoid conflicts with existing officially-assigned MAC addresses,
 there is an address pool which is reserved for so-called
 <quote>locally administered</quote> addresses. It is defined by
 the value of two specific bits in the first byte of the address (the
-article "MAC address" in the English language Wikipedia gives a 
+article <quote>MAC address</quote> in the English language Wikipedia gives a 
 good explanation). In practice this means that e.g. any address starting
 with hexadecimal ca (such as ca:ff:ee:12:34:56) can be used as a locally
 administered address. 
@@ -156,7 +156,8 @@ permanente la modifica.
 On some systems with older u-boot versions there can be problems with
 properly relocating the Linux kernel, the initial ramdisk and the
 device-tree blob in memory during the boot process.  In this case,
-u-boot shows the message "Starting kernel ...", but the system freezes
+u-boot shows the message <quote>Starting kernel ...</quote>,
+but the system freezes
 afterwards without further output.  These issues have been solved with
 newer u-boot versions from v2014.07 onwards.
 -->
@@ -180,7 +181,7 @@ the fix requires an additional environment variable (bootm_size) to be
 set, which u-boot does automatically only on fresh installations
 without existing environment data.  It is possible to manually set
 bootm_size to the new u-boot's default value by running the command
-"env default bootm_size; saveenv" at the u-boot prompt.
+<quote>env default bootm_size; saveenv</quote> at the u-boot prompt.
 -->
 
 Questo problema potrebbe comunque verificarsi anche se il sistema era
@@ -198,8 +199,8 @@ promnpt di u-boot.
 
 <!--
 Another possibility to circumvent relocation-related problems is to
-run the command "setenv fdt_high ffffffff; setenv initrd_high
-0xffffffff; saveenv" at the u-boot prompt to completely disable
+run the command <quote>setenv fdt_high ffffffff; setenv initrd_high
+0xffffffff; saveenv</quote> at the u-boot prompt to completely disable
 the relocation of the initial ramdisk and the device-tree blob.          
 -->
 
diff --git a/it/preparing/minimum-hardware-reqts.xml b/it/preparing/minimum-hardware-reqts.xml
index 672a4813d..6d4aa669b 100644
--- a/it/preparing/minimum-hardware-reqts.xml
+++ b/it/preparing/minimum-hardware-reqts.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 68697 -->
+<!-- original version: 69222 -->
 
  <sect1 id="minimum-hardware-reqts">
  <!-- <title>Meeting Minimum Hardware Requirements</title> -->
@@ -56,7 +56,7 @@ desktop.
 <thead>
 <row>
   <entry><!-- Install Type -->Tipologia d'installazione</entry>
-  <entry><!-- RAM (minimal) -->RAM (minima)</entry>
+  <entry><!-- RAM (minimum) -->RAM (minima)</entry>
   <entry><!-- RAM (recommended) -->RAM (raccomandata)</entry>
   <entry><!-- Hard Drive -->Spazio su disco</entry>
 </row>
@@ -65,14 +65,14 @@ desktop.
 <tbody>
 <row>
   <entry><!-- No desktop -->Senza desktop</entry>
-  <entry>64 megabyte</entry>
-  <entry>256 megabyte</entry>
-  <entry>1 gigabyte</entry>
+  <entry><!-- 128 megabytes -->128 megabyte</entry>
+  <entry><!-- 512 megabytes -->512 megabyte</entry>
+  <entry><!-- 2 gigabytes -->2 gigabyte</entry>
 </row><row arch="not-s390">
   <entry><!-- With Desktop -->Con desktop</entry>
-  <entry>128 megabyte</entry>
-  <entry>512 megabyte</entry>
-  <entry><!-- 5 gigabytes -->5 gigabyte</entry>
+  <entry><!-- 256 megabytes -->256 megabyte</entry>
+  <entry><!-- 1 gigabytes -->1 gigabyte</entry>
+  <entry><!-- 10 gigabytes -->5 gigabyte</entry>
 </row>
 
 </tbody></tgroup></table>
diff --git a/it/preparing/needed-info.xml b/it/preparing/needed-info.xml
index 6834a62ec..7d104614f 100644
--- a/it/preparing/needed-info.xml
+++ b/it/preparing/needed-info.xml
@@ -77,7 +77,12 @@ Contiene informazioni utili sulla configurazione o l'utilizzo dell'hardware.
 <itemizedlist arch="x86;sparc;mips;mipsel">
 <listitem arch="x86"><para>
 
+<!--
 <ulink url="&url-debian-wiki-hardware;">The Debian Wiki hardware page</ulink>
+-->
+
+<ulink url="&url-debian-wiki-hardware;">Pagina del wiki Debian
+sull'hardware</ulink>
 
 </para></listitem>
 
diff --git a/it/preparing/non-debian-partitioning.xml b/it/preparing/non-debian-partitioning.xml
index 618a56ee5..7c6d3ca10 100644
--- a/it/preparing/non-debian-partitioning.xml
+++ b/it/preparing/non-debian-partitioning.xml
@@ -96,7 +96,7 @@ way before moving a wall or you risk destroying it.
 -->
 
 In generale, modificare una partizione che contiene già un file system
-distruggerà qualsiasi informazione preesistente. Perciò di dovrebbe sempre
+distruggerà qualsiasi informazione preesistente. Perciò si dovrebbe sempre
 fare il backup prima di procedere a qualunque ripartizionamento. Continuando
 ad usare l'analogia della casa, è opportuno spostare tutti i mobili prima
 di procedere alla demolizione e ricostruzione di un muro, altrimenti si
diff --git a/it/preparing/pre-install-bios-setup.xml b/it/preparing/pre-install-bios-setup.xml
index d3f6be761..aee04b166 100644
--- a/it/preparing/pre-install-bios-setup.xml
+++ b/it/preparing/pre-install-bios-setup.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 69170 -->
+<!-- original version: 69217 -->
 
  <sect1 id="pre-install-bios-setup">
  <!-- <title>Pre-Installation Hardware and Operating System Setup</title> -->
@@ -198,19 +198,19 @@ ricerca dell'opzione.
 <para>
 
 <!--
-Windows 8 offers a feature called "fast boot" to cut down the time
+Windows 8 offers a feature called <quote>fast boot</quote> to cut down the time
 needed to boot itself.  Technically, when this feature is enabled,
 Windows 8 does not do a real shutdown and a real cold boot afterwards
 when ordered to shut down, but instead does something resembling a
-partial suspend to disk to reduce the "boot" time.  As long as Windows
+partial suspend to disk to reduce the <quote>boot</quote> time.  As long as Windows
 8 is the only operating system on the machine, this is unproblematic,
 but it can result in problems and data loss when you have a dual boot
 setup in which another operating system accesses the same filesystems
 as Windows 8 does.  In that case the real state of the filesystem can
-be different from what Windows 8 believes it to be after the "boot"
+be different from what Windows 8 believes it to be after the <quote>boot</quote>
 and this could cause filesystem corruption upon further write accesses
 to the filesystem.  Therefore in a dual boot setup, to avoid
-filesystem corruption the "fast boot" feature has to be disabled
+filesystem corruption the <quote>fast boot</quote> feature has to be disabled
 within Windows.
 -->