diff --git a/en_US.ISO8859-1/articles/diskless-x/article.sgml b/en_US.ISO8859-1/articles/diskless-x/article.sgml
index 235a346099..ec16577767 100644
--- a/en_US.ISO8859-1/articles/diskless-x/article.sgml
+++ b/en_US.ISO8859-1/articles/diskless-x/article.sgml
@@ -98,7 +98,7 @@ nb8390.com
<sect1>
<title>Getting the network boot programs (On the server)</title>
- <para>Compile the 'net-boot' programs that are located in
+ <para>Compile the <quote>net-boot</quote> programs that are located in
<filename>/usr/src/sys/i386/boot/netboot</filename>. You should read
the comments at the top of the <filename>Makefile</filename>. Adjust as
required. Make a backup of the original in case it gets foobar'd. When
@@ -202,7 +202,7 @@ bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab</progra
<row>
<entry><literal>ht=ether</literal></entry>
- <entry>the hardware type of 'ethernet'.</entry>
+ <entry>the hardware type of <quote>ethernet</quote>.</entry>
</row>
<row>
diff --git a/en_US.ISO8859-1/articles/filtering-bridges/article.sgml b/en_US.ISO8859-1/articles/filtering-bridges/article.sgml
index de0ffd3172..af4cf51e9a 100644
--- a/en_US.ISO8859-1/articles/filtering-bridges/article.sgml
+++ b/en_US.ISO8859-1/articles/filtering-bridges/article.sgml
@@ -22,7 +22,7 @@
<abstract>
<para>For those of you who do not know, DSL differs from more traditional
- connectivity methods in that the "connectivity spigot" that comes
+ connectivity methods in that the <quote>connectivity spigot</quote> that comes
out of the wall has no possibility for packet filtering. If you get
a T1 line or some such it will come with a router that can generally
include a packet filter. If you get ISDN or a dialup link, you also
@@ -52,7 +52,7 @@
half or defining a new space that is typically unroutable (see
<ulink url="ftp://nis.nsf.net/internet/documents/rfc/rfc1918.txt">RFC 1918</ulink>).
This wastes half of the useful addresses (or at least puts
- them on the "wrong" side of the router -- the thing that is
+ them on the <quote>wrong</quote> side of the router—the thing that is
doing the packet filtering that makes the inside network safe).
Using a bridge costs some CPU cycles, but makes all of the
problems of adding a 2nd router go away.</para>
@@ -74,7 +74,7 @@
RELENG_4 and -current have had bridging support for all Ethernet
interfaces. This does not mean that any Ethernet interface will work.
For them to work, they have to support a working promiscuous mode for
- both reception and transmission -- that is, they have to be able to
+ both reception and transmission—that is, they have to be able to
transmit Ethernet packets with any source address, not just their own.
In order to get good throughput, the cards should also be PCI bus
mastering cards. The best choices still are the Intel EtherExpress Pro
@@ -111,7 +111,7 @@ options IPFIREWALL_VERBOSE</programlisting>
<para>Before you boot the new kernel, you must make some preparations in
<filename>rc.boot</filename> and <filename>rc.firewall</filename>. The
default rule for the firewall is to drop all packets on the floor. You
- will want to override this by setting up the 'open' firewall in
+ will want to override this by setting up the <quote>open</quote> firewall in
<filename>/etc/rc.conf</filename>. Put these lines in
<filename>/etc/rc.conf</filename> to achieve this:</para>
@@ -183,10 +183,10 @@ firewall_type="open"</programlisting>
portions of the startup that require network access, say for DNS
resolution. Some care must be made in picking which interface is going
to be the configured one. In most cases, you are best to pick the
- "outside" one (that is, the interface connected to the Internet). Let's
+ <quote>outside</quote> one (that is, the interface connected to the Internet). Let's
presume for the sake of the examples to come, that
- <devicename>fxp0</devicename> is the "outside" interface, and
- <devicename>fxp1</devicename> is the "inside" one. That means that fxp0
+ <devicename>fxp0</devicename> is the <quote>outside</quote> interface, and
+ <devicename>fxp1</devicename> is the <quote>inside</quote> one. That means that fxp0
should be mentioned in <filename>/etc/rc.conf</filename>'s ifconfig
sections, but <devicename>fxp1</devicename> should not be. The sysctl
that turns the bridge on will make <devicename>fxp1</devicename> start
@@ -203,11 +203,11 @@ firewall_type="open"</programlisting>
bridged and packets that are being received by the local machine. In
general, packets being bridged are only run through ipfirewall once, not
twice as is usually the case. Bridged packets are filtered while they
- are being received, so rules that use 'out' or 'xmit' will never match.
- I usually use 'in via' which is an older syntax, but one that makes
+ are being received, so rules that use <literal>out</literal> or <literal>xmit</literal> will never match.
+ I usually use <literal>in via</literal> which is an older syntax, but one that makes
sense as you read it. Another limitation is that you are restricted
- only to 'pass' or 'drop' for filtering bridged packets. Sophisticated
- things like 'divert' or 'forward' or 'reject' are not available. Such
+ only to <literal>pass</literal> or <literal>drop</literal> for filtering bridged packets. Sophisticated
+ things like <literal>divert</literal> or <literal>forward</literal> or <literal>reject</literal> are not available. Such
options can still be used, but only on traffic to or from the bridge
machine itself.</para>
@@ -217,7 +217,7 @@ firewall_type="open"</programlisting>
addresses and port numbers (but with source and dest reversed, of
course). For firewalls that have no statekeeping, there is almost no
way to deal with this sort of traffic short of setting up proxies. But
- a firewall that can "remember" an outgoing UDP packet and for the next
+ a firewall that can <quote>remember</quote> an outgoing UDP packet and for the next
few minutes allow a response, handling UDP services is trivial. The
example to follow shows how to do this. The truly paranoid can also set
up rules like this to handle TCP. This allows you to avoid some sorts
@@ -286,7 +286,7 @@ ${ipfw} add deny log ip from any to any</programlisting>
do to make sure that someone does not try and evade the packet filter by
generating nefarious packets that look like they are from the inside.
The problem with that is that there is at least one host on the outside
- interface that you do not want to ignore -- your router. In my
+ interface that you do not want to ignore—your router. In my
particular case, I have some machines on the outside and some on the
inside, but I do not necessarily want the outside machines to have
routine access to the inside. At the same time, I do not want to throw
@@ -311,7 +311,7 @@ ${ipfw} add deny log ip from any to any</programlisting>
<para>There is a rule for passing SMTP to a mailhost if you have one.
Obviously the whole ruleset above should be flavored to taste, and
that is an example of a specific service exemption. Note that
- in order for 'mailhost' to work, name service lookups must work
+ in order for <quote>mailhost</quote> to work, name service lookups must work
BEFORE the bridge is enabled. This is an example of making sure
that you enable the correct interface.</para>
@@ -320,7 +320,7 @@ ${ipfw} add deny log ip from any to any</programlisting>
DNS server, you do not need them.</para>
<para>Folks used to setting up IP firewalls also probably are used to
- either having a 'reset' or a 'forward' rule for ident packets
+ either having a <literal>reset</literal> or a <literal>forward</literal> rule for ident packets
(TCP port 113). Unfortunately, this is not an option with the
bridging code, so the path of least resistance is to simply pass
them to their destination. As long as that destination machine
@@ -330,7 +330,7 @@ ${ipfw} add deny log ip from any to any</programlisting>
timeout).</para>
<para>The only other thing that is a little weird that you may have noticed
- is that there is a rule to let ${us_ip} speak and a separate rule to
+ is that there is a rule to let <literal>${us_ip}</literal> speak and a separate rule to
allow the inside network to speak. Remember that this is because the
two sets of traffic will be taking different paths through the kernel
and into the packet filter. The inside net will be going through the
@@ -338,7 +338,7 @@ ${ipfw} add deny log ip from any to any</programlisting>
stack to speak. Thus the two rules to handle the different cases. The
in via ${oif} rules work for both paths. In general if you use in via
rules throughout the filter, you will need to make an exception for
- locally generated packets, because they did not "come in" via
+ locally generated packets, because they did not <quote>come in</quote> via
anything.</para>
</sect1>
diff --git a/en_US.ISO8859-1/articles/freebsd-questions/article.sgml b/en_US.ISO8859-1/articles/freebsd-questions/article.sgml
index a6eb23c0c0..f36c3c3fe6 100644
--- a/en_US.ISO8859-1/articles/freebsd-questions/article.sgml
+++ b/en_US.ISO8859-1/articles/freebsd-questions/article.sgml
@@ -217,8 +217,8 @@ you consider the question to be pretty technical.</literallayout>
<listitem>
<para>Not everybody who answers FreeBSD questions reads every message:
they look at the subject line and decide whether it interests them.
- Clearly, it is in your interest to specify a subject. ``FreeBSD
- problem'' or ``Help'' are not enough. If you provide no subject at
+ Clearly, it is in your interest to specify a subject. <quote>FreeBSD
+ problem</quote> or <quote>Help</quote> are not enough. If you provide no subject at
all, many people will not bother reading it. If your subject is not
specific enough, the people who can answer it may not read
it.</para>
@@ -406,7 +406,7 @@ of difficulty installing it. I have a 66 MHz 486 with 16 MB of
memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball
disk and a Toshiba 3501XA CDROM drive. The installation works just
fine, but when I try to reboot the system, I get the message
-``Missing Operating System''.</literallayout>
+<quote>Missing Operating System</quote>.</literallayout>
</example>
</sect1>
diff --git a/en_US.ISO8859-1/articles/laptop/article.sgml b/en_US.ISO8859-1/articles/laptop/article.sgml
index 87f4ebe6fb..bac561f779 100644
--- a/en_US.ISO8859-1/articles/laptop/article.sgml
+++ b/en_US.ISO8859-1/articles/laptop/article.sgml
@@ -73,16 +73,16 @@
<programlisting>
Option "Emulate3Buttons"
</programlisting>
- in the XF86Config file in the "InputDevice" section (for XFree86
- version 4; for version 3, put just the line "Emulate3Buttons",
- without the quotes, in the "Pointer" section.)
+ in the XF86Config file in the <literal>InputDevice</literal> section (for XFree86
+ version 4; for version 3, put just the line <literal>Emulate3Buttons</literal>,
+ without the quotes, in the <literal>Pointer</literal> section.)
</sect1>
<sect1>
<title>Modems</title>
<para>
Laptops usually come with internal (on-board) modems.
- Unfortunately, this almost always means they are "winmodems" whose
+ Unfortunately, this almost always means they are <quote>winmodems</quote> whose
functionality is implemented in software, for which only windows
drivers are normally available (though a few drivers are beginning
to show up for other operating systems). Otherwise, you
@@ -106,10 +106,10 @@ Option "Emulate3Buttons"
<devicename>pcic0</devicename>).</para>
<para>FreeBSD currently supports 16-bit PCMCIA cards, but not
- 32-bit ("CardBus") cards. A database of supported cards is in
+ 32-bit (<quote>CardBus</quote>) cards. A database of supported cards is in
the file <filename>/etc/defaults/pccard.conf</filename>. Look
through it, and preferably buy cards listed there. Cards not
- listed may also work as "generic" devices: in particular most
+ listed may also work as <quote>generic</quote> devices: in particular most
modems (16-bit) should work fine, provided they are not
winmodems (these do exist even as PC-cards, so watch out). If
your card is recognised as a generic modem, note that the
@@ -118,7 +118,7 @@ Option "Emulate3Buttons"
over-cautious for your modem, so you may want to play with it,
reducing it or removing it totally.</para>
- <para>Some parts of pccard.conf may need editing. Check the irq
+ <para>Some parts of <filename>pccard.conf</filename> may need editing. Check the irq
line, and be sure to remove any number already being used: in
particular, if you have an on board sound card, remove irq 5
(otherwise you may experience hangs when you insert a card).
@@ -159,7 +159,7 @@ Option "Emulate3Buttons"
<command>apm -b</command> gives you battery status (or 255 if
not supported), <command>apm -Z</command> puts the laptop on
standby, <command>apm -z</command> (or zzz) suspends it. To
- shutdown and power off the machine, use "shutdown -p".
+ shutdown and power off the machine, use <command>shutdown -p</command>.
Again, some or all of these functions may not work very well
or at all. You may find that laptop suspension/standby works
in console mode but not under X (that is, the screen does not
diff --git a/en_US.ISO8859-1/articles/multi-os/article.sgml b/en_US.ISO8859-1/articles/multi-os/article.sgml
index 8b28f5a6b2..a40b7c76b0 100644
--- a/en_US.ISO8859-1/articles/multi-os/article.sgml
+++ b/en_US.ISO8859-1/articles/multi-os/article.sgml
@@ -352,7 +352,7 @@ Press Esc to continue
multibooting Windows NT, '95, and DOS with other operating
systems.</para>
]]>
- <para>And Hale Landis's "How It Works" document pack contains some
+ <para>And Hale Landis's <quote>How It Works</quote> document pack contains some
good info on all sorts of disk geometry and booting related
topics. You can find it at
<ulink
@@ -389,7 +389,7 @@ Press Esc to continue
<para>Your disk has a particular number of cylinders, number of
heads, and number of sectors per cylinder-head (a
cylinder-head also known nown as a track). Collectively this
- information defines the "physical disk geometry" for your hard
+ information defines the <quote>physical disk geometry</quote> for your hard
disk. There are typically 512 bytes per sector, and 63
sectors per track, with the number of cylinders and heads
varying widely from disk to disk. Thus you can figure the
diff --git a/en_US.ISO8859-1/articles/pxe/article.sgml b/en_US.ISO8859-1/articles/pxe/article.sgml
index 3800349d55..cb769136b9 100644
--- a/en_US.ISO8859-1/articles/pxe/article.sgml
+++ b/en_US.ISO8859-1/articles/pxe/article.sgml
@@ -35,9 +35,9 @@
<title>Introduction</title>
<warning>
- <para>This procedure will make the 'Server' both insecure and dangerous,
- it is best to just keep the 'Server' on its own hub and not in any way
- accessible by any machines other than the 'Clients'.</para>
+ <para>This procedure will make the <quote>Server</quote> both insecure and dangerous,
+ it is best to just keep the <quote>Server</quote> on its own hub and not in any way
+ accessible by any machines other than the <quote>Clients</quote>.</para>
</warning>
<para>Terminology:</para>
@@ -268,8 +268,8 @@ RELNOTES.TXT compat1x doc packages</screen>
<filename>PLIST</filename> which contains all the files that you wish to
install and be incorporated into your package.</para>
- <para>You will also want files called '<filename>pre</filename>' and
- '<filename>post</filename>' in the directory, these are shell scripts
+ <para>You will also want files called <filename>pre</filename> and
+ <filename>post</filename> in the directory, these are shell scripts
that you want to execute before and after your package is
installed.</para>
@@ -277,4 +277,3 @@ RELNOTES.TXT compat1x doc packages</screen>
it should be run and do the final configuration for you.</para>
</sect1>
</article>
-
diff --git a/en_US.ISO8859-1/articles/storage-devices/article.sgml b/en_US.ISO8859-1/articles/storage-devices/article.sgml
index 218d4c0cfe..9179f68707 100644
--- a/en_US.ISO8859-1/articles/storage-devices/article.sgml
+++ b/en_US.ISO8859-1/articles/storage-devices/article.sgml
@@ -42,7 +42,7 @@
place the speed of the interface is higher, 10 or 15
Mbits/second instead of the 5 Mbits/second of ST412 interfaced
drives. Secondly some higher level commands are added, making
- the ESDI interface somewhat 'smarter' to the operating system
+ the ESDI interface somewhat <quote>smarter</quote> to the operating system
driver writers. It is by no means as smart as SCSI by the way.
ESDI is standardized by ANSI.</para>
@@ -272,7 +272,7 @@
each track for actual data storage, and sector N itself is the
spare sector. N is the total number of sectors physically
available on the track. The idea behind this is that the
- operating system sees a 'perfect' disk without bad sectors. In
+ operating system sees a <quote>perfect</quote> disk without bad sectors. In
the case of FreeBSD this concept is not usable.</para>
<para>The problem is that the translation from
@@ -304,7 +304,7 @@
requested that is in the <command>bad144</command> list, a
replacement block (also from the end of the FreeBSD slice) is
used. In this way, the <command>bad144</command> replacement
- scheme presents 'perfect' media to the FreeBSD filesystems.</para>
+ scheme presents <quote>perfect</quote> media to the FreeBSD filesystems.</para>
<para>There are a number of potential pitfalls associated with the
use of <command>bad144</command>. First of all, the slice cannot
@@ -515,7 +515,7 @@ disk wd3 at wdc1 drive 1</programlisting>
instance you do not specify a head/cylinder/sector to address a
particular block, but simply the number of the block you want.
Elaborate caching schemes, automatic bad block replacement etc are all
- made possible by this 'intelligent device' approach.</para>
+ made possible by this <quote>intelligent device</quote> approach.</para>
<para>On a SCSI bus, each possible pair of devices can communicate.
Whether their function allows this is another matter, but the standard
@@ -616,7 +616,7 @@ disk wd3 at wdc1 drive 1</programlisting>
<para>Fast means that the timing on the bus is somewhat different, so
that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead of 5
- Mbytes/sec for 'slow' SCSI. As discussed before, bus speeds of 20
+ Mbytes/sec for <quote>slow</quote> SCSI. As discussed before, bus speeds of 20
and 40 million transfers/second are also emerging (Fast-20 == Ultra
SCSI and Fast-40 == Ultra2 SCSI).</para>
@@ -635,7 +635,7 @@ disk wd3 at wdc1 drive 1</programlisting>
<para>A single-ended SCSI bus uses signals that are either 5 Volts
or 0 Volts (indeed, TTL levels) and are relative to a COMMON
ground reference. A singled ended 8 bit SCSI bus has
- approximately 25 ground lines, who are all tied to a single `rail'
+ approximately 25 ground lines, who are all tied to a single <quote>rail</quote>
on all devices. A standard single ended bus has a maximum length
of 6 meters. If the same bus is used with fast-SCSI devices, the
maximum length allowed drops to 3 meters. Fast-SCSI means that
@@ -650,7 +650,7 @@ disk wd3 at wdc1 drive 1</programlisting>
quickly find out if your SCSI bus is electrically sound.</para>
<note>
- <para>If some devices on your bus use 'fast' to communicate your
+ <para>If some devices on your bus use <quote>fast</quote> to communicate your
bus must adhere to the length restrictions for fast
buses!</para>
</note>
@@ -668,7 +668,7 @@ disk wd3 at wdc1 drive 1</programlisting>
Apple uses a 25pin D-type connecter (like the one on serial ports
and parallel printers). Considering that the official SCSI bus
needs 50 pins you can imagine the use of this connector needs some
- 'creative cabling'. The reduction of the number of ground wires
+ <quote>creative cabling</quote>. The reduction of the number of ground wires
they used is a bad idea, you better stick to 50 pins cabling in
accordance with the SCSI standard. For Fast-20 and 40 do not even
think about buses like this.</para>
@@ -812,7 +812,7 @@ disk wd3 at wdc1 drive 1</programlisting>
certainly will. Clever external terminators sometimes have a LED
indication that shows whether terminator power is present.</para>
- <para>In newer designs auto-restoring fuses that 'reset' themselves
+ <para>In newer designs auto-restoring fuses that <quote>reset</quote> themselves
after some time are sometimes used.</para>
</sect3>
@@ -1116,7 +1116,7 @@ device cd0 at scbus? [the first ever CDROM found, no wiring]<
<para>A kernel built to the config file below will attach the first
SCSI disk it finds to sd0, the second disk to sd1 etc. If you ever
removed or added a disk, all other devices of the same type (disk
- in this case) would 'move around'. This implies you have to
+ in this case) would <quote>move around</quote>. This implies you have to
change <filename>/etc/fstab</filename> each time.</para>
<para>Although the old style still works, you are
@@ -1166,7 +1166,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
specific target ID. This process is called device probing by the
way.</para>
- <para>To work around the 'slow response' problem, FreeBSD allows a
+ <para>To work around the <quote>slow response</quote> problem, FreeBSD allows a
tunable delay time before the SCSI devices are probed following a
SCSI bus reset. You can set this delay time in your kernel
configuration file using a line like:</para>
@@ -1594,7 +1594,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
<para>Make sure you have adequate air flow around the drive,
especially if you are going to use a fast-spinning drive. You
- generally need at least 1/2" (1.25cm) of spacing above and below a
+ generally need at least 1/2” (1.25cm) of spacing above and below a
drive. Understand how the air flows through your PC case. Most
cases have the power supply suck the air out of the back. See
where the air flows in, and put the drive where it will have the
@@ -1611,12 +1611,12 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
<sect3>
<title>Form factor</title>
- <para>Most SCSI drives sold today are of 3.5" form factor. They
- come in two different heights; 1.6" (<quote>half-height</quote>) or
- 1" (<quote>low-profile</quote>). The half-height drive is the same
+ <para>Most SCSI drives sold today are of 3.5” form factor. They
+ come in two different heights; 1.6” (<quote>half-height</quote>) or
+ 1” (<quote>low-profile</quote>). The half-height drive is the same
height as a CDROM drive. However, do not forget the spacing rule
mentioned in the previous section. If you have three standard
- 3.5" drive bays, you will not be able to put three half-height
+ 3.5” drive bays, you will not be able to put three half-height
drives in there (without frying them, that is).</para>
</sect3>
diff --git a/en_US.ISO8859-1/articles/vinum/article.sgml b/en_US.ISO8859-1/articles/vinum/article.sgml
index 32b3f435a7..9eed234383 100644
--- a/en_US.ISO8859-1/articles/vinum/article.sgml
+++ b/en_US.ISO8859-1/articles/vinum/article.sgml
@@ -20,8 +20,8 @@
<year>2001</year>
<holder>Robert A. Van Valzah</holder>
</copyright>
- <pubdate>$Date: 2001-10-31 23:12:55 $ GMT</pubdate>
- <releaseinfo>$Id: article.sgml,v 1.4 2001-10-31 23:12:55 chern Exp $</releaseinfo>
+ <pubdate>$Date: 2002-02-14 23:57:13 $ GMT</pubdate>
+ <releaseinfo>$Id: article.sgml,v 1.5 2002-02-14 23:57:13 keramida Exp $</releaseinfo>
</articleinfo>
<abstract>
@@ -290,14 +290,14 @@
<foreignphrase>In Vino Veritas</foreignphrase>
(<foreignphrase>Vino</foreignphrase> is the accusative form of
<foreignphrase>Vinum</foreignphrase>).
- Literally translated, that is "Truth lies in wine" hinting that
+ Literally translated, that is <quote>Truth lies in wine</quote> hinting that
drunkards have a hard time lying.
</para>
<para>I have been using it in production on six different servers for
over two years with no data loss.
Like the rest of FreeBSD, <application>Vinum</application>
- provides "rock-stable performance."
+ provides <quote>rock-stable performance.</quote>
(On a personal note, I have seen <application>Vinum</application>
panic when I misconfigured something, but I have
never had any trouble in normal operation.)
@@ -322,7 +322,7 @@
<para><application>Vinum</application>,
coupled with prudent partition management, lets you
- keep "warm-spare" spindles on-line so that failures
+ keep <quote>warm-spare</quote> spindles on-line so that failures
are transparent to users. Failed spindles can be replaced
during regular maintenance periods or whenever it is convenient.
When all spindles are working, the server benefits from increased
@@ -368,7 +368,7 @@
<application>Vinum</application>, installing FreeBSD
without it, and then beginning to use it.</para>
- <para>I have come to call this whole process "bootstrapping Vinum."
+ <para>I have come to call this whole process <quote>bootstrapping Vinum.</quote>
That is, the process of getting <application>Vinum</application>
initially installed
and operating to the point where you have met your resilience
@@ -415,8 +415,8 @@
<note>
<para>Breaking up your disk space into smaller and smaller partitions
- has the benefit of allowing you to "tune" for the most common
- type of access and tends to keep disk hogs "within their pens."
+ has the benefit of allowing you to <quote>tune</quote> for the most common
+ type of access and tends to keep disk hogs <quote>within their pens.</quote>
However it also causes some loss in total available disk space
due to fragmentation.</para></note>
</section>
@@ -505,7 +505,7 @@
<para>Keep your kernel fairly generic (or at least keep
<filename>/kernel.GENERIC</filename> around).
This will improve the chances that you can come back up on
- "foreign" hardware more quickly.</para>
+ <quote>foreign</quote> hardware more quickly.</para>
</tip>
<para>The pros and cons discussed above suggest
@@ -708,7 +708,7 @@
will still call
it by whatever name it had when it was attached to
<devicename>/dev/ad2</devicename>
- (i.e., when it was "created" or first made known to
+ (i.e., when it was <quote>created</quote> or first made known to
<application>Vinum</application>).</para>
<para>Since connections can change, it is best to give
@@ -2087,7 +2087,7 @@ ok <userinput>boot -s</userinput</screen>
use strict;
use FileHandle;
-my $config_tag1 = '$Id: article.sgml,v 1.4 2001-10-31 23:12:55 chern Exp $';
+my $config_tag1 = '$Id: article.sgml,v 1.5 2002-02-14 23:57:13 keramida Exp $';
# Copyright (C) 2001 Robert A. Van Valzah
#
# Bootstrap Vinum
diff --git a/en_US.ISO8859-1/articles/vm-design/article.sgml b/en_US.ISO8859-1/articles/vm-design/article.sgml
index 3f400b365b..9e992c6039 100644
--- a/en_US.ISO8859-1/articles/vm-design/article.sgml
+++ b/en_US.ISO8859-1/articles/vm-design/article.sgml
@@ -226,7 +226,7 @@
process will take a copy-on-write fault and duplicate the page in C2.
The original page in B is now completely hidden since both C1 and C2
have a copy and B could theoretically be destroyed if it does not
- represent a 'real' file). However, this sort of optimization is not
+ represent a <quote>real</quote> file). However, this sort of optimization is not
trivial to make because it is so fine-grained. FreeBSD does not make
this optimization. Now, suppose (as is often the case) that the child
process does an <function>exec()</function>. Its current address space
@@ -319,7 +319,7 @@
are mapped, or processes with large runsizes (RSS) fork. Also, in order
to keep track of swap space, a <quote>list of holes</quote> is kept in
kernel memory, and this tends to get severely fragmented as well. Since
- the 'list of holes' is a linear list, the swap allocation and freeing
+ the <quote>list of holes</quote> is a linear list, the swap allocation and freeing
performance is a non-optimal O(n)-per-page. It also requires kernel
memory allocations to take place during the swap freeing process, and
that creates low memory deadlock problems. The problem is further
@@ -343,7 +343,7 @@
times in order to avoid potential deadlocks. Finally, to reduce
fragmentation the radix tree is capable of allocating large contiguous
chunks at once, skipping over smaller fragmented chunks. I did not take
- the final step of having an 'allocating hint pointer' that would trundle
+ the final step of having an <quote>allocating hint pointer</quote> that would trundle
through a portion of swap as allocations were made in order to further
guarantee contiguous allocations or at least locality of reference, but
I ensured that such an addition could be made.</para>