From 0cc37e2948c2b7adf4a1fb4c484e2183c9e30726 Mon Sep 17 00:00:00 2001
From: John Gilmore <gnu@cygnus>
Date: Sun, 21 Jun 1992 01:56:05 +0000
Subject: [PATCH] Typo.

---
 gdb/doc/gdb.texinfo | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 3e8b55a250..2efe19869c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4329,7 +4329,7 @@ On AMD 29000 family processors, registers are saved in a separate ``register
 stack''.  There is no way for GDB to determine the extent of this stack.
 Normally, GDB just assumes that the stack is ``large enough''.
 This may result in GDB referencing memory locations that don't
-exist, you can specify the ending address of the register stack with the
+exist, so you can specify the ending address of the register stack with the
 @code{set rstack_high_address} command.  The argument should be an address,
 which you will probably want to precede with 0x and specify in hexadecimal.