More tpyos, speelling and gramer

1 files changed, 17 insertions, 17 deletions

diff --git a/Packages.txt b/Packages.txt
index 5e57e958bea..d9ad4db7aa7 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.190 2001/09/21 08:36:50 skrll Exp $
+# $NetBSD: Packages.txt,v 1.191 2001/09/21 09:04:22 skrll Exp $
 ###########################################################################
 
 			==========================
@@ -22,7 +22,7 @@ Run this command to produce a table of contents:
 There is a lot of software freely available for Unix based systems, which
 usually runs on NetBSD, too, sometimes with some modifications. The NetBSD
 packages collection incorporates any such changes necessary to make that
-software run on NetBSD, and makes the installation (and reinstallation) of
+software run on NetBSD, and makes the installation (and re-installation) of
 the software package easy by means of a single command.
 
 The NetBSD package system is used to enable such freely available
@@ -105,7 +105,7 @@ Right now this document is written in plain ASCII text, and there's not
 much typography applied here. Future versions may move to something like
 HTML or DocBook, which have better ways theres.
 
-When giving examples for comands, shell prompts are used to show if the
+When giving examples for commands, shell prompts are used to show if the
 command should/can be issued as root, or if "normal" user privileges are
 sufficient. We use a "#" for root's shell prompt, and a "%" for users'
 shell prompt, assuming they use the C-shell or tcsh.
@@ -285,7 +285,7 @@ an overview of what you can set there.  Environment variables such as
 LOCALBASE, and X11BASE can also be set in /etc/mk.conf to save having
 to remember to set them each time you want to use pkgsrc.
 
-If you want to deinstall and re-install a binary package that you've
+If you want to de-install and re-install a binary package that you've
 created (see next section), that you put into pkgsrc/packages manually or
 that's located on a remote FTP server, you can use the the "bin-install"
 target. This target will install a binary package - if available - via
@@ -382,7 +382,7 @@ the only package for which BULK_PREREQ makes sense is xpkgwedge.
 
 In pkgsrc/mk/bulk, copy ``build.conf-example'' to ``build.conf'' and
 edit it, following the comments in that file. This is the config
-file that determines where logfiles are generated after the build,
+file that determines where log files are generated after the build,
 where to mail the build report, where your pkgsrc is located and
 which user to su(8) to to do a 'cvs update'.
 
@@ -429,7 +429,7 @@ or crashes. You have been warned! :)
 
 Make sure you don't need any of the packages still installed.
 BEWARE: During the bulk build, ALL packages will be removed!!!
-Be sure to remove all other things that might interfer with builds, like 
+Be sure to remove all other things that might interfere with builds, like 
 some libs installed in /usr/local, etc. then become root and type:
 
         # cd /usr/pkgsrc
@@ -453,7 +453,7 @@ The bulk builds consist of three steps:
 1. pre-build: The script updates your pkgsrc via (anon)cvs, then cleans
 	out any broken distfiles, and removes all packages installed.
 
-2. the bulk build: This is basically 'make bulk-package' with an optimized
+2. the bulk build: This is basically 'make bulk-package' with an optimised
 	order in which packages will be built. Packages that don't require
 	other packages will be built first, and packages with many depends
 	will be built later.
@@ -484,7 +484,7 @@ For 1.5/alpha:
 
  * Full set of all binaries:          1300MB (NFS ok)
 
-Note that all pkgs will be deinstalled as soon as they are turned into a
+Note that all pkgs will be de-installed as soon as they are turned into a
 binary package, and that work-sources are removed, so there is no huge
 demand to disk space. Afterwards, if the package is needed again, it will
 be installed via pkg_add instead of building again, so there are no cycles
@@ -944,7 +944,7 @@ expansions to this variable in the following way:
 
 	   PLIST_SUBST+=    SOMEVAR="somevalue"
 
-which replaces all occurances of ${SOMEVAR} in the PLIST with "somevalue".
+which replaces all occurrences of ${SOMEVAR} in the PLIST with "somevalue".
 For the values which are replaced by default, please look in bsd.pkg.mk
 (and search for PLIST_SUBST).
 
@@ -1088,7 +1088,7 @@ The pkg's own libtool is made by ltconfig script at do-configure target.
 If USE_LIBTOOL and LTCONFIG_OVERRIDE are defined, the specified ltconfig is
 overridden, using the pkgsrc/devel/libtool instead of the pkg's own libtool.
 
-If your package makes use of the platform independant library for loading
+If your package makes use of the platform independent library for loading
 dynamic shared objects, that comes with libtool (libltdl), you should
 add USE_LTDL= yes to the Makefile.
 
@@ -1377,7 +1377,7 @@ perform the equivalent of:
 
  * update:
    This target causes the current package to be updated to the latest
-   version.  The package and all depending packages first get deinstalled,
+   version.  The package and all depending packages first get de-installed,
    then current versions of the corresponding packages get compiled and
    installed.  This is similar to manually noting which packages are
    currently installed, then performing a series of "make deinstall" and
@@ -1420,7 +1420,7 @@ perform the equivalent of:
    Clean the source tree for all packages that would get updated if
    "make update" was called from the current directory.  This target
    should not be used if the current package (or any of its depending
-   packages) have already been deinstalled (e.g., after calling "make
+   packages) have already been de-installed (e.g., after calling "make
    update") or you may lose some packages you intended to update.
    As a rule of thumb: only use this target _before_ the first time
    you call "make update" and only if you have a dirty package tree
@@ -1540,8 +1540,8 @@ these files is two-fold:
  8.1 Using buildlink.mk files
  ============================
 
-Goal (1) is accomplished by simply including a package dependency's
-buildlink.mk file in a package's Makefile, which does the following:
+Goal (1) is accomplished by simply including the buildlink.mk file of a
+dependency in the package's Makefile, which does the following:
 
  (1a) Adds a DEPENDS or BUILD_DEPENDS line for the package;
 
@@ -1971,7 +1971,7 @@ You can also use wildcards in package dependences:
 Note that such wildcard dependencies are retained when creating binary
 packages.  The dependency is checked when installing the binary
 package and any package which matches the pattern will be used. 
-Wildard dependencies should be used with care.
+Wildcard dependencies should be used with care.
 
 For example, if a package needs any version of Tk installed, but does
 not require an explicit version of Tk:
@@ -2113,7 +2113,7 @@ that can be set to note these restrictions:
  * NO_BIN_ON_FTP:
    Binaries may not be placed on an ftp server.  Set this
    variable to ${RESTRICTED} whenever a binary package may not
-   not be made available on the internet.
+   not be made available on the Internet.
  
  * NO_SRC_ON_CDROM:
    Distfiles may not be placed on CD-ROM.  Set this variable to
@@ -2123,7 +2123,7 @@ that can be set to note these restrictions:
  * NO_SRC_ON_FTP:
    Distfiles may not be placed on FTP.  Set this variable to
    ${RESTRICTED} if re-distribution of the source code or other
-   distfile(s) via the internet is not allowed.
+   distfile(s) via the Internet is not allowed.
 
 Please note that the use of NO_PACKAGE, IGNORE, NO_CDROM, or other generic
 make variables to denote restrictions is deprecated, because they