From: Tom Tromey <tromey@redhat.com>
Date: Thu, 15 Nov 2012 21:25:43 +0000 (+0000)
Subject: 	* gdb.texinfo (Signaling): Fix typo.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=ae606bee5b0808aaf3fe1cb80cc9ae6e877d6d46;p=binutils-gdb.git

	* gdb.texinfo (Signaling): Fix typo.
---

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index dc0ca89c434..a7746819a9f 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2012-11-15  Tom Tromey  <tromey@redhat.com>
+
+	* gdb.texinfo (Signaling): Fix typo.
+
 2012-11-13  Giuseppe Montalto  <giuseppe.montalto@st.com>
 
 	* gdb.texinfo (GDB/MI Data Manipulation): Document new optional
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f45b65e21cb..945a66b227e 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -15642,7 +15642,7 @@ SIGINT} are both ways of sending an interrupt signal.
 
 Alternatively, if @var{signal} is zero, continue execution without
 giving a signal.  This is useful when your program stopped on account of
-a signal and would ordinary see the signal when resumed with the
+a signal and would ordinarily see the signal when resumed with the
 @code{continue} command; @samp{signal 0} causes it to resume without a
 signal.