Capitalise titles as per the Chicago Manual of Style.

This commit is contained in:
Ceri Davies 2003-07-13 20:36:54 +00:00
parent 142824467d
commit 583831606d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17547
10 changed files with 60 additions and 60 deletions
en_US.ISO8859-1/books/handbook

View file

@ -501,7 +501,7 @@ postmaster@example.com postmaster@noc.example.net
</author> </author>
</authorgroup> </authorgroup>
</sect1info> </sect1info>
<title>Changing your Mail Transfer Agent</title> <title>Changing Your Mail Transfer Agent</title>
<indexterm> <indexterm>
<primary>email</primary> <primary>email</primary>
<secondary>change mta</secondary> <secondary>change mta</secondary>
@ -520,7 +520,7 @@ postmaster@example.com postmaster@noc.example.net
easy to make the change.</para> easy to make the change.</para>
<sect2> <sect2>
<title>Install a new MTA</title> <title>Install a New MTA</title>
<para>You have a wide choice of MTAs available. A good <para>You have a wide choice of MTAs available. A good
starting point is the starting point is the
@ -554,8 +554,8 @@ postmaster@example.com postmaster@noc.example.net
used to disable it is subtly different.</para> used to disable it is subtly different.</para>
<sect3> <sect3>
<title>FreeBSD 4.5-STABLE before 2002/4/4 and earlier <title>FreeBSD 4.5-STABLE before 2002/4/4 and Earlier
(including 4.5-RELEASE and earlier)</title> (Including 4.5-RELEASE and Earlier)</title>
<para>Enter:</para> <para>Enter:</para>
@ -570,7 +570,7 @@ postmaster@example.com postmaster@noc.example.net
<sect3> <sect3>
<title>FreeBSD 4.5-STABLE after 2002/4/4 <title>FreeBSD 4.5-STABLE after 2002/4/4
(including 4.6-RELEASE and later)</title> (Including 4.6-RELEASE and Later)</title>
<para>In order to completely disable <para>In order to completely disable
<application>sendmail</application> you must use</para> <application>sendmail</application> you must use</para>
@ -606,7 +606,7 @@ postmaster@example.com postmaster@noc.example.net
</sect3> </sect3>
<sect2> <sect2>
<title>Running your new MTA on boot</title> <title>Running Your New MTA on Boot</title>
<para>You may have a choice of two methods for running your <para>You may have a choice of two methods for running your
new MTA on boot, again depending on what version of FreeBSD new MTA on boot, again depending on what version of FreeBSD
@ -614,7 +614,7 @@ postmaster@example.com postmaster@noc.example.net
<sect3> <sect3>
<title>FreeBSD 4.5-STABLE before 2002/4/11 <title>FreeBSD 4.5-STABLE before 2002/4/11
(including 4.5-RELEASE and earlier)</title> (Including 4.5-RELEASE and Earlier)</title>
<para>Add a script to <para>Add a script to
<filename>/usr/local/etc/rc.d/</filename> that <filename>/usr/local/etc/rc.d/</filename> that
@ -638,7 +638,7 @@ postmaster@example.com postmaster@noc.example.net
<sect3> <sect3>
<title>FreeBSD 4.5-STABLE after 2002/4/11 <title>FreeBSD 4.5-STABLE after 2002/4/11
(including 4.6-RELEASE and later)</title> (Including 4.6-RELEASE and Later)</title>
<para>With later versions of FreeBSD, you can use the <para>With later versions of FreeBSD, you can use the
above method or you can set</para> above method or you can set</para>
@ -655,7 +655,7 @@ postmaster@example.com postmaster@noc.example.net
<sect2> <sect2>
<title>Replacing <application>sendmail</application> as <title>Replacing <application>sendmail</application> as
the system's default mailer</title> the System's Default Mailer</title>
<para>The program <application>sendmail</application> is so ubiquitous <para>The program <application>sendmail</application> is so ubiquitous
as standard software on Unix systems that some software as standard software on Unix systems that some software

View file

@ -1440,7 +1440,7 @@
</example> </example>
<example> <example>
<title>Creating a List of Changes (as unified diffs) to &man.ls.1;</title> <title>Creating a List of Changes (as Unified Diffs) to &man.ls.1;</title>
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput> <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
&prompt.user; <userinput>cvs login</userinput> &prompt.user; <userinput>cvs login</userinput>
@ -4213,7 +4213,7 @@ doc/zh_*</screen>
tags</quote>.</para> tags</quote>.</para>
<sect2> <sect2>
<title>Branch tags</title> <title>Branch Tags</title>
<para>All of these, with the exception of <literal>HEAD</literal> (which <para>All of these, with the exception of <literal>HEAD</literal> (which
is always a valid tag), only apply to the <filename>src/</filename> is always a valid tag), only apply to the <filename>src/</filename>
@ -4221,7 +4221,7 @@ doc/zh_*</screen>
<filename>www/</filename> trees are not branched.</para> <filename>www/</filename> trees are not branched.</para>
<variablelist> <variablelist>
<title>Branch tags</title> <title>Branch Tags</title>
<varlistentry> <varlistentry>
<term>HEAD</term> <term>HEAD</term>
@ -4345,7 +4345,7 @@ doc/zh_*</screen>
</sect2> </sect2>
<sect2> <sect2>
<title>Release tags</title> <title>Release Tags</title>
<para>These tags correspond to the FreeBSD <filename>src/</filename> <para>These tags correspond to the FreeBSD <filename>src/</filename>
tree (and <filename>ports/</filename>, <filename>doc/</filename>, and tree (and <filename>ports/</filename>, <filename>doc/</filename>, and
@ -4597,7 +4597,7 @@ doc/zh_*</screen>
</sect1> </sect1>
<sect1 id="mirrors-rsync"> <sect1 id="mirrors-rsync">
<title>rsync sites</title> <title>rsync Sites</title>
<para>The following sites make FreeBSD available through the rsync <para>The following sites make FreeBSD available through the rsync
protocol. The <application>rsync</application> utility works in protocol. The <application>rsync</application> utility works in

View file

@ -117,7 +117,7 @@
</authorgroup> </authorgroup>
</sect1info> </sect1info>
<title>Setting Up The Sound Card</title> <title>Setting Up the Sound Card</title>
<sect2 id="sound-device"> <sect2 id="sound-device">
<title>Locating the Correct Device</title> <title>Locating the Correct Device</title>
@ -800,7 +800,7 @@ option USER_LDT</programlisting>
kern.ipc.shmall=32768</programlisting> kern.ipc.shmall=32768</programlisting>
<sect2 id="video-interface"> <sect2 id="video-interface">
<title>Determining Video capabilities</title> <title>Determining Video Capabilities</title>
<indexterm><primary>XVideo</primary></indexterm> <indexterm><primary>XVideo</primary></indexterm>
<indexterm><primary>SDL</primary></indexterm> <indexterm><primary>SDL</primary></indexterm>
@ -1307,7 +1307,7 @@ zoom=yes</programlisting>
</sect3> </sect3>
<sect3 id="video-ports-transcode"> <sect3 id="video-ports-transcode">
<title>The transcode utilities</title> <title>The transcode Utilities</title>
<para>The software <application>transcode</application> is not a player, but a suite of tools for <para>The software <application>transcode</application> is not a player, but a suite of tools for
re-encoding <filename>.avi</filename> and <filename>.mpg</filename> files. With <application>transcode</application>, one has the re-encoding <filename>.avi</filename> and <filename>.mpg</filename> files. With <application>transcode</application>, one has the

View file

@ -292,7 +292,7 @@
the network.</para> the network.</para>
<example> <example>
<title>Downloading a Package Manually and then Installing It Locally</title> <title>Downloading a Package Manually and Installing It Locally</title>
<screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.FreeBSD.org</replaceable></userinput> <screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.FreeBSD.org</replaceable></userinput>
Connected to ftp2.FreeBSD.org. Connected to ftp2.FreeBSD.org.
@ -1103,7 +1103,7 @@ Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
</sect1> </sect1>
<sect1 id="ports-nextsteps"> <sect1 id="ports-nextsteps">
<title>Post-installation activities</title> <title>Post-installation Activities</title>
<para>After installing a new application you will normally want to <para>After installing a new application you will normally want to
read any documentation it may have included, edit any read any documentation it may have included, edit any

View file

@ -807,7 +807,7 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
</sect4> </sect4>
<sect4> <sect4>
<title>Setting up <filename>ppp.conf</filename> for Dynamic-IP Users</title> <title>Setting Up <filename>ppp.conf</filename> for Dynamic-IP Users</title>
<para>The <filename>/etc/ppp/ppp.conf</filename> file should <para>The <filename>/etc/ppp/ppp.conf</filename> file should
contain something along the lines of:</para> contain something along the lines of:</para>
@ -837,7 +837,7 @@ ttyd1:
</sect4> </sect4>
<sect4> <sect4>
<title>Setting up <filename>ppp.conf</filename> for Static-IP <title>Setting Up <filename>ppp.conf</filename> for Static-IP
Users</title> Users</title>
<para>Along with the contents of the sample <para>Along with the contents of the sample
@ -1299,7 +1299,7 @@ ifconfig_tun0=</programlisting>
<title>Using Kernel PPP</title> <title>Using Kernel PPP</title>
<sect2> <sect2>
<title>Setting up Kernel PPP</title> <title>Setting Up Kernel PPP</title>
<indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm> <indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm>
<para>Before you start setting up PPP on your machine, make sure <para>Before you start setting up PPP on your machine, make sure
@ -2040,7 +2040,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
(<acronym>PPPoE</acronym>).</para> (<acronym>PPPoE</acronym>).</para>
<sect2> <sect2>
<title>Configuring the kernel</title> <title>Configuring the Kernel</title>
<para>No kernel configuration is necessary for PPPoE any longer. If <para>No kernel configuration is necessary for PPPoE any longer. If
the necessary netgraph support is not built into the kernel, it will the necessary netgraph support is not built into the kernel, it will
@ -2048,7 +2048,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
</sect2> </sect2>
<sect2> <sect2>
<title>Setting up <filename>ppp.conf</filename></title> <title>Setting Up <filename>ppp.conf</filename></title>
<para>Here is an example of a working <para>Here is an example of a working
<filename>ppp.conf</filename>:</para> <filename>ppp.conf</filename>:</para>
@ -2089,7 +2089,7 @@ ppp_profile="name_of_service_provider"</programlisting>
</sect2> </sect2>
<sect2> <sect2>
<title>Using a PPPoE Service tag</title> <title>Using a PPPoE Service Tag</title>
<para>Sometimes it will be necessary to use a service tag to establish <para>Sometimes it will be necessary to use a service tag to establish
your connection. Service tags are used to distinguish between your connection. Service tags are used to distinguish between
@ -2448,7 +2448,7 @@ tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
<indexterm><primary>SLIP</primary></indexterm> <indexterm><primary>SLIP</primary></indexterm>
<sect2 id="slipc"> <sect2 id="slipc">
<title>Setting up a SLIP Client</title> <title>Setting Up a SLIP Client</title>
<indexterm><primary>SLIP</primary><secondary>client</secondary></indexterm> <indexterm><primary>SLIP</primary><secondary>client</secondary></indexterm>
<para>The following is one way to set up a FreeBSD machine for SLIP <para>The following is one way to set up a FreeBSD machine for SLIP
on a static host network. For dynamic hostname assignments (your on a static host network. For dynamic hostname assignments (your
@ -2719,7 +2719,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
</sect2> </sect2>
<sect2 id="slips"> <sect2 id="slips">
<title>Setting up a SLIP Server</title> <title>Setting Up a SLIP Server</title>
<indexterm><primary>SLIP</primary><secondary>server</secondary></indexterm> <indexterm><primary>SLIP</primary><secondary>server</secondary></indexterm>
<para>This document provides suggestions for setting up SLIP Server <para>This document provides suggestions for setting up SLIP Server

View file

@ -901,7 +901,7 @@ showpage</programlisting>
</sect3> </sect3>
<sect3 id="printing-printcap"> <sect3 id="printing-printcap">
<title>Enabling the Spooler: The <filename>/etc/printcap</filename> <title>Enabling the Spooler: the <filename>/etc/printcap</filename>
File</title> File</title>
<para>At this point, your printer should be hooked up, your kernel <para>At this point, your printer should be hooked up, your kernel
@ -2354,7 +2354,7 @@ exit 0</programlisting>
</sect4> </sect4>
<sect4 id="printing-advanced-autoconv"> <sect4 id="printing-advanced-autoconv">
<title>Automated Conversion: An Alternative To Conversion <title>Automated Conversion: an Alternative to Conversion
Filters</title> Filters</title>
<para>All these conversion filters accomplish a lot for your <para>All these conversion filters accomplish a lot for your
@ -3295,7 +3295,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
</sect3> </sect3>
<sect3 id="printing-advanced-restricting-access"> <sect3 id="printing-advanced-restricting-access">
<title>Restricting Access To Printers</title> <title>Restricting Access to Printers</title>
<para>You can control who can print to what printers by using the Unix <para>You can control who can print to what printers by using the Unix
group mechanism and the <literal>rg</literal> capability in group mechanism and the <literal>rg</literal> capability in

View file

@ -1246,7 +1246,7 @@ GAME GAG WELT OUT DOWN CHAT
</sect2> </sect2>
<sect2> <sect2>
<title>Generating a Single one-time Password</title> <title>Generating a Single One-time Password</title>
<para>Once you have initialized S/Key or OPIE, when you login you will be <para>Once you have initialized S/Key or OPIE, when you login you will be
presented with a prompt like this:</para> presented with a prompt like this:</para>
@ -1323,7 +1323,7 @@ Last login: Tue Mar 21 11:56:41 from 10.0.0.2 ... </screen>
</sect2> </sect2>
<sect2> <sect2>
<title>Generating Multiple one-time Passwords</title> <title>Generating Multiple One-time Passwords</title>
<para>Sometimes you have to go places where you do not have <para>Sometimes you have to go places where you do not have
access to a trusted machine or secure connection. In this case, access to a trusted machine or secure connection. In this case,
@ -3505,7 +3505,7 @@ Your identification has been saved in /home/user/.ssh/identity.
such as SMTP, POP3, FTP, etc.</para> such as SMTP, POP3, FTP, etc.</para>
<example> <example>
<title>Using SSH to create a secure tunnel for SMTP</title> <title>Using SSH to Create a Secure Tunnel for SMTP</title>
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5025:localhost:25 user@mailserver.example.com</replaceable></userinput> <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5025:localhost:25 user@mailserver.example.com</replaceable></userinput>
user@mailserver.example.com's password: <userinput>*****</userinput> user@mailserver.example.com's password: <userinput>*****</userinput>
@ -3526,7 +3526,7 @@ Escape character is '^]'.
<title>Practical SSH Tunneling Examples</title> <title>Practical SSH Tunneling Examples</title>
<sect4> <sect4>
<title>Secure Access of a POP3 server</title> <title>Secure Access of a POP3 Server</title>
<para>At work, there is an SSH server that accepts <para>At work, there is an SSH server that accepts
connections from the outside. On the same office network connections from the outside. On the same office network

View file

@ -590,7 +590,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
</sect3> </sect3>
<sect3 id="term-pcs"> <sect3 id="term-pcs">
<title>PCs Acting As Terminals</title> <title>PCs Acting as Terminals</title>
<para>If a <link linkend="term-dumb">dumb terminal</link> has just <para>If a <link linkend="term-dumb">dumb terminal</link> has just
enough ability to display, send, and receive text, then certainly enough ability to display, send, and receive text, then certainly
@ -917,7 +917,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
</sect3> </sect3>
<sect3> <sect3>
<title>Characters Appear Doubled; the Password Appears when Typed</title> <title>Characters Appear Doubled; the Password Appears When Typed</title>
<para>Switch the terminal (or the terminal emulation software) <para>Switch the terminal (or the terminal emulation software)
from <quote>half duplex</quote> or <quote>local echo</quote> to from <quote>half duplex</quote> or <quote>local echo</quote> to
@ -1142,7 +1142,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
format of the file and the list of capabilities.</para> format of the file and the list of capabilities.</para>
<sect4> <sect4>
<title>Locked-Speed Config</title> <title>Locked-speed Config</title>
<para>If you are locking your modem's data communications rate at a <para>If you are locking your modem's data communications rate at a
particular speed, you probably will not need to make any changes particular speed, you probably will not need to make any changes
@ -1150,7 +1150,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
</sect4> </sect4>
<sect4> <sect4>
<title>Matching-Speed Config</title> <title>Matching-speed Config</title>
<para>You will need to setup an entry in <para>You will need to setup an entry in
<filename>/etc/gettytab</filename> to give <filename>/etc/gettytab</filename> to give
@ -1279,7 +1279,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
</para> </para>
<sect4> <sect4>
<title>Locked-Speed Config</title> <title>Locked-speed Config</title>
<para>For a locked-speed configuration, your <para>For a locked-speed configuration, your
<filename>ttys</filename> entry needs to have a fixed-speed entry <filename>ttys</filename> entry needs to have a fixed-speed entry
@ -1298,7 +1298,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
</sect4> </sect4>
<sect4> <sect4>
<title>Matching-Speed Config</title> <title>Matching-speed Config</title>
<para>In a matching-speed configuration, your <para>In a matching-speed configuration, your
<filename>ttys</filename> entry needs to reference the appropriate <filename>ttys</filename> entry needs to reference the appropriate
@ -1491,7 +1491,7 @@ AT&amp;B2&amp;W</programlisting>
on your system.</para> on your system.</para>
<sect3> <sect3>
<title>Checking out the FreeBSD System</title> <title>Checking Out the FreeBSD System</title>
<para>Hook up your modem to your FreeBSD system, boot the system, and, <para>Hook up your modem to your FreeBSD system, boot the system, and,
if your modem has status indication lights, watch to see whether the if your modem has status indication lights, watch to see whether the
@ -1723,7 +1723,7 @@ tip57600|Dial any phone number at 57600 bps:\
</sect2> </sect2>
<sect2> <sect2>
<title>I Access a Number of Hosts through a Terminal Server</title> <title>I Access a Number of Hosts Through a Terminal Server</title>
<para>Rather than waiting until you are connected and typing <para>Rather than waiting until you are connected and typing
<command>CONNECT &lt;host&gt;</command> each time, use tip's <command>CONNECT &lt;host&gt;</command> each time, use tip's
@ -1743,7 +1743,7 @@ deep13:Gizmonics Institute terminal server:\
</sect2> </sect2>
<sect2> <sect2>
<title>Can Tip Try More Than one Line for each Site?</title> <title>Can Tip Try More Than One Line for Each Site?</title>
<para>This is often a problem where a university has several modem lines <para>This is often a problem where a university has several modem lines
and several thousand students trying to use them.</para> and several thousand students trying to use them.</para>
@ -1818,7 +1818,7 @@ big-university 5551114</programlisting>
</sect2> </sect2>
<sect2> <sect2>
<title>Suddenly Everything I Type Is in UPPER CASE??</title> <title>Suddenly Everything I Type Is in Upper Case??</title>
<para>You must have pressed <para>You must have pressed
<keycombo action="simul"> <keycombo action="simul">
@ -2263,7 +2263,7 @@ boot:</screen>
and the console eventually selected.</para> and the console eventually selected.</para>
<sect3> <sect3>
<title>Case 1: You Set the flags to 0x10 for <title>Case 1: You Set the Flags to 0x10 for
<devicename>sio0</devicename></title> <devicename>sio0</devicename></title>
<programlisting>device sio0 at isa? port IO_COM1 flags 0x10 irq 4</programlisting> <programlisting>device sio0 at isa? port IO_COM1 flags 0x10 irq 4</programlisting>
@ -2327,7 +2327,7 @@ boot:</screen>
</sect3> </sect3>
<sect3> <sect3>
<title>Case 2: You Set the flags to 0x30 for sio0</title> <title>Case 2: You Set the Flags to 0x30 for sio0</title>
<programlisting>device sio0 at isa? port IO_COM1 flags 0x30 irq 4</programlisting> <programlisting>device sio0 at isa? port IO_COM1 flags 0x30 irq 4</programlisting>
@ -2529,7 +2529,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
will override the settings in the boot block.</para> will override the settings in the boot block.</para>
<sect3> <sect3>
<title>Setting up the Serial Console</title> <title>Setting Up the Serial Console</title>
<para>You can easily specify the boot loader and the kernel to use the <para>You can easily specify the boot loader and the kernel to use the
serial console by writing just one line in serial console by writing just one line in
@ -2582,7 +2582,7 @@ start</programlisting>
</sect3> </sect3>
<sect3> <sect3>
<title>Using Serial Port Other than <devicename>sio0</devicename> for <title>Using a Serial Port Other Than <devicename>sio0</devicename> for
the Console</title> the Console</title>
<para>You need to recompile the boot loader to use a serial port other <para>You need to recompile the boot loader to use a serial port other

View file

@ -993,7 +993,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
</sect1> </sect1>
<sect1 id="vinum-root"> <sect1 id="vinum-root">
<title>Using Vinum for the root filesystem</title> <title>Using Vinum for the Root Filesystem</title>
<para>For a machine that has fully-mirrored filesystems using <para>For a machine that has fully-mirrored filesystems using
Vinum, it is desirable to also mirror the root filesystem. Vinum, it is desirable to also mirror the root filesystem.
@ -1023,8 +1023,8 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
examples in the following sections assume this name though.</para> examples in the following sections assume this name though.</para>
<sect2> <sect2>
<title>Starting up Vinum early enough for the root <title>Starting up Vinum Early Enough for the Root
filesystem</title> Filesystem</title>
<para>There are several measures to take for this to <para>There are several measures to take for this to
happen:</para> happen:</para>
@ -1086,8 +1086,8 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
</sect2> </sect2>
<sect2> <sect2>
<title>Making a Vinum-based root volume accessible to the <title>Making a Vinum-based Root Volume Accessible to the
bootstrap</title> Bootstrap</title>
<para>Since the current FreeBSD bootstrap is only 7.5 KB of <para>Since the current FreeBSD bootstrap is only 7.5 KB of
code, and already has the burden of reading files (like code, and already has the burden of reading files (like
@ -1222,7 +1222,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
</sect2> </sect2>
<sect2> <sect2>
<title>Example of a Vinum-based root setup</title> <title>Example of a Vinum-based Root Setup</title>
<para>After the Vinum root volume has been set up, the output of <para>After the Vinum root volume has been set up, the output of
<command>vinum l -rv root</command> could look like:</para> <command>vinum l -rv root</command> could look like:</para>
@ -1292,7 +1292,7 @@ Subdisk root.p1.s0:
and solutions.</para> and solutions.</para>
<sect3> <sect3>
<title>System bootstrap loads, but system does not boot</title> <title>System Bootstrap Loads, but System Does Not Boot</title>
<para>If for any reason the system does not continue to boot, <para>If for any reason the system does not continue to boot,
the bootstrap can be interrupted with by pressing the the bootstrap can be interrupted with by pressing the
@ -1335,7 +1335,7 @@ Subdisk root.p1.s0:
</sect3> </sect3>
<sect3> <sect3>
<title>Only primary bootstrap loads</title> <title>Only Primary Bootstrap Loads</title>
<para>If <filename>/boot/loader</filename> fails to load, but <para>If <filename>/boot/loader</filename> fails to load, but
the primary bootstrap still loads (visible by a single dash the primary bootstrap still loads (visible by a single dash
@ -1351,8 +1351,8 @@ Subdisk root.p1.s0:
</sect3> </sect3>
<sect3 id="vinum-root-panic"> <sect3 id="vinum-root-panic">
<title>Nothing boots, the bootstrap <title>Nothing Boots, the Bootstrap
panics</title> Panics</title>
<para>This situation will happen if the bootstrap had been <para>This situation will happen if the bootstrap had been
destroyed by the Vinum installation. Unfortunately, Vinum destroyed by the Vinum installation. Unfortunately, Vinum

View file

@ -1258,7 +1258,7 @@ DisplayManager.requestPort: 0</screen>
</sect3> </sect3>
<sect3 id="x11-wm-gnome-antialias"> <sect3 id="x11-wm-gnome-antialias">
<title>Anti-aliased fonts with GNOME</title> <title>Anti-aliased Fonts with GNOME</title>
<indexterm><primary>GNOME</primary> <indexterm><primary>GNOME</primary>
<secondary>anti-aliased fonts</secondary></indexterm> <secondary>anti-aliased fonts</secondary></indexterm>
@ -1414,7 +1414,7 @@ DisplayManager.requestPort: 0</screen>
difficult to learn by random exploration.</para> difficult to learn by random exploration.</para>
<sect3 id="x11-wm-kde-kdm"> <sect3 id="x11-wm-kde-kdm">
<title>The KDE display manager</title> <title>The KDE Display Manager</title>
<indexterm><primary>KDE</primary> <indexterm><primary>KDE</primary>
<secondary>display manager</secondary></indexterm> <secondary>display manager</secondary></indexterm>