* gdb.texinfo (Signaling): Fix typo.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index dc0ca89c43499e731c3941f344963035ebac9f9c..a7746819a9fd49690b10a9efc601a647f6d8399c 100644 (file)
--- 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 f45b65e21cb8e93a475003c77edb403b574dc351..945a66b227e0e95f9166a2752681d2d20a8c63de 100644 (file)
--- 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.