Date: Sun, 2 Apr 2000 14:28:13 -0500 From: Chris Costello <chris@calldei.com> To: doc@FreeBSD.org Subject: Handcook Capitalization Patch Message-ID: <20000402142813.C27486@holly.calldei.com>
next in thread | raw e-mail | index | archive | help
The titles in the handbook are currently inconsistently
capitalized. Some capitalize only the first letter, some
capitalize it properly, and some capitalize every single word.
This patch will fix that. I'd like to know if this is OK with
you guys and I'd like to have it in by tonight (Sun, 2 Apr).
Index: backups/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v
retrieving revision 1.19
diff -u -r1.19 chapter.sgml
--- backups/chapter.sgml 2000/03/21 19:55:41 1.19
+++ backups/chapter.sgml 2000/04/02 19:24:11
@@ -175,7 +175,7 @@
</sect2>
<sect2>
- <title>Using a new tape for the first time</title>
+ <title>Using a New Tape for the First Time</title>
<para>The first time that you try to read or write a new, completely
blank tape, the operation will fail. The console messages should be
@@ -320,7 +320,7 @@
</sect2>
<sect2>
- <title>Do nothing</title>
+ <title>Do Nothing</title>
<para>“Do nothing” is not a computer program, but it is the
most widely used backup strategy. There are no initial costs. There
@@ -626,7 +626,7 @@
</sect1>
<sect1 id="backups-floppybackups">
- <title>What about backups to floppies?</title>
+ <title>What about Backups to Floppies?</title>
<sect2 id="floppies-using">
<title>Can I use floppies for backing up my data?</title>
Index: boot/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v
retrieving revision 1.5
diff -u -r1.5 chapter.sgml
--- boot/chapter.sgml 2000/03/25 14:18:24 1.5
+++ boot/chapter.sgml 2000/04/02 19:24:12
@@ -29,7 +29,7 @@
</sect1>
<sect1 id="boot-blocks">
- <title>The boot blocks: Bootstrap stages 1 and 2</title>
+ <title>The Boot Blocks: Bootstrap Stages 1 and 2</title>
<para><firstterm>Bootstrapping</firstterm> is the process
whereby a computer probes and initializes its devices, and
@@ -124,7 +124,7 @@
</sect1>
<sect1 id="boot-loader">
- <title>loader: Bootstrap stage three</title>
+ <title>Loader: Bootstrap Stage Three</title>
<para>The loader is the final stage of the three-stage
bootstrap, and is located on the filesystem, usually as
@@ -144,7 +144,7 @@
command set.</para>
<sect2 id="boot-loader-flow">
- <title>loader program flow</title>
+ <title>Loader Program Flow</title>
<para>During initialization, the loader will probe for a
console and for disks, and figure out what disk it is
@@ -173,7 +173,7 @@
</sect2>
<sect2 id="boot-loader-commands">
- <title>loader built-in commands</title>
+ <title>Loader Built-In Commands</title>
<para>The easy-to-use command set comprises of:</para>
@@ -314,7 +314,7 @@
</sect2>
<sect2 id="boot-loader-examples">
- <title>loader examples</title>
+ <title>Loader Examples</title>
<para>Here are some practical examples of loader usage.</para>
@@ -362,7 +362,7 @@
</sect1>
<sect1 id="boot-kernel">
- <title>Kernel interaction during boot</title>
+ <title>Kernel Interaction During Boot</title>
<para>Once the kernel is loaded by either <link
linkend="boot-loader">loader</link> (as usual) or <link
@@ -371,7 +371,7 @@
necessary.</para>
<sect2 id="boot-kernel-bootflags">
- <title>Kernel bootflags</title>
+ <title>Kernel Boot Flags</title>
<para>Here are the more common boot flags:</para>
@@ -433,7 +433,7 @@
</sect1>
<sect1 id="boot-init">
- <title>Init: Process control initialization</title>
+ <title>Init: Process Control Initialization</title>
<para>Once the kernel has finished booting, it passes control to
the user process <command>init</command>, which is located at
@@ -442,7 +442,7 @@
<command>loader</command>.</para>
<sect2 id="boot-autoreboot">
- <title>Automatic reboot sequence</title>
+ <title>Automatic Reboot Sequence</title>
<para>The automatic reboot sequence makes sure that the
filesystems available on the system are consistent. If they
@@ -454,7 +454,7 @@
</sect2>
<sect2 id="boot-singleuser">
- <title>Single-user mode</title>
+ <title>Single-User Mode</title>
<para>This mode can be reached through the <link
linkend="boot-autoreboot">automatic reboot
@@ -496,7 +496,7 @@
</sect2>
<sect2 id="boot-multiuser">
- <title>Multi-user mode</title>
+ <title>Multi-User Mode</title>
<para>If <command>init</command> finds your filesystems to be
in order, or once the user has finished in <link
@@ -505,7 +505,7 @@
resource configuration of the system.</para>
<sect3 id="boot-rc">
- <title>Resource configuration (rc)</title>
+ <title>Resource Configuration (rc)</title>
<para>The resource configuration system reads in
configuration defaults from
@@ -526,7 +526,7 @@
</sect1>
<sect1 id="boot-shutdown">
- <title>Shutdown sequence</title>
+ <title>Shutdown Sequence</title>
<para>Upon controlled shutdown, via <command>shutdown</command>,
<command>init</command> will attempt to run the script
Index: contrib/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v
retrieving revision 1.178
diff -u -r1.178 chapter.sgml
--- contrib/chapter.sgml 2000/04/02 08:56:38 1.178
+++ contrib/chapter.sgml 2000/04/02 19:24:24
@@ -41,7 +41,7 @@
to at least give it a second look.</para>
<sect1 id="contrib-what">
- <title>What Is Needed</title>
+ <title>What is Needed</title>
<para>The following list of tasks and sub-projects represents something of
an amalgam of the various core team <filename>TODO</filename> lists and
Index: disks/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v
retrieving revision 1.16
diff -u -r1.16 chapter.sgml
--- disks/chapter.sgml 2000/03/25 20:05:40 1.16
+++ disks/chapter.sgml 2000/04/02 19:24:26
@@ -15,7 +15,7 @@
</sect1>
<sect1 id="disks-naming">
- <title>Disk naming</title>
+ <title>Disk Naming</title>
<para>Physical drives come in two main flavours,
<acronym>IDE</acronym>, or <acronym>SCSI</acronym>; but there
@@ -24,7 +24,7 @@
own drivers and devices.</para>
<table id="disk-naming-physical-table">
- <title>Physical disk naming conventions</title>
+ <title>Physical Disk Naming Conventions</title>
<tgroup cols="2">
<thead>
@@ -92,7 +92,7 @@
</table>
<sect2>
- <title>Slices and partitions</title>
+ <title>Slices and Partitions</title>
<para>Physical disks usually contain
<firstterm>slices</firstterm>, unless they are
@@ -112,7 +112,7 @@
</sect1>
<sect1 id="disks-mounting">
- <title>Mounting and unmounting filesystems</title>
+ <title>Mounting and Unmounting Filesystems</title>
<para>The filesystem is best visualized as a tree,
rooted, as it were, at <filename>/</filename>.
@@ -135,7 +135,7 @@
drives.</para>
<sect2 id="disks-fstab">
- <title>The fstab file</title>
+ <title>The fstab File</title>
<para>During the <link linkend="boot">boot process</link>,
filesystems listed in <filename>/etc/fstab</filename> are
@@ -172,7 +172,7 @@
</sect2>
<sect2 id="disks-mount">
- <title>The mount command</title>
+ <title>The mount Command</title>
<para>The &man.mount.8; command is what is ultimately used to
mount filesystems.</para>
@@ -297,7 +297,7 @@
</sect2>
<sect2 id="disks-umount">
- <title>The umount command</title>
+ <title>The umount Command</title>
<para>The umount command takes, as a parameter, one of a
mountpoint, a device name, or the <option>-a</option> or
@@ -315,7 +315,7 @@
</sect1>
<sect1 id="disks-adding">
- <title>Adding disks</title>
+ <title>Adding Disks</title>
<para><emphasis>Originally contributed by &a.obrien; 26 April
1998</emphasis></para>
@@ -407,7 +407,7 @@
</sect2>
<sect2>
- <title>Using command line utilities</title>
+ <title>Using Command Line Utilities</title>
<sect3>
<title>* Using Slices</title>
@@ -446,7 +446,7 @@
</sect1>
<sect1 id="disks-virtual">
- <title>Virtual disks: Network, memory, and file-based filesystems</title>
+ <title>Virtual Disks: Network, Memory, and File-Based Filesystems</title>
<para>Besides the disks you physically insert into your computer;
floppies, CDs, hard drives, and so forth, other forms of disks
@@ -482,7 +482,7 @@
<para>To create a new filesystem image with vnconfig:</para>
<example>
- <title>Creating a new file-backed disk with vnconfig</title>
+ <title>Creating a New File-Backed Disk with vnconfig</title>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>newimage</replaceable> bs=1k count=<replaceable>5</replaceable>k</userinput>
5120+0 records in
@@ -503,7 +503,7 @@
</sect2>
<sect2 id="disks-md">
- <title>md: memory filesystem</title>
+ <title>md: Memory Filesystem</title>
<para>md is a simple, efficient means to do memory
filesystems.</para>
Index: eresources/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v
retrieving revision 1.40
diff -u -r1.40 chapter.sgml
--- eresources/chapter.sgml 2000/02/01 11:48:11 1.40
+++ eresources/chapter.sgml 2000/04/02 19:24:29
@@ -23,7 +23,7 @@
included.</para>
<sect1 id="eresources-mail">
- <title>Mailing lists</title>
+ <title>Mailing Lists</title>
<para>Though many of the FreeBSD development members read USENET, we
cannot always guarantee that we will get to your questions in a timely
@@ -49,7 +49,7 @@
should be consulted before posting a question.</para>
<sect2 id="eresources-summary">
- <title>List summary</title>
+ <title>List Summary</title>
<para><emphasis>General lists:</emphasis> The following are general
lists which anyone is free (and encouraged) to join:</para>
@@ -345,7 +345,7 @@
</sect2>
<sect2 id="eresources-subscribe">
- <title>How to subscribe</title>
+ <title>How to Subscribe</title>
<para>All mailing lists live on <hostid
role="fqdn">FreeBSD.org</hostid>, so to post to a given list you
@@ -391,7 +391,7 @@
</sect2>
<sect2 id="eresources-charters">
- <title>List charters</title>
+ <title>List Charters</title>
<para><emphasis>All</emphasis> FreeBSD mailing lists have certain basic
rules which must be adhered to by anyone using them. Failure to comply
@@ -906,7 +906,7 @@
</sect1>
<sect1 id="eresources-news">
- <title>Usenet newsgroups</title>
+ <title>Usenet Newsgroups</title>
<para>In addition to two FreeBSD specific newsgroups, there are many
others in which FreeBSD is discussed or are otherwise relevant to
@@ -916,7 +916,7 @@
from courtesy of Warren Toomey <email>wkt@cs.adfa.edu.au</email>.</para>
<sect2>
- <title>BSD specific newsgroups</title>
+ <title>BSD Specific Newsgroups</title>
<itemizedlist>
<listitem>
@@ -932,7 +932,7 @@
</sect2>
<sect2>
- <title>Other Unix newsgroups of interest</title>
+ <title>Other Unix Newsgroups of Interest</title>
<itemizedlist>
<listitem>
@@ -1049,7 +1049,7 @@
</sect1>
<sect1 id="eresources-web">
- <title>World Wide Web servers</title>
+ <title>World Wide Web Servers</title>
<itemizedlist>
<listitem>
Index: internals/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml,v
retrieving revision 1.18
diff -u -r1.18 chapter.sgml
--- internals/chapter.sgml 2000/03/17 10:51:47 1.18
+++ internals/chapter.sgml 2000/04/02 19:24:38
@@ -62,7 +62,7 @@
</sect1>
<sect1 id="dma">
- <title>DMA: What it Is and How it Works</title>
+ <title>DMA: What it is and How it Works</title>
<para><emphasis>Copyright © 1995,1997 &a.uhclem;, All Rights
Reserved. 10 December 1996. Last Update 8 October
@@ -1621,7 +1621,7 @@
</sect1>
<sect1 id="ipv6-implementation">
- <title>IPv6/IPsec implementation</title>
+ <title>IPv6/IPsec Implementation</title>
<para><emphasis>Contributed by &a.shin;, 5 March
2000.</emphasis></para>
Index: kerneldebug/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v
retrieving revision 1.21
diff -u -r1.21 chapter.sgml
--- kerneldebug/chapter.sgml 1999/12/16 16:04:24 1.21
+++ kerneldebug/chapter.sgml 2000/04/02 19:24:40
@@ -232,7 +232,7 @@
</sect1>
<sect1>
- <title>Debugging a crash dump with DDD</title>
+ <title>Debugging a Crash Dump with DDD</title>
<para>Examining a kernel crash dump with a graphical debugger like
<command>ddd</command> is also possible. Add the <option>-k</option>
@@ -246,7 +246,7 @@
</sect1>
<sect1>
- <title>Post-mortem Analysis of a Dump</title>
+ <title>Post-Mortem Analysis of a Dump</title>
<para>What do you do if a kernel dumped core but you did not expect it,
and it is therefore not compiled using <command>config -g</command>? Not
@@ -284,7 +284,7 @@
</sect1>
<sect1>
- <title>On-line Kernel Debugging Using DDB</title>
+ <title>On-Line Kernel Debugging Using DDB</title>
<para>While <command>kgdb</command> as an offline debugger provides a very
high level of user interface, there are some things it cannot do. The
@@ -479,7 +479,7 @@
</sect1>
<sect1>
- <title>On-line Kernel Debugging Using Remote GDB</title>
+ <title>On-Line Kernel Debugging Using Remote GDB</title>
<para>This feature has been supported since FreeBSD 2.2, and it is
actually a very neat one.</para>
Index: staff/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml,v
retrieving revision 1.112
diff -u -r1.112 chapter.sgml
--- staff/chapter.sgml 2000/03/22 19:07:58 1.112
+++ staff/chapter.sgml 2000/04/02 19:24:44
@@ -933,7 +933,7 @@
</sect1>
<sect1 id="staff-who">
- <title>Who Is Responsible for What</title>
+ <title>Who is Responsible for What</title>
<variablelist>
<varlistentry>
Index: users/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/users/chapter.sgml,v
retrieving revision 1.1
diff -u -r1.1 chapter.sgml
--- users/chapter.sgml 2000/03/08 11:12:22 1.1
+++ users/chapter.sgml 2000/04/02 19:24:44
@@ -5,7 +5,7 @@
-->
<chapter id="users">
- <title>Users and basic account management</title>
+ <title>Users and Basic Account Management</title>
<sect1 id="users-synopsis">
<title>Synopsis</title>
@@ -27,7 +27,7 @@
</sect1>
<sect1 id="users-superuser">
- <title>The superuser account</title>
+ <title>The Superuser Account</title>
<para>The superuser account, usually called
<username>root</username>, comes preconfigured, and facilitates
@@ -59,7 +59,7 @@
</sect1>
<sect1 id="users-system">
- <title>System accounts</title>
+ <title>System Accounts</title>
<para>System users are those used to run services such as DNS,
mail, web servers, and so forth. The reason for this is
@@ -79,7 +79,7 @@
</sect1>
<sect1 id="users-user">
- <title>User accounts</title>
+ <title>User Accounts</title>
<para>User accounts are the primary means of access for real
people to the system, and these accounts insulate the user and
@@ -98,7 +98,7 @@
</sect1>
<sect1 id="users-modifying">
- <title>Modifying accounts</title>
+ <title>Modifying Accounts</title>
<para><application>pw</application> is a powerful and flexible
means to modify accounts, but <application>adduser</application>
@@ -312,7 +312,7 @@
database.</para>
<example>
- <title>Interactive chpass by superuser</title>
+ <title>Interactive chpass by Superuser</title>
<screen>#Changing user database information for jru.
Login: jru
@@ -335,7 +335,7 @@
information, and only for themselves.</para>
<example>
- <title>Interactive chpass by normal user</title>
+ <title>Interactive chpass by Normal User</title>
<screen>#Changing user database information for jru.
Shell: /usr/local/bin/tcsh
@@ -398,7 +398,7 @@
</sect1>
<sect1 id="users-limiting-and-personalizing">
- <title>Limiting and personalizing users</title>
+ <title>Limiting and Personalizing Users</title>
<para>Quotas allow the system administrator to set disk usage
maximums, and users to check their disk usage, if quotas are
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000402142813.C27486>