[gdb/testsuite] Fix typos in gdb.threads/infcall-from-bp-cond-simple.exp

Fix two typos in gdb.threads/infcall-from-bp-cond-simple.exp.

diff --git a/gdb/testsuite/gdb.threads/infcall-from-bp-cond-simple.exp b/gdb/testsuite/gdb.threads/infcall-from-bp-cond-simple.exp
index c9508c9d67ea8a4db57a5e606978de8a04af74b1..feec37bd298df5f540cf1af6cccd7a88c8c131f9 100644 (file)
--- a/gdb/testsuite/gdb.threads/infcall-from-bp-cond-simple.exp
+++ b/gdb/testsuite/gdb.threads/infcall-from-bp-cond-simple.exp
@@ -79,7 +79,7 @@ proc run_condition_test { message n_expected_hits condition \
        gdb_breakpoint \
            "${::srcfile}:${::cond_bp_line} if ((++\$n_cond_eval) && (${condition}))"
 
-       # And a breakpoint that we hit when the test is over, this one is
+       # Add a breakpoint that we hit when the test is over, this one is
        # not conditional.  Only the main thread gets here once all the
        # other threads have finished.
        gdb_breakpoint "${::srcfile}:${::stop_bp_line}"
@@ -114,7 +114,7 @@ proc run_condition_test { message n_expected_hits condition \
 # includes an inferior call), it is still possible to kill the running
 # inferior, and then restart the inferior.
 #
-# At once point doing this would result in GDB giving an assertion error.
+# At one point doing this would result in GDB giving an assertion error.
 proc_with_prefix run_kill_and_restart_test { target_async target_non_stop } {
     # This test relies on the 'start' command, which is not possible with
     # the plain 'remote' target.