gdb/

[deliverable/binutils-gdb.git] / gdb / doc / agentexpr.texi

diff --git a/gdb/doc/agentexpr.texi b/gdb/doc/agentexpr.texi
index 79985b7a0ecd0c5011d170263187b1f0584fe62c..1b893d5a7bbeb1504803d4a9f106ff51db961621 100644 (file)
--- a/gdb/doc/agentexpr.texi
+++ b/gdb/doc/agentexpr.texi
@@ -5,12 +5,19 @@
 @c @setchapternewpage off
 @c %**end of header
 
+@c This file is part of the GDB manual.
+@c
+@c Copyright (C) 2003, 2004, 2005, 2006
+@c               Free Software Foundation, Inc.
+@c
+@c See the file gdb.texinfo for copying conditions.
+
 @c Revision: $Id$
 
 @node Agent Expressions
 @appendix The GDB Agent Expression Mechanism
 
-In some applications, it is not feasable for the debugger to interrupt
+In some applications, it is not feasible for the debugger to interrupt
 the program's execution long enough for the developer to learn anything
 helpful about its behavior.  If the program's correctness depends on its
 real-time behavior, delays introduced by a debugger might cause the
@@ -214,7 +221,7 @@ their sum, as an integer.
 
 In this example, @code{add} is the name of the bytecode, and
 @code{(0x02)} is the one-byte value used to encode the bytecode, in
-hexidecimal.  The phrase ``@var{a} @var{b} @result{} @var{a+b}'' shows
+hexadecimal.  The phrase ``@var{a} @var{b} @result{} @var{a+b}'' shows
 the stack before and after the bytecode executes.  Beforehand, the stack
 must contain at least two values, @var{a} and @var{b}; since the top of
 the stack is to the right, @var{b} is on the top of the stack, and
@@ -835,5 +842,3 @@ opcode 0x30 reserved, to remain compatible with the customer who added
 it.
 
 @end table
-
-@bye