*** empty log message ***

diff --git a/gdb/PROBLEMS.async b/gdb/PROBLEMS.async
index 6b22ebb1cf3389f3266254708fe2899a17e979ae..a54d586bd2eeef0bbc7e840b2e3ec84fe564750d 100644 (file)
--- a/gdb/PROBLEMS.async
+++ b/gdb/PROBLEMS.async
@@ -1,7 +1,7 @@
-The test mi-async.exp in gdb.mi works with `runtest gdb.mi/"*.exp"' but not
+The test mi-async.exp in gdb.mi works with `runtest gdb.mi/mi-async.exp' but not
 `make check RUNTESFLAGS=mi-async.exp'.  GDB doesn't always stop after
 `start' has been issued.  I have witnessed this sometimes when running
-the excutable basics interactively with the start command.  I guess this is
+the executable basics interactively with the start command.  I guess this is
 due to spurious other events but I don't know what they are.
 
 Failures in the gdb.mi testsuite when running asynchronously