os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Spelling Changes:

Browse source 
* OSs -> Operating Systems
* commmunications -> communications
* realise -> realize
* customising -> customizing
* customise -> customize
* realise -> realize
* behaviour -> behavior

British to American spelling for some of the above words only in the
Handbook as discussed on -doc.

Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-08-06 21:25:28 +00:00
parent 31d095639c
commit c20dd61362
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10210
6 changed files with 16 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.68 2001/08/06 20:25:01 chern Exp $
-->
<chapter id="advanced-networking">
@ -1876,7 +1876,7 @@ ISDN BRI line</literallayout>
maps! FreeBSD includes a script named
<command>ypinit</command> to do this for you
(see its man page for more information). Note that this
script is available on most Unix OSs, but not on all.
script is available on most Unix Operating Systems, but not on all.
On Digital Unix/Compaq Tru64 Unix it is called
<command>ypsetup</command>.
Because we are generating maps for an NIS master, we are

8
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.34 2001/07/30 23:44:00 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.35 2001/08/04 20:06:20 jim Exp $
-->
<chapter id="basics">
@ -344,7 +344,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
might imagine.</para>
<para>Sometimes you will need to communicate with a daemon process. These
commmunications are called <firstterm>signals</firstterm>, and you can
communications are called <firstterm>signals</firstterm>, and you can
communicate with daemons (or with any running process) by sending it a
signal. There are a number if different signals that you can
send&mdash;some of them have a specific meaning, others are interpreted
@ -366,7 +366,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<para>Two signals can be used to stop a process,
<literal>SIGTERM</literal> and <literal>SIGKILL</literal>.
<literal>SIGTERM</literal> is the polite way to kill a process; the
process can <emphasis>catch</emphasis> the signal, realise that you want
process can <emphasis>catch</emphasis> the signal, realize that you want
it to shut down, close any log files it may have open, and generally
finish whatever it is doing at the time before shutting down. In some
cases a process may even ignore <literal>SIGTERM</literal> if it is in
@ -401,7 +401,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
file. So instead of killing and restarting <command>httpd</command> you
would send it the <literal>SIGHUP</literal> signal. Because there is no
standard way to respond to these signals, different daemons will have
different behaviour, so be sure and read the documentation for the
different behavior, so be sure and read the documentation for the
daemon in question.</para>
<para>Signals are sent using the &man.kill.1; command, as this example

6
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.19 2001/08/04 04:07:17 jim Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.20 2001/08/04 19:00:04 jim Exp $
-->
<chapter id="boot">
@ -15,13 +15,13 @@
<para>The process of starting a computer and loading the operating system
is referred to as <quote>the bootstrap process</quote>, or simply
<quote>booting</quote>. FreeBSD's boot process provides a great deal of
flexibility in customising what happens when you start the system,
flexibility in customizing what happens when you start the system,
allowing you to select from different operating systems installed on the
same computer, or even different versions of the same operating system
or installed kernel.</para>
<para>This chapter details the configuration options you can set and how
to customise the FreeBSD boot process. This includes everything that
to customize the FreeBSD boot process. This includes everything that
happens until the FreeBSD kernel has started, probed for devices, and
started &man.init.8;. If you are not quite sure when this happens, it
occurs when the text color changes from bright white to grey.</para>

6
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.55 2001/08/02 00:47:33 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.56 2001/08/05 19:25:16 jim Exp $
-->
<chapter id="kernelconfig">
@ -62,7 +62,7 @@
<para>Traditionally FreeBSD has had what is called a
<quote>monolithic</quote> kernel. This means that the kernel was one
large program, supported a fixed list of devices, and if you wanted to
change the kernel's behaviour then you had to compile a new kernel, and
change the kernel's behavior then you had to compile a new kernel, and
then reboot your computer with the new kernel.</para>
<para>Today, FreeBSD is rapidly moving to a model where much of the
@ -165,7 +165,7 @@
<filename>/usr/src</filename> can be a bad idea. If you are
experiencing problems it can be tempting to just delete
<filename>/usr/src</filename> and start again. Five seconds after
you do that you realise that you have deleted your custom kernel
you do that you realize that you have deleted your custom kernel
config file.</para>
<para>You might want to keep your kernel config file elsewhere, and then

4
en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.32 2001/06/17 12:29:19 schweikh Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.33 2001/07/06 13:03:01 dd Exp $
-->
<chapter id="kerneldebug">
@ -334,7 +334,7 @@
for serial consoles that allows the use of a serial line BREAK on the
console line to enter DDB (<literal>options BREAK_TO_DEBUGGER</literal>
in the kernel config file). It is not the default since there are a lot
of crappy serial adapters around that gratuitously generate a BREAK
of low quality serial adapters around that gratuitously generate a BREAK
condition, for example when pulling the cable.</para>
<para>The third way is that any panic condition will branch to DDB if the

4
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.35 2001/08/06 12:17:47 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.36 2001/08/06 12:36:16 murray Exp $
-->
<chapter id="serialcomms">
@ -1344,7 +1344,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<para>For example to set the <literal>termios</literal> flag
<varname>crtscts</varname> on serial port #1's
(<devicename>COM2:</devicename>) dial-in and dial-out initialization
devices, the folling lines could be added to
devices, the following lines could be added to
<filename>/etc/rc.serial</filename> :</para>
<programlisting># Serial port initial configuration
stty -f /dev/ttyid1 crtscts