summaryrefslogtreecommitdiff
path: root/en
diff options
context:
space:
mode:
Diffstat (limited to 'en')
-rw-r--r--en/hardware/buying-hardware.xml2
-rw-r--r--en/hardware/hardware-supported.xml14
-rw-r--r--en/preparing/bios-setup/i386.xml10
3 files changed, 14 insertions, 12 deletions
diff --git a/en/hardware/buying-hardware.xml b/en/hardware/buying-hardware.xml
index a6dd3b144..525dc79ea 100644
--- a/en/hardware/buying-hardware.xml
+++ b/en/hardware/buying-hardware.xml
@@ -48,7 +48,7 @@ describing how an operating system and its device drivers communicate with a
certain class of devices. All devices which comply to such a
(de-facto-)standard can be used with a single generic device driver and no
device-specific drivers are required. With some kinds of hardware (e.g.
-USB "Human Interface Devices", i.e. keyboards, mice, etc., and USB mass
+USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass
storage devices like USB flash disks and memory card readers) this works
very well and practically every device sold in the market is
standards-compliant.
diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml
index a4e7c09d0..b4f11924a 100644
--- a/en/hardware/hardware-supported.xml
+++ b/en/hardware/hardware-supported.xml
@@ -241,8 +241,8 @@ From a technical point of view, laptops are normal PCs, so all information
regarding PC systems applies to laptops as well. Installations
on laptops nowadays usually work out of the box, including things like
automatically suspending the system on closing the lid and laptop specfic
-hardware buttons like those for disabling the wifi interfaces ("airplane
-mode"). Nonetheless sometimes the hardware vendors use specialized or
+hardware buttons like those for disabling the wifi interfaces (<quote>airplane
+mode</quote>). Nonetheless sometimes the hardware vendors use specialized or
proprietary hardware for some laptop-specific functions which
might not be supported. To see if your particular laptop works well
with GNU/Linux, see for example the
@@ -260,8 +260,8 @@ multiprocessing</quote> or SMP &mdash; is available for this
architecture. Having multiple processors in a computer was originally
only an issue for high-end server systems but has become quite common in
recent years even for rather low-end desktop computers and laptops with
-the introduction of so called "multi-core" processors. These contain
-two or more processor units, called "cores", in one physical chip.
+the introduction of so called <quote>multi-core</quote> processors. These contain
+two or more processor units, called <quote>cores</quote>, in one physical chip.
The standard &debian; &release; kernel image has been compiled with SMP support.
It is also usable on non-SMP systems without problems.
@@ -284,8 +284,8 @@ automatically deactivate SMP on uniprocessor systems.
Having multiple processors in a computer was originally
only an issue for high-end server systems but has become quite common in
recent years even for rather low-end desktop computers and laptops with
-the introduction of so called "multi-core" processors. These contain
-two or more processor units, called "cores", in one physical chip.
+the introduction of so called <quote>multi-core</quote> processors. These contain
+two or more processor units, called <quote>cores</quote>, in one physical chip.
</para><para arch="i386">
@@ -356,7 +356,7 @@ having a graphical display usually works out of the box. Whether
advanced graphics card features such as 3D-hardware acceleration
or hardware-accelerated video are available, depends on the
actual graphics hardware used in the system and in some cases
-on the installation of additional "firmware" images (see <xref
+on the installation of additional <quote>firmware</quote> images (see <xref
linkend="hardware-firmware"/>). In very few cases there have
been reports about hardware on which installation of additional graphics
card firmware was required even for basic graphics support, but
diff --git a/en/preparing/bios-setup/i386.xml b/en/preparing/bios-setup/i386.xml
index fddc947ae..c9c6d6324 100644
--- a/en/preparing/bios-setup/i386.xml
+++ b/en/preparing/bios-setup/i386.xml
@@ -38,7 +38,8 @@ are not already enabled.
Most BIOS versions allow to call up a boot menu on system startup in
which you select from which device the computer should start for the
current session. If this option is available, the BIOS usually displays
-a short message like "press <keycap>F12</keycap> for boot menu" on system startup.
+a short message like <quote>press <keycap>F12</keycap> for boot
+menu</quote> on system startup.
The actual key used to select this menu varies from system to system;
commonly used keys are <keycap>F12</keycap>, <keycap>F11</keycap> and
<keycap>F8</keycap>. Choosing a device from this menu does not change
@@ -59,10 +60,11 @@ a USB stick might not work even if there is an appropriate option in the
BIOS setup menu and the stick is selected as the primary boot device. On
some of these systems using a USB stick as boot medium is impossible; others
can be tricked into booting from the stick by changing the device type in
-the BIOS setup from the default "USB harddisk" or "USB stick" to "USB ZIP"
-or "USB CDROM". In particular if you use an isohybrid CD/DVD image on a USB stick
+the BIOS setup from the default <quote>USB harddisk</quote> or <quote>USB
+stick</quote> to <quote>USB ZIP</quote> or <quote>USB CDROM</quote>.
+In particular if you use an isohybrid CD/DVD image on a USB stick
(see <xref linkend="usb-copy-isohybrid"/>), changing the device type to
-"USB CDROM" helps on some BIOSes which will not boot from a USB stick in
+<quote>USB CDROM</quote> helps on some BIOSes which will not boot from a USB stick in
USB harddisk mode.
</para>