[pkgsrc/trunk]: pkgsrc/doc/guide/files fix typo

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/6a71507d5df1
branches:  trunk
changeset: 533630:6a71507d5df1
user:      kano <kano%pkgsrc.org@localhost>
date:      Sat Sep 22 02:52:48 2007 +0000

description:
fix typo

diffstat:

 doc/guide/files/options.xml |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r 90abdfe6746b -r 6a71507d5df1 doc/guide/files/options.xml
--- a/doc/guide/files/options.xml       Sat Sep 22 00:12:33 2007 +0000
+++ b/doc/guide/files/options.xml       Sat Sep 22 02:52:48 2007 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: options.xml,v 1.23 2007/09/21 13:28:29 gdt Exp $ -->
+<!-- $NetBSD: options.xml,v 1.24 2007/09/22 02:52:48 kano Exp $ -->
 
 <!-- based on: pkgsrc/mk/bsd.options.mk 1.56 -->
 
@@ -15,7 +15,7 @@
 
 <para>There are two broad classes of behaviors that one might want to
 control via options.  One is whether some particular feature is
-enabled in a program that will be built anway, often by including or
+enabled in a program that will be built anyway, often by including or
 not including a dependency on some other package.  The other is
 whether or not an additional program will be built as part of the
 package.  Generally, it is better to make a split package for such