* baseboards/mcore-moto-sim.exp, lib/dejagnu.exp, lib/dg.exp,

lib/dmucs.exp, lib/framework.exp, lib/remote.exp, lib/target.exp,
	runtest.exp: Fix spelling errors in comments.

ChangeLog

@@ -1,3 +1,9 @@
+2016-03-30  Ben Elliston  <bje@gnu.org>
+
+	* baseboards/mcore-moto-sim.exp, lib/dejagnu.exp, lib/dg.exp,
+	lib/dmucs.exp, lib/framework.exp, lib/remote.exp, lib/target.exp,
+	runtest.exp: Fix spelling errors in comments.
+
 2016-03-30  Ben Elliston  <bje@gnu.org>
 
 	* lib/remote.exp (remote_expect): Use perror not send_user.

baseboards/mcore-moto-sim.exp

@@ -18,9 +18,9 @@
 # Inc., 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA.
 
 # This is a HACKED version of mcore-sim.exp that is intended to
-# support running tests on Motorola's proprietry MCore simulator.
+# support running tests on Motorola's proprietary MCore simulator.
 
-# It is quite likely that thia file will need to be modified in
+# It is quite likely that this file will need to be modified in
 # order for you to use Motorola's simulator.
 
 # This is a list of toolchains that are supported on this board.

lib/dejagnu.exp

@@ -98,8 +98,8 @@ proc host_compile {compline} {
     return ${comp_output}
 }
 
-# Execute the executable file, and anaylyse the output for the
-# test state keywords.
+# Execute the executable file, and analyse the output for the test
+# state keywords.
 #    Returns:
 #	A "" (empty) string if everything worked, or an error message
 #	if there was a problem.

lib/dg.exp

@@ -115,7 +115,7 @@
 #	pattern matching.  This also gives the tool an opportunity to review
 #	the output and check for any conditions which indicate an "untested"
 #	or "unresolved" state.  An example is if a testcase is too big and
-#	fills all available ram (which can happen for 16 bit cpus).  The
+#	fills all available ram (which can happen for 16 bit CPUs).  The
 #	result is either the pruned text or
 #	"::untested|unresolved|unsupported::message"
 #	(eg: "::unsupported::memory full").
@@ -564,7 +564,7 @@ proc dg-runtest { testcases options default-extra-options } {
 # dg-trim-dirname -- rip DIR_NAME out of FILE_NAME
 #
 # Syntax: dg-trim-dirname dir_name file_name
-# We need to go through this contorsion in order to properly support
+# We need to go through this contortion in order to properly support
 # directory-names which might have embedded regexp special characters.
 #
 proc dg-trim-dirname { dir_name file_name } {

lib/dmucs.exp

@@ -17,7 +17,7 @@
 # Inc., 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA.
 
 # This file requires a slightly modified dmucs, which has been
-# modified to support mutiple architectures for toolchain
+# modified to support multiple architectures for toolchain
 # testing. DMUCS sends the CPU load to a server, which we can query
 # using the 'gethost' command to get the next available slave for a
 # remote test based on which one is the least busy. The code for this

lib/framework.exp

@@ -174,7 +174,7 @@ proc is_remote { board } {
     return 1
 }
 
-# If this is a canadian (3 way) cross. This means the tools are
+# If this is a Canadian (3 way) cross. This means the tools are
 # being built with a cross compiler for another host.
 #
 proc is3way {} {
@@ -484,7 +484,7 @@ proc setup_xfail { args } {
 #
 # A bug report ID _MUST_ be specified, and is the first argument.
 # It still must be a string without '-' so we can be sure someone
-# did not just forget it and we end-up using a taget triple as
+# did not just forget it and we end-up using a target triple as
 # bug id.
 #
 # Multiple target triplet patterns can be specified for targets

lib/remote.exp

@@ -1167,7 +1167,7 @@ proc standard_wait { dest timeout } {
     return [list $status $output]
 }
 
-# This checks the value cotained in the variable named "variable" in
+# This checks the value contained in the variable named "variable" in
 # the calling procedure for output from the status wrapper and returns
 # a non-negative value if it exists; otherwise, it returns -1. The
 # output from the wrapper is removed from the variable.

lib/target.exp

@@ -64,14 +64,14 @@ proc push_target { name } {
     push_config target $name
 }
 
-# Set the host connnection.
+# Set the host connection.
 #
 proc push_host { name } {
     pop_config host
     push_config host $name
 }
 
-# Set the build connnection.
+# Set the build connection.
 #
 proc push_build { name } {
     pop_config build

runtest.exp

@@ -668,12 +668,12 @@ if { $arg_build_triplet != "" } {
     set build_triplet $arg_build_triplet
 }
 
-# if we only specify --host, then that must be the build machne too, and we're
-# stuck using the old functionality of a simple cross test
+# If we only specify --host, then that must be the build machine too,
+# and we're stuck using the old functionality of a simple cross test.
 if {[expr { $build_triplet == ""  &&  $host_triplet != "" } ]} {
     set build_triplet $host_triplet
 }
-# if we only specify --build, then we'll use that as the host too
+# If we only specify --build, then we'll use that as the host too.
 if {[expr { $build_triplet != "" && $host_triplet == "" } ]} {
     set host_triplet $build_triplet
 }