manual/en/preparing/needed-info.xml: replaced literal quotes ("")

by <quote></quote> tags to ensure proper typesetting.

Thanks to Holger Wansing for pointing this out.

1 files changed, 18 insertions, 18 deletions

diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml
index f48b6f107..c5ef84da7 100644
--- a/en/preparing/needed-info.xml
+++ b/en/preparing/needed-info.xml
@@ -282,10 +282,10 @@ not run as many different types of hardware as some operating systems.
 </para><para>
 
 Drivers in &arch-kernel; in most cases are not written for a certain
-"product" or "brand" from a specific manufacturer, but for a certain
+<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain
 hardware/chipset. Many seemingly
 different products/brands are based on the same hardware design; it is not
-uncommon that chip manufacturers provide so-called "reference designs" for
+uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for
 products based on their chips which are then used by several different
 device manufacturers and sold under lots of different product or brand
 names.
@@ -307,8 +307,8 @@ might be no driver at all for one of them.
 
 For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on
 which chipset they are based is to look at their device IDs.  All
-USB/PCI/PCI-Express/ExpressCard devices have so called "vendor" and
-"product" IDs, and the combination of these two is usually the same for any
+USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and
+<quote>product</quote> IDs, and the combination of these two is usually the same for any
 product based on the same chipset.
 
 </para><para>
@@ -317,46 +317,46 @@ On Linux systems, these IDs can be read with the <command>lsusb</command>
 command for USB devices and with the <command>lspci -nn</command> command for
 PCI/PCI-Express/ExpressCard devices.  The vendor and product IDs are usually
 given in the form of two hexadecimal numbers, seperated by a colon, such as
-"1d6b:0001".
+<quote>1d6b:0001</quote>.
 
 </para><para>
 
-An example for the output of <command>lsusb</command>: "Bus 001
-Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub", whereby 1d6b is
+An example for the output of <command>lsusb</command>: <quote>Bus 001
+Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is
 the vendor ID and 0002 is the product ID.
 
 </para><para>
 
 An example for the output of <command>lspci -nn</command> for an Ethernet
-card: "03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
-RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)". 
+card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
+RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. 
 The IDs are given inside the rightmost square brackets, i.e. here
 10ec is the vendor- and 8168 is the product ID.
 
 </para><para>
 
 As another example, a graphics card could give the following output:
-"04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee
-ATI RV710 [Radeon HD 4350] [1002:954f]".
+<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee
+ATI RV710 [Radeon HD 4350] [1002:954f]</quote>.
 
 </para><para>
 
 On Windows systems, the IDs for a device can be found in the Windows device
-manager on the tab "details", where the vendor ID is prefixed with VEN_
+manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_
 and the product ID is prefixed with DEV_.
 
-On Windows 7 systems, you have to select the property "Hardware IDs" in the
+On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the
 device manager's details tab to actually see the IDs, as they are not
 displayed by default.
 
 </para><para>
 
-Searching on the internet with the vendor/product ID, "&arch-kernel;" and
-"driver" as the search terms often results in information regarding
+Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and
+<quote>driver</quote> as the search terms often results in information regarding
 the driver support status for a certain chipset. If a search for the
 vendor/product ID does not yield usable results, a search for the chip
 code names, which are also often provided by lsusb and lspci
-("RTL8111"/"RTL8168B" in the network card example and "RV710" in the
+(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the
 graphics card example), can help.
 
 </para>
@@ -366,7 +366,7 @@ graphics card example), can help.
 
 <para>
 
-&debian-gnu; is also available as a so-called "live system" for certain
+&debian-gnu; is also available as a so-called <quote>live system</quote> for certain
 architectures.  A live system is a preconfigured ready-to-use system
 in a compressed format that can be booted and used from a read-only medium
 like a CD or DVD.  Using it by default does not create any permanent changes
@@ -477,7 +477,7 @@ If you use a WLAN/WiFi network, you should find out:
 <itemizedlist>
 <listitem><para>
 
-The ESSID ("network name") of your wireless network.
+The ESSID (<quote>network name</quote>) of your wireless network.
 
 </para></listitem>
 <listitem><para>