[wwwdocs] Consistently use "testsuite"

Index: contributewhy.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contributewhy.html,v
retrieving revision 1.8
diff -u -r1.8 contributewhy.html
--- contributewhy.html	27 Jun 2014 11:48:45 -0000	1.8
+++ contributewhy.html	3 Feb 2017 07:39:07 -0000
@@ -91,7 +91,7 @@ 
 port in the official GCC sources maintained by the GNU Project.  The
 wider exposure in the GCC developer and tester community will help
 keep your port up to date with the current sources.  You may even find
-that volunteers will run the ever-growing test suite on your port and
+that volunteers will run the ever-growing testsuite on your port and
 fix problems during the development cycle -- sometimes without your
 intervention.</p>
 
Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.223
diff -u -r1.223 faq.html
--- faq.html	29 Dec 2016 21:07:36 -0000	1.223
+++ faq.html	3 Feb 2017 07:39:07 -0000
@@ -42,7 +42,7 @@ 
   <ol>
     <li><a href="#testoptions">How do I pass flags like
         <code>-fnew-abi</code> to the testsuite?</a></li>
-    <li><a href="#multipletests">How can I run the test suite with multiple options?</a></li>
+    <li><a href="#multipletests">How can I run the testsuite with multiple options?</a></li>
   </ol></li>
 
   <li><a href="#misc">Miscellaneous</a>
@@ -297,7 +297,7 @@ 
 </pre>
 
 <hr />
-<h2><a name="multipletests"> How can I run the test suite with multiple options? </a></h2>
+<h2><a name="multipletests"> How can I run the testsuite with multiple options? </a></h2>
 
 <p>If you invoke <code>runtest</code> directly, you can use the
 <code>--target_board</code> option, e.g:</p>
Index: readings.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.255
diff -u -r1.255 readings.html
--- readings.html	22 Jan 2017 20:20:57 -0000	1.255
+++ readings.html	3 Feb 2017 07:39:07 -0000
@@ -442,7 +433,7 @@ 
         <a href="http://www.itl.nist.gov/div897/ctg/fortran_form.htm">FORTRAN
         77 test suite</a> by the NIST Information Technology Laboratory
         (<a href="http://www.itl.nist.gov/div897/ctg/software.htm">license</a>)
-        The test suite contains legal and operational Fortran 77 code.
+        contains legal and operational Fortran 77 code.
       </li>
       <li>
         IDRIS
@@ -465,7 +456,7 @@ 
         Arjen Markus (source provided).
       </li>
       <li>
-        <a href="http://gdbf95.sourceforge.net/">gdbf95</a> test suite.
+        <a href="http://gdbf95.sourceforge.net/">gdbf95</a> testsuite.
       </li>
       <li>
         Tests of run-time checking capabilities
@@ -487,7 +478,7 @@ 
         <li>
           <a href="http://www.ifremer.fr/ditigo/molagnon/fortran90/engfaq.html">
           Michel Olagnon's Fortran 90 List</a> contains a "Tests and
-          Benchmarks" section mentioning commercial test suites.
+          Benchmarks" section mentioning commercial testsuites.
         </li>
         <li>
           <a href="http://www.personal.psu.edu/faculty/h/d/hdk/fortran.html">Herman
@@ -498,7 +489,7 @@ 
           <cite>Complying with Fortran 90, How does the current crop of
           Fortran 90 compilers measure up to the standard?</cite>, Steven
           Baker, Dr Dobb's, January 1995. It described the results of several
-          commercial test suites.
+          commercial testsuites.
         </li>
       </ul>
    </li>