aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/remote.texi
diff options
context:
space:
mode:
authorRoland Pesch <pesch@cygnus>1993-11-09 19:07:05 +0000
committerRoland Pesch <pesch@cygnus>1993-11-09 19:07:05 +0000
commitc79890ee1a897bc3699a81323e7265893e5d9702 (patch)
tree3e1bbbc5662af873a513bb50a2148527bbcdf43d /gdb/doc/remote.texi
parent7714a8b593cc8952b65fd6917203e1e0308cc017 (diff)
downloadgdb-c79890ee1a897bc3699a81323e7265893e5d9702.zip
gdb-c79890ee1a897bc3699a81323e7265893e5d9702.tar.gz
gdb-c79890ee1a897bc3699a81323e7265893e5d9702.tar.bz2
Fixed a few regular typos (@var for @value).
Diffstat (limited to 'gdb/doc/remote.texi')
-rw-r--r--gdb/doc/remote.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi
index 3f52a69..a1a75de 100644
--- a/gdb/doc/remote.texi
+++ b/gdb/doc/remote.texi
@@ -440,9 +440,9 @@ allows you to connect your program with a remote @value{GDBN} via
because it requires essentially the same operating-system facilities
that @value{GDBN} itself does. In fact, a system that can run
@code{gdbserver} to connect to a remote @value{GDBN} could also run
-@var{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
+@value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
because it is a much smaller program than @value{GDBN} itself. It is
-also easier to port than all of @var{GDBN}, so you may be able to get
+also easier to port than all of @value{GDBN}, so you may be able to get
started more quickly on a new system by using @code{gdbserver}.
@value{GDBN} and @code{gdbserver} communicate via either a serial line