Fix misspellings of "testcase" and "testsuite"

[Matt Kraai <kraai at alumni dot cmu dot edu>]

Howdy,

The following patch fixes some misspellings of "testcase" and
"testsuite" in contribute.html.

Committed as obvious.

-- 
Matt

	* htdocs/contribute.html: Fix misspellings of "testcase" and
	"testsuite".

Index: htdocs/contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.53
diff -3 -c -p -r1.53 contribute.html
*** htdocs/contribute.html	1 Aug 2003 16:22:53 -0000	1.53
--- htdocs/contribute.html	5 Aug 2003 00:51:18 -0000
*************** and targets that don't.</p>
*** 83,89 ****
  <p>You will of course have tested that your change does what you
  expected it to do: fix a bug, improve an optimization, add a new
  feature.  If the test framework permits, you should automate these
! tests and add them to GCC's test suite.  You must also perform
  regression tests to ensure that your patch does not break anything
  else.</p>
  
--- 83,89 ----
  <p>You will of course have tested that your change does what you
  expected it to do: fix a bug, improve an optimization, add a new
  feature.  If the test framework permits, you should automate these
! tests and add them to GCC's testsuite.  You must also perform
  regression tests to ensure that your patch does not break anything
  else.</p>
  
*************** else.</p>
*** 91,97 ****
  C front end, you must perform a complete build of GCC and the runtime
  libraries included with it, on at least one target.  You must
  bootstrap all languages, not just C.  You must also run all of the
! test suites included with GCC and its runtime libraries.  For a normal
  native configuration, running <code>make bootstrap</code> followed by
  <code>make -k check</code> from the top level of the GCC tree
  (<strong>not</strong> the <code>gcc</code> subdirectory) will
--- 91,97 ----
  C front end, you must perform a complete build of GCC and the runtime
  libraries included with it, on at least one target.  You must
  bootstrap all languages, not just C.  You must also run all of the
! testsuites included with GCC and its runtime libraries.  For a normal
  native configuration, running <code>make bootstrap</code> followed by
  <code>make -k check</code> from the top level of the GCC tree
  (<strong>not</strong> the <code>gcc</code> subdirectory) will
*************** them.</p>
*** 108,114 ****
  
  <p>Since the Ada front end is written in Ada, if you change it you
  must perform a complete bootstrap; however, running other language
! test suites is not necessary.</p>
  
  
  <h2><a name="docchanges">Documentation Changes</a></h2>
--- 108,114 ----
  
  <p>Since the Ada front end is written in Ada, if you change it you
  must perform a complete bootstrap; however, running other language
! testsuites is not necessary.</p>
  
  
  <h2><a name="docchanges">Documentation Changes</a></h2>
*************** file" mode of the validator.</p>
*** 143,149 ****
  submit; it's not good enough to test an earlier variant.  The tree
  where you perform this test should not have any other changes applied
  to it, because otherwise you cannot be sure that your patch will work
! correctly on its own.  Include all your new test cases in your
  testsuite run.</p>
  
  
--- 143,149 ----
  submit; it's not good enough to test an earlier variant.  The tree
  where you perform this test should not have any other changes applied
  to it, because otherwise you cannot be sure that your patch will work
! correctly on its own.  Include all your new testcases in your
  testsuite run.</p>