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

Fix some miscellaneous typos.

Browse source 
Submitted by:	lss <lss@2ez.com>
This commit is contained in:
Jim Mock 2000-04-06 20:28:35 +00:00
parent f7f7adfb20
commit 2b4d281a37
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7015
4 changed files with 90 additions and 82 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.14 2000/03/15 23:00:40 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.15 2000/03/15 23:01:40 jim Exp $
-->
<chapter id="basics">
@ -10,7 +10,7 @@
<sect1>
<title>Synopsis</title>
<para><emphasis>Reritten by Chris Shumway
<para><emphasis>Rewritten by Chris Shumway
<email>cshumway@cdrom.com</email>, 10 Mar 2000.</emphasis></para>
<para>The following chapter will cover the basic commands and
@ -27,8 +27,8 @@
most pronounced, is that FreeBSD is a multi-user operating system.
The system can handle several users all working simultaneously on
completely unrelated tasks. The system is responsible for properly
sharing and managing requests for hardware devices, preferials,
memory, and cpu time evenly to each user.</para>
sharing and managing requests for hardware devices, peripherals,
memory, and CPU time evenly to each user.</para>
<para>Because the system is capable of supporting multiple users,
everything the system manages has a set of permissions governing who
@ -101,8 +101,8 @@
</informaltable>
<para>For the long directory listing by <command>ls -l</command>, a
column will show a files' permissions for the owner, group, and
everyone else. Here's how its broken up:</para>
column will show a file's permissions for the owner, group, and
everyone else. Here's how it is broken up:</para>
<screen>-rw-r--r--</screen>
@ -122,7 +122,7 @@
<literal>644</literal>, where each digit represents the three parts
of the file's permission.</para>
<para>This is all well and good files, but how does the system control
<para>This is all well and good, but how does the system control
permissions on devices? FreeBSD actually treats most hardware
devices as a file that programs can open, read, and write data to
just like any other file. These special device files are stored on
@ -145,7 +145,7 @@
<title>Directory Structures</title>
<para>Since FreeBSD uses its file systems to determine many
fundamental system operations, the hiarchy of the file system is
fundamental system operations, the hierarchy of the file system is
extremely important. Due to the fact that the &man.hier.7; man page
provides a complete description of the directory structure, it will
not be duplicated here. Please read &man.hier.7; for more
@ -163,11 +163,11 @@
<filename>/mnt</filename>, and <filename>/cdrom</filename>. These
directories are usually referenced to entries in the file
<filename>/etc/fstab</filename>. <filename>/etc/fstab</filename> is
a table of various file systems and mount points for refence by the
a table of various file systems and mount points for reference by the
system. Most of the file systems in <filename>/etc/fstab</filename>
are mounted automatically at boot time from the script &man.rc.8;
unless they contain the noauto option. Consult the &man.fstab.5;
manual page for more information on the format of the
unless they contain the <option>noauto</option> option. Consult the
&man.fstab.5; manual page for more information on the format of the
<filename>/etc/fstab</filename> file and the options it
contains.</para>
</sect1>
@ -185,8 +185,8 @@
from the FreeBSD Ports Collection that have much more power, such as
tcsh and bash.</para>
<para>Which shell do you use? Its really a matter of taste. If your
a C programmer you might feel more comfortable with a C-like shell
<para>Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as tcsh. If you've come from Linux or are new to a UNIX
command line interface you might try bash. The point is that each
shell has unique properties that may or may not work with your
@ -254,7 +254,7 @@
<row>
<entry><envar>TERM</envar></entry>
<entry>The name of the user's terminal. Used to determine the
capabilites of the terminal.</entry>
capabilities of the terminal.</entry>
</row>
<row>

58
en_US.ISO8859-1/books/handbook/introduction/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.25 2000/01/25 20:50:09 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.26 2000/01/31 19:22:16 jim Exp $
-->
<chapter id="introduction">
@ -22,7 +22,7 @@
architectures are also underway. For a brief overview of FreeBSD,
see the <link linkend="nutshell">next section</link>. You can also
read about <link linkend="history">the history of FreeBSD</link>,
or the <link linkend="relnotes">the current release</link>. If you
or the <link linkend="relnotes">current release</link>. If you
are interested in contributing something to the Project (code,
hardware, unmarked bills), see the <link
linkend="contrib">contributing to FreeBSD</link> section.</para>
@ -102,8 +102,8 @@
</listitem>
<listitem>
<para><emphasis>Multiuser facilities</emphasis> which allow many
people to use a FreeBSD system simulatenously for a variety
<para><emphasis>Multi-user facilities</emphasis> which allow many
people to use a FreeBSD system simultaneously for a variety
of things. This means, for example, that system peripherals
such as printers and tape drives are properly shared between
all users on the system or the network and that individual
@ -118,7 +118,7 @@
inter-operate easily with other systems as well act as an
enterprise server, providing vital functions such as NFS
(remote file access) and e-mail services or putting your
organization on the Internet with WWW, ftp, routing and
organization on the Internet with WWW, FTP, routing and
firewall (security) services.</para>
</listitem>
@ -156,8 +156,8 @@
<listitem>
<para>Thousands of additional and
<emphasis>easy-to-port</emphasis> applications available on
the Internet. FreeBSD is source code compatible with most
<emphasis>easy-to-port</emphasis> applications are available
on the Internet. FreeBSD is source code compatible with most
popular commercial Unix systems and thus most applications
require few, if any, changes to compile.</para>
</listitem>
@ -298,7 +298,7 @@
name server (DNS)? A firewall to keep people out of your
internal network? FreeBSD can easily turn that unused 386 or
486 PC sitting in the corner into an advanced router with
sophisticated packet filtering capabilities.</para>
sophisticated packet-filtering capabilities.</para>
</listitem>
<listitem>
@ -322,7 +322,7 @@
</itemizedlist>
<para>FreeBSD is available in both source and binary form on CDROM
and via anonymous ftp. See <link linkend="mirrors">Obtaining
and via anonymous FTP. See <link linkend="mirrors">Obtaining
FreeBSD</link> for more details.</para>
</sect2>
</sect1>
@ -370,7 +370,7 @@
with an eye towards improving FreeBSD's distribution channels for
those many unfortunates without easy access to the Internet.
Walnut Creek CDROM not only supported the idea of distributing
FreeBSD on CD but went so far as to provide the project with a
FreeBSD on CD but also went so far as to provide the project with a
machine to work on and a fast Internet connection. Without Walnut
Creek CDROM's almost unprecedented degree of faith in what was, at
the time, a completely unknown project, it is quite unlikely that
@ -423,21 +423,25 @@
<para>FreeBSD 2.2 was branched from the development mainline
(&ldquo;-CURRENT&rdquo;) in November 1996 as the RELENG_2_2
branch, and the first full release (2.2.1) was released in April,
branch, and the first full release (2.2.1) was released in April
1997. Further releases along the 2.2 branch were done in the
Summer and Fall of '97, the last of which (2.2.8) appeared in
November, 1998. The first official 3.0 release appeared in
October, 1998 and spelled the beginning of the end for the 2.2
summer and fall of '97, the last of which (2.2.8) appeared in
November 1998. The first official 3.0 release appeared in
October 1998 and spelled the beginning of the end for the 2.2
branch.</para>
<para>The tree branched again on Jan 20, 1999, leading to the
4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was
released on February 15, 1999, 3.2 on May 15, 1999, and 3.3 on
September 16, 1999. The most current release on this branch is
&rel.current;, which was released on December 20, 1999.</para>
3.4, which was released on December 20, 1999.</para>
<para>Long term development projects continue to take place in the
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and, of
<para>There was another branch on March 13, 2000, which saw the
emergence of the 5.0-CURRENT and 4.X-STABLE branches. The only
release from this branch so far is &rel.current;-RELEASE.</para>
<para>Long-term development projects continue to take place in the
5.0-CURRENT branch, and SNAPshot releases of 5.0 on CDROM (and, of
course, on the net) are continually made available as work
progresses.</para>
</sect2>
@ -497,7 +501,7 @@
<para>The central source tree for FreeBSD is maintained by
<ulink url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
(Concurrent Version System), a freely available source code
control tool which comes bundled with FreeBSD. The primary
control tool that comes bundled with FreeBSD. The primary
<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
repository</ulink> resides on a machine in Concord CA, USA
from where it is replicated to numerous mirror machines
@ -559,7 +563,7 @@
analogy above is not actually very accurate, and it may be
more suitable to say that these are the people who gave up
their lives in favor of FreeBSD against their better
judgement! <!-- smiley --><emphasis>;-)</emphasis></para>
judgment! <!-- smiley --><emphasis>;-)</emphasis></para>
</note>
</listitem>
</varlistentry>
@ -570,15 +574,15 @@
<listitem>
<para>Last, but definitely not least, the largest group of
developers are the users themselves who provide feedback and
bug-fixes to us on an almost constant basis. The primary
bug fixes to us on an almost constant basis. The primary
way of keeping in touch with FreeBSD's more non-centralized
development is to subscribe to the &a.hackers; (see <link
linkend="eresources-mail">mailing list info</link>) where
such things are discussed.</para>
<para><link linkend="contrib-additional">The list</link> of
those who have contributed something which made its way into
our source tree is a long and growing one, so why not join
those who have contributed something, which made its way into
our source tree, is a long and growing one, so why not join
it by contributing something back to FreeBSD today?
<!-- smiley --><emphasis>:-)</emphasis></para>
@ -618,7 +622,7 @@
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
feature set, and stability of FreeBSD has improved dramatically.
The largest change is a revamped virtual memory system with a merged
VM/file buffer cache that not only increases performance, but
VM/file buffer cache that not only increases performance, but also
reduces FreeBSD's memory footprint, making a 5MB configuration a
more acceptable minimum. Other enhancements include full NIS client
and server support, transaction TCP support, dial-on-demand PPP,
@ -632,7 +636,7 @@
sane and easily understood installation process. Your feedback on
this (constantly evolving) process is especially welcome!</para>
<para>In addition to the base distributions, FreeBSD offers a new
<para>In addition to the base distributions, FreeBSD offers a
ported software collection with hundreds of commonly sought-after
programs. By mid-January 2000, there were nearly 3000 ports! The
list of ports ranges from http (WWW) servers, to games, languages,
@ -644,10 +648,10 @@
compile a port, you simply change to the directory of the program
you wish to install, type <command>make install</command>, and let
the system do the rest. The full original distribution for each
port you build is retrieved dynamically off the CDROM or a local ftp
port you build is retrieved dynamically off the CDROM or a local FTP
site, so you need only enough disk space to build the ports you
want. Almost every port is also provided as a pre-compiled
&ldquo;package&rdquo; which can be installed with a simple command
&ldquo;package&rdquo;, which can be installed with a simple command
(pkg_add) by those who do not wish to compile their own ports from
source.</para>
@ -685,7 +689,7 @@
<para>The core of FreeBSD does not contain DES code which would
inhibit its being exported outside the United States. There is an
add-on package to the core distribution, for use only in the United
States, that contains the programs that normally use DES. The
States, which contains the programs that normally use DES. The
auxiliary packages provided separately can be used by anyone. A
freely (from outside the U.S.) exportable European distribution of
DES for our non-U.S. users also exists and is described in the

28
en_US.ISO_8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.14 2000/03/15 23:00:40 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.15 2000/03/15 23:01:40 jim Exp $
-->
<chapter id="basics">
@ -10,7 +10,7 @@
<sect1>
<title>Synopsis</title>
<para><emphasis>Reritten by Chris Shumway
<para><emphasis>Rewritten by Chris Shumway
<email>cshumway@cdrom.com</email>, 10 Mar 2000.</emphasis></para>
<para>The following chapter will cover the basic commands and
@ -27,8 +27,8 @@
most pronounced, is that FreeBSD is a multi-user operating system.
The system can handle several users all working simultaneously on
completely unrelated tasks. The system is responsible for properly
sharing and managing requests for hardware devices, preferials,
memory, and cpu time evenly to each user.</para>
sharing and managing requests for hardware devices, peripherals,
memory, and CPU time evenly to each user.</para>
<para>Because the system is capable of supporting multiple users,
everything the system manages has a set of permissions governing who
@ -101,8 +101,8 @@
</informaltable>
<para>For the long directory listing by <command>ls -l</command>, a
column will show a files' permissions for the owner, group, and
everyone else. Here's how its broken up:</para>
column will show a file's permissions for the owner, group, and
everyone else. Here's how it is broken up:</para>
<screen>-rw-r--r--</screen>
@ -122,7 +122,7 @@
<literal>644</literal>, where each digit represents the three parts
of the file's permission.</para>
<para>This is all well and good files, but how does the system control
<para>This is all well and good, but how does the system control
permissions on devices? FreeBSD actually treats most hardware
devices as a file that programs can open, read, and write data to
just like any other file. These special device files are stored on
@ -145,7 +145,7 @@
<title>Directory Structures</title>
<para>Since FreeBSD uses its file systems to determine many
fundamental system operations, the hiarchy of the file system is
fundamental system operations, the hierarchy of the file system is
extremely important. Due to the fact that the &man.hier.7; man page
provides a complete description of the directory structure, it will
not be duplicated here. Please read &man.hier.7; for more
@ -163,11 +163,11 @@
<filename>/mnt</filename>, and <filename>/cdrom</filename>. These
directories are usually referenced to entries in the file
<filename>/etc/fstab</filename>. <filename>/etc/fstab</filename> is
a table of various file systems and mount points for refence by the
a table of various file systems and mount points for reference by the
system. Most of the file systems in <filename>/etc/fstab</filename>
are mounted automatically at boot time from the script &man.rc.8;
unless they contain the noauto option. Consult the &man.fstab.5;
manual page for more information on the format of the
unless they contain the <option>noauto</option> option. Consult the
&man.fstab.5; manual page for more information on the format of the
<filename>/etc/fstab</filename> file and the options it
contains.</para>
</sect1>
@ -185,8 +185,8 @@
from the FreeBSD Ports Collection that have much more power, such as
tcsh and bash.</para>
<para>Which shell do you use? Its really a matter of taste. If your
a C programmer you might feel more comfortable with a C-like shell
<para>Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as tcsh. If you've come from Linux or are new to a UNIX
command line interface you might try bash. The point is that each
shell has unique properties that may or may not work with your
@ -254,7 +254,7 @@
<row>
<entry><envar>TERM</envar></entry>
<entry>The name of the user's terminal. Used to determine the
capabilites of the terminal.</entry>
capabilities of the terminal.</entry>
</row>
<row>

58
en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.25 2000/01/25 20:50:09 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.26 2000/01/31 19:22:16 jim Exp $
-->
<chapter id="introduction">
@ -22,7 +22,7 @@
architectures are also underway. For a brief overview of FreeBSD,
see the <link linkend="nutshell">next section</link>. You can also
read about <link linkend="history">the history of FreeBSD</link>,
or the <link linkend="relnotes">the current release</link>. If you
or the <link linkend="relnotes">current release</link>. If you
are interested in contributing something to the Project (code,
hardware, unmarked bills), see the <link
linkend="contrib">contributing to FreeBSD</link> section.</para>
@ -102,8 +102,8 @@
</listitem>
<listitem>
<para><emphasis>Multiuser facilities</emphasis> which allow many
people to use a FreeBSD system simulatenously for a variety
<para><emphasis>Multi-user facilities</emphasis> which allow many
people to use a FreeBSD system simultaneously for a variety
of things. This means, for example, that system peripherals
such as printers and tape drives are properly shared between
all users on the system or the network and that individual
@ -118,7 +118,7 @@
inter-operate easily with other systems as well act as an
enterprise server, providing vital functions such as NFS
(remote file access) and e-mail services or putting your
organization on the Internet with WWW, ftp, routing and
organization on the Internet with WWW, FTP, routing and
firewall (security) services.</para>
</listitem>
@ -156,8 +156,8 @@
<listitem>
<para>Thousands of additional and
<emphasis>easy-to-port</emphasis> applications available on
the Internet. FreeBSD is source code compatible with most
<emphasis>easy-to-port</emphasis> applications are available
on the Internet. FreeBSD is source code compatible with most
popular commercial Unix systems and thus most applications
require few, if any, changes to compile.</para>
</listitem>
@ -298,7 +298,7 @@
name server (DNS)? A firewall to keep people out of your
internal network? FreeBSD can easily turn that unused 386 or
486 PC sitting in the corner into an advanced router with
sophisticated packet filtering capabilities.</para>
sophisticated packet-filtering capabilities.</para>
</listitem>
<listitem>
@ -322,7 +322,7 @@
</itemizedlist>
<para>FreeBSD is available in both source and binary form on CDROM
and via anonymous ftp. See <link linkend="mirrors">Obtaining
and via anonymous FTP. See <link linkend="mirrors">Obtaining
FreeBSD</link> for more details.</para>
</sect2>
</sect1>
@ -370,7 +370,7 @@
with an eye towards improving FreeBSD's distribution channels for
those many unfortunates without easy access to the Internet.
Walnut Creek CDROM not only supported the idea of distributing
FreeBSD on CD but went so far as to provide the project with a
FreeBSD on CD but also went so far as to provide the project with a
machine to work on and a fast Internet connection. Without Walnut
Creek CDROM's almost unprecedented degree of faith in what was, at
the time, a completely unknown project, it is quite unlikely that
@ -423,21 +423,25 @@
<para>FreeBSD 2.2 was branched from the development mainline
(&ldquo;-CURRENT&rdquo;) in November 1996 as the RELENG_2_2
branch, and the first full release (2.2.1) was released in April,
branch, and the first full release (2.2.1) was released in April
1997. Further releases along the 2.2 branch were done in the
Summer and Fall of '97, the last of which (2.2.8) appeared in
November, 1998. The first official 3.0 release appeared in
October, 1998 and spelled the beginning of the end for the 2.2
summer and fall of '97, the last of which (2.2.8) appeared in
November 1998. The first official 3.0 release appeared in
October 1998 and spelled the beginning of the end for the 2.2
branch.</para>
<para>The tree branched again on Jan 20, 1999, leading to the
4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was
released on February 15, 1999, 3.2 on May 15, 1999, and 3.3 on
September 16, 1999. The most current release on this branch is
&rel.current;, which was released on December 20, 1999.</para>
3.4, which was released on December 20, 1999.</para>
<para>Long term development projects continue to take place in the
4.0-CURRENT branch, and SNAPshot releases of 4.0 on CDROM (and, of
<para>There was another branch on March 13, 2000, which saw the
emergence of the 5.0-CURRENT and 4.X-STABLE branches. The only
release from this branch so far is &rel.current;-RELEASE.</para>
<para>Long-term development projects continue to take place in the
5.0-CURRENT branch, and SNAPshot releases of 5.0 on CDROM (and, of
course, on the net) are continually made available as work
progresses.</para>
</sect2>
@ -497,7 +501,7 @@
<para>The central source tree for FreeBSD is maintained by
<ulink url="http://www.cyclic.com/cyclic-pages/CVS-sheet.html">CVS</ulink>
(Concurrent Version System), a freely available source code
control tool which comes bundled with FreeBSD. The primary
control tool that comes bundled with FreeBSD. The primary
<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
repository</ulink> resides on a machine in Concord CA, USA
from where it is replicated to numerous mirror machines
@ -559,7 +563,7 @@
analogy above is not actually very accurate, and it may be
more suitable to say that these are the people who gave up
their lives in favor of FreeBSD against their better
judgement! <!-- smiley --><emphasis>;-)</emphasis></para>
judgment! <!-- smiley --><emphasis>;-)</emphasis></para>
</note>
</listitem>
</varlistentry>
@ -570,15 +574,15 @@
<listitem>
<para>Last, but definitely not least, the largest group of
developers are the users themselves who provide feedback and
bug-fixes to us on an almost constant basis. The primary
bug fixes to us on an almost constant basis. The primary
way of keeping in touch with FreeBSD's more non-centralized
development is to subscribe to the &a.hackers; (see <link
linkend="eresources-mail">mailing list info</link>) where
such things are discussed.</para>
<para><link linkend="contrib-additional">The list</link> of
those who have contributed something which made its way into
our source tree is a long and growing one, so why not join
those who have contributed something, which made its way into
our source tree, is a long and growing one, so why not join
it by contributing something back to FreeBSD today?
<!-- smiley --><emphasis>:-)</emphasis></para>
@ -618,7 +622,7 @@
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
feature set, and stability of FreeBSD has improved dramatically.
The largest change is a revamped virtual memory system with a merged
VM/file buffer cache that not only increases performance, but
VM/file buffer cache that not only increases performance, but also
reduces FreeBSD's memory footprint, making a 5MB configuration a
more acceptable minimum. Other enhancements include full NIS client
and server support, transaction TCP support, dial-on-demand PPP,
@ -632,7 +636,7 @@
sane and easily understood installation process. Your feedback on
this (constantly evolving) process is especially welcome!</para>
<para>In addition to the base distributions, FreeBSD offers a new
<para>In addition to the base distributions, FreeBSD offers a
ported software collection with hundreds of commonly sought-after
programs. By mid-January 2000, there were nearly 3000 ports! The
list of ports ranges from http (WWW) servers, to games, languages,
@ -644,10 +648,10 @@
compile a port, you simply change to the directory of the program
you wish to install, type <command>make install</command>, and let
the system do the rest. The full original distribution for each
port you build is retrieved dynamically off the CDROM or a local ftp
port you build is retrieved dynamically off the CDROM or a local FTP
site, so you need only enough disk space to build the ports you
want. Almost every port is also provided as a pre-compiled
&ldquo;package&rdquo; which can be installed with a simple command
&ldquo;package&rdquo;, which can be installed with a simple command
(pkg_add) by those who do not wish to compile their own ports from
source.</para>
@ -685,7 +689,7 @@
<para>The core of FreeBSD does not contain DES code which would
inhibit its being exported outside the United States. There is an
add-on package to the core distribution, for use only in the United
States, that contains the programs that normally use DES. The
States, which contains the programs that normally use DES. The
auxiliary packages provided separately can be used by anyone. A
freely (from outside the U.S.) exportable European distribution of
DES for our non-U.S. users also exists and is described in the