dejagnu.texi minor typos

[David B Anderson <davea at quasar dot engr dot sgi dot com>]

The following is a suggested patch for src/dejagnu/doc/dejagnu.texi  .

Spelling corrections only.

I did not change the British-spelling 'behaviour' though it takes more
space on the page than 'behavior' :-)

I don't really know who this should go to, so sending it
to the gdb list in hopes that it will  be seen by the right person.

Suggestions as to what else I should do with this would
be welcome.


Index: dejagnu.texi
===================================================================
RCS file: /cvs/src/src/dejagnu/doc/dejagnu.texi,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 dejagnu.texi
--- dejagnu.texi        1999/11/09 01:28:42     1.1.1.1
+++ dejagnu.texi        2000/10/04 16:01:14
@@ -1156,7 +1156,7 @@ procedure, which is discussed elsewhere.
 @c FIXME: write that section and put an xref here
 
 This array can also hold information for a remote host, which is used
-when testing a candain cross. In this case, the only thing different is
+when testing a canadian cross. In this case, the only thing different is
 the index is just @code{host}. Here's the settings I use to run tests
 on my NT machine while running DejaGnu on a Unix machine. (in this case
 a Linux box)
@@ -1290,7 +1290,7 @@ and test a cross compiler on a machine o
 hosted on.
 
 Here we have the config settings for our California office. Note that
-all config values are site dependant. Here we have two sets of values
+all config values are site dependent. Here we have two sets of values
 that we use for testing m68k-aout cross compilers. As both of these
 target boards has a different debugging protocol, we test on both of
 them in sequence.
@@ -1422,7 +1422,7 @@ variable in the top section, then just p
 second section. Usually the values defined in this config file are
 related to the configuration of the test run. This is the ideal place to
 set the variables @code{host_triplet}, @code{build_triplet},
-@code{target_triplet}. All other variables are tool dependant. ie for
+@code{target_triplet}. All other variables are tool dependent. ie for
 testing a compiler, the value for @var{CC} might be set to a freshly
 built binary, as opposed to one in the user's path.
 
@@ -1881,7 +1881,7 @@ results.
 @cindex conditional expected failure
 
 This procedure adds a condition xfail, based on compiler options used to
-create a test case executable. If an include options is found in the
+create a test case executable. If an includes option is found in the
 compiler flags, and it's the right architecture, it'll trigger an
 XFAIL. Otherwise it'll produce an ordinary FAIL. You can also specify
 flags to exclude. This makes a result be a FAIL, even if the included
@@ -1938,7 +1938,7 @@ set compiler_conditional_xfail_data @{@ 
   What this does is it matches only for these two targets if "-Wall -v" or 
 "-O3" is set, but neither "-O1" or "-Map" is set.
 
-  For a set to match, the options specified are searched for independantly of
+  For a set to match, the options specified are searched for independently of
 each other, so a "-Wall -v" matches either "-Wall -v" or "-v -Wall". A space
 seperates the options in the string. Glob-style regular expressions are also
 permitted.


Regards,
David B. Anderson davea@sgi.com danderson@acm.org http://reality.sgi.com/davea/