Date: Mon, 03 Dec 2001 16:43:25 +0000 From: Ceri <setantae@submonkey.net> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/32474: Minor nitpicks in the config chapter of the handbook Message-ID: <E16AwBh-00022I-00@rhadamanth.private.submonkey.net>
next in thread | raw e-mail | index | archive | help
>Number: 32474
>Category: docs
>Synopsis: Minor nitpicks in the config chapter of the handbook
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Dec 03 08:50:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Ceri <setantae@submonkey.net>
>Release: FreeBSD 4.4-STABLE i386
>Organization:
>Environment:
System: FreeBSD rhadamanth.private.submonkey.net 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Nov 26 13:11:22 GMT 2001 setantae@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386
Today's doc tree
>Description:
There are a couple of minor grammatical issues with the config section
of the handbook.
>How-To-Repeat:
Read it while feeling very fussy.
>Fix:
Herewith a patch.
Ceri
--- doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml.old Mon Dec 3 16:08:40 2001
+++ doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml Mon Dec 3 16:38:17 2001
@@ -50,14 +50,14 @@
<itemizedlist>
<listitem>
<para>Why and how to efficiently size, layout, and place
- filesystems and swap partition on your hard drive.</para>
+ filesystems and swap partitions on your hard drive.</para>
</listitem>
<listitem>
<para>The basics of the <filename>rc.conf</filename> configuration and
<filename>/usr/local/etc/rc.d</filename> startup systems.</para>
</listitem>
<listitem>
- <para>How to configure virtual hosts on your network device.</para>
+ <para>How to configure virtual hosts on your network devices.</para>
</listitem>
<listitem>
<para>How to use the various configuration files in
@@ -123,7 +123,7 @@
<para>The size of your <filename>/var</filename> partition
reflects the intended use of your machine.
<filename>/var</filename> is primarily used to hold:
- mailboxes, print spool and log files. Mail boxes and log
+ mailboxes, print spool and log files. Mailboxes and log
files, in particular, can grow to unexpected sizes based upon
how many users are on your system and how long your log files
are kept. If you intend to run a mail server, a
@@ -315,7 +315,7 @@
configuration files for the application, they will be created by
copying the .default files.</para>
- <para>For example, here is
+ <para>For example, consider the contents of the directory
<filename>/usr/local/etc/apache</filename>:</para>
<literallayout class="monospaced">-rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf
@@ -704,7 +704,7 @@
<filename>logfile</filename> is moved to
<filename>logfile.0</filename>, <filename>logfile.0</filename>
is moved to <filename>logfile.1</filename>, and so on.
- Additionally, the log files may be archived in &man.gzip.1; format
+ Alternatively, the log files may be archived in &man.gzip.1; format
causing them to be named: <filename>logfile.0.gz</filename>,
<filename>logfile.1.gz</filename>, and so on.</para>
@@ -775,8 +775,8 @@
administrator. Over five hundred system variables can be read
and set using &man.sysctl.8;.</para>
- <para>At its core, &man.sysctl.8; serves to do two functions: read and
- modify system settings.</para>
+ <para>At its core, &man.sysctl.8; serves two functions: to read and
+ to modify system settings.</para>
<para>To view all readable variables:</para>
@@ -889,8 +889,9 @@
are two downsides to Soft Updates that you should be aware of: First,
Soft Updates guarantees filesystem consistency in the case of a crash
but could very easily be several
- seconds (even a minute!) behind updating the physical disk. If you
- crash you may lose more work than otherwise. Secondly, Soft Updates
+ seconds (even a minute!) behind updating the physical disk. If your
+ system
+ crashes you may lose more work than otherwise. Secondly, Soft Updates
delays the freeing of filesystem blocks. If you have a filesystem
(such as the root filesystem) which is close to full, doing a major
update of it, e.g. <command>make installworld</command>, can run it
@@ -943,7 +944,7 @@
<title>Network Limits</title>
<para>The <varname>NMBCLUSTERS</varname> kernel configuration
- option dictate the amount of network mbufs available to the
+ option dictates the amount of network mbufs available to the
system. A heavily-trafficked server with a low number of MBUFs
will hinder FreeBSD's ability. Each cluster represents
approximately 2K of memory, so a value of 1024 represents 2
>Release-Note:
>Audit-Trail:
>Unformatted:
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?E16AwBh-00022I-00>