[pkgsrc/trunk]: pkgsrc/doc filesystem -> file system; properly case NetBSD; f...

[wiz <wiz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/f346737b7942
branches:  trunk
changeset: 538645:f346737b7942
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Fri Feb 15 07:37:11 2008 +0000

description:
filesystem -> file system; properly case NetBSD; fix a typo.

diffstat:

 doc/HOWTO-pbulk |  10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diffs (37 lines):

diff -r 1170a3020e72 -r f346737b7942 doc/HOWTO-pbulk
--- a/doc/HOWTO-pbulk   Fri Feb 15 06:36:25 2008 +0000
+++ b/doc/HOWTO-pbulk   Fri Feb 15 07:37:11 2008 +0000
@@ -1,12 +1,12 @@
-Step One: Suggested Filesystem Layout
+Step One: Suggested File System Layout
 
 For the DragonFly builds I'm using:
 - /bulklog for the bulk meta data and log files of each package
 - /scratch as WRKOBJDIR
 - /distfiles as DISTDIR
 - /packages as PACKAGES
-- separate physical filesystems for /var and /usr/pkg
-All filesystems but those are read-only, /tmp and /dev need platform
+- separate physical file systems for /var and /usr/pkg
+All file systems but those are read-only, /tmp and /dev need platform
 specific handling either as tmpfs or link. ptyfs helps for /dev.
 
 For parallel builds, /bulklog, /packages and /usr/pkgsrc are supposed to
@@ -17,7 +17,7 @@
 
 Install pkgtools/pbulk and possibly helper programs like screen into
 LOCALBASE=/usr/pkg_bulk, PKG_DBDIR=/usr/pkg_bulk/.pkgdb. A full
-bootstrap is the recommented approach. Copy /usr/pkg_bulk to the client
+bootstrap is the recommended approach. Copy /usr/pkg_bulk to the client
 nodes for parallel builds.
 
 Step Three: Configure pbulk
@@ -26,7 +26,7 @@
 Setup general build parameters in mk.conf. Below is an example
 fragment to add.
 
-(b) [not for netbsd]
+(b) [not for NetBSD]
 Build a binary bootstrap kit and override the included mk.conf with the
 file created in (a). Compress the tarball with gzip.