summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorGerd Moellmann <gerd@gnu.org>2001-02-23 12:58:02 +0000
committerGerd Moellmann <gerd@gnu.org>2001-02-23 12:58:02 +0000
commitb66309475edb50736dea9faf3cbd1c1a7501e820 (patch)
treef20b3779810245c72810dc70aa4bdeecfd0f8f59 /man
parent6b1f581436f15ac94ac050161b67e1fae2815975 (diff)
downloademacs-b66309475edb50736dea9faf3cbd1c1a7501e820.tar.gz
(Expert): Remove doubled `in'.
Diffstat (limited to 'man')
-rw-r--r--man/info.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/info.texi b/man/info.texi
index 9cb331c4488..bed35bbd601 100644
--- a/man/info.texi
+++ b/man/info.texi
@@ -688,7 +688,7 @@ switches to the next node if and when that is necessary. You type
To search for the same string again, just @kbd{s} followed by @key{RET}
will do. The file's nodes are scanned in the order they are in in the
file, which has no necessary relationship to the order that they may be
-in in the tree structure of menus and @samp{next} pointers. But
+in the tree structure of menus and @samp{next} pointers. But
normally the two orders are not very different. In any case, you can
always do a @kbd{b} to find out what node you have reached, if the
header is not visible (this can happen, because @kbd{s} puts your cursor