fix grammar oddity in the manual

This patch fixes a buglet in the manual.
It's wrong to say that a method is defined "as" a subclass.
Instead it should say that a method is defined "in" a subclass.

I'm checking this in under the obvious rule.

2013-11-14  Tom Tromey  <tromey@redhat.com>

	* gdb.texinfo (Breakpoints In Python): Replace "as" with "in".

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 6ffdefa99e1a4fcd1a70ac8a18deeb7bab02eb97..0dc75cd6948be4ca1074fcb514e0c3f1939d1030 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2013-11-14  Tom Tromey  <tromey@redhat.com>
+
+       * gdb.texinfo (Breakpoints In Python): Replace "as" with "in".
+
 2013-11-14  Joel Brobecker  <brobecker@adacore.com>
 
        * gdb.texinfo (Show): Add xref anchor for "show language" command.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index a164785720f8050d238d06e0bce18f3d0b7add54..c2dfa170ff516c52223b2d982796da531c649501 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27184,7 +27184,7 @@ is assumed to be a @code{gdb.WP_WRITE} class.
 @defun Breakpoint.stop (self)
 The @code{gdb.Breakpoint} class can be sub-classed and, in
 particular, you may choose to implement the @code{stop} method.
-If this method is defined as a sub-class of @code{gdb.Breakpoint},
+If this method is defined in a sub-class of @code{gdb.Breakpoint},
 it will be called when the inferior reaches any location of a
 breakpoint which instantiates that sub-class.  If the method returns
 @code{True}, the inferior will be stopped at the location of the