From: Tom de Vries <tdevries@suse.de>
Date: Mon, 8 Dec 2025 15:38:28 +0000 (+0100)
Subject: [gdb/testsuite] Fix two typos in gdb.multi/remote-with-running-inferior.exp
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ec095064125b3a31d984bbe904897655d476d161;p=thirdparty%2Fbinutils-gdb.git

[gdb/testsuite] Fix two typos in gdb.multi/remote-with-running-inferior.exp

Fix two typos in test-case gdb.multi/remote-with-running-inferior.exp.
---

diff --git a/gdb/testsuite/gdb.multi/remote-with-running-inferior.exp b/gdb/testsuite/gdb.multi/remote-with-running-inferior.exp
index f33f60d0ea8..ffa92df66f1 100644
--- a/gdb/testsuite/gdb.multi/remote-with-running-inferior.exp
+++ b/gdb/testsuite/gdb.multi/remote-with-running-inferior.exp
@@ -124,7 +124,7 @@ proc run_test { target_non_stop non_stop } {
 	}
     }
 
-    # Allow inferior 2 to reach main.  The confirms that inferior 2 can be
+    # Allow inferior 2 to reach main.  This confirms that inferior 2 can be
     # set running again.
     gdb_test "break main inferior 2" \
 	"Breakpoint $::decimal at .*"
@@ -136,7 +136,7 @@ proc run_test { target_non_stop non_stop } {
     # Switch to inferior 1 and allow it to continue.  This is a
     # critical part of the test.  When the test was added a bug (in
     # all-stop mode) would leave inferior 1 stopped, but GDB code
-    # would think the thread was running.  As such. the thread
+    # would think the thread was running.  As such, the thread
     # couldn't be resumed again.
     gdb_test "inferior 1" "Switching to inferior 1.*"