; Fix bad references to other manuals

* doc/misc/bovine.texi (top, Optional Lambda Expression)
(Starting Rules, Bovine Grammar Rules, How Lexical Tokens Match):
* doc/misc/eudc.texi (Overview, Creating BBDB Records)
(Inline Query Expansion):
* doc/misc/dbus.texi (Top):
* doc/misc/efaq.texi (Top):
* doc/misc/wisent.texi (Wisent Semantic, Wisent Lex): Fix
cross-references to other manuals.  Remove redundant pointers from
Top node.  (Bug#72761)

(cherry picked from commit 7319f5e078)

doc/misc/bovine.texi

@@ -83,8 +83,7 @@ wisent}.
 
 Bovine @acronym{LL} grammars are stored in files with a @file{.by}
 extension.  When compiled, the contents is converted into a file of
-the form @file{NAME-by.el}.  This, in turn is byte compiled.
-@xref{top,, Grammar Framework Manual, grammar-fw}.
+the form @file{NAME-by.el}.
 
 @ifnottex
 @insertcopying
@@ -105,8 +104,7 @@ the form @file{NAME-by.el}.  This, in turn is byte compiled.
 In Bison, one and only one nonterminal is designated as the ``start''
 symbol.  In @semantic{}, one or more nonterminals can be designated as
 the ``start'' symbol.  They are declared following the @code{%start}
-keyword separated by spaces.  @xref{start Decl,, Grammar Framework
-Manual, grammar-fw}.
+keyword separated by spaces.
 
 If no @code{%start} keyword is used in a grammar, then the very first
 is used.  Internally the first start nonterminal is targeted by the
@@ -116,8 +114,7 @@ parser harness.
 To find locally defined variables, the local context handler needs to
 parse the body of functional code.  The @code{scopestart} declaration
 specifies the name of a nonterminal used as the goal to parse a local
-context, @pxref{scopestart Decl,, Grammar Framework Manual,
-grammar-fw}.  Internally the
+context.  Internally the
 scopestart nonterminal is targeted by the reserved symbol
 @code{bovine-inner-scope}, so it can be found by the parser harness.
 
@@ -126,7 +123,7 @@ scopestart nonterminal is targeted by the reserved symbol
 
 The rules are what allow the compiler to create tags from a language
 file.  Once the setup is done in the prologue, you can start writing
-rules.  @xref{Grammar Rules,, Grammar Framework Manual, grammar-fw}.
+rules.
 
 @example
 @var{result} : @var{components1} @var{optional-semantic-action1})
@@ -148,8 +145,7 @@ A particular @var{result} written into your grammar becomes
 the parser's goal.  It is designated by a @code{%start} statement
 (@pxref{Starting Rules}).  The value returned by the associated
 @var{optional-semantic-action} is the parser's result.  It should be
-a tree of @semantic{} @dfn{tags}, @pxref{Semantic Tags,, Semantic
-Application Development, semantic-appdev}.
+a tree of @semantic{} @dfn{tags}.
 
 @var{components} is made up of symbols.  A symbol such as @code{FOO}
 means that a syntactic token of class @code{FOO} must be matched.
@@ -172,8 +168,7 @@ For instance:
 @end example
 
 Means that @code{FOO} is a reserved language keyword, matched as such
-by looking up into a keyword table, @pxref{keyword Decl,, Grammar
-Framework Manual, grammar-fw}.  This is because @code{"foo"} will be
+by looking up into a keyword table.  This is because @code{"foo"} will be
 converted to
 @code{FOO} in the lexical analysis stage.  Thus the symbol @code{FOO}
 won't be available any other way.
@@ -386,8 +381,6 @@ Is an optional set of labeled values such as @code{:constant-flag t :parent
 Create a tag with @var{name} of respectively the class
 @code{variable}, @code{function}, @code{type}, @code{include},
 @code{package}, and @code{code}.
-See @ref{Creating Tags,, Semantic Application Development,
-semantic-appdev}, for the lisp functions these translate into.
 @end table
 
 If the symbol @code{%quotemode backquote} is specified, then use

doc/misc/calc.texi

@@ -142,7 +142,7 @@ modify this GNU manual.''
 
 @c [begin]
 @ifnottex
-@node Top, Getting Started, (dir), (dir)
+@node Top
 @top The GNU Emacs Calculator
 
 @noindent

doc/misc/dbus.texi

@@ -41,7 +41,7 @@ modify this GNU manual.''
 @contents
 
 
-@node Top, Overview, (dir), (dir)
+@node Top
 @top D-Bus integration in Emacs
 
 This manual documents an API for usage of D-Bus in Emacs.  D-Bus is a

doc/misc/efaq.texi

@@ -48,7 +48,7 @@ itself allows free copying and redistribution.
 
 @contents
 
-@node Top, FAQ notation, (dir), (dir)
+@node Top
 @top The GNU Emacs FAQ
 
 This is the GNU Emacs FAQ.

doc/misc/eudc.texi

@@ -107,7 +107,7 @@ inline query
 Fast minibuffer queries for email addresses and phone numbers
 @item
 Interface to BBDB to let you insert server records into your own BBDB database
-(@pxref{Top,,BBDB,bbdb,BBDB Manual})
+(@pxref{BBDB,,BBDB,bbdb,BBDB Manual})
 @end itemize
 
 @menu
@@ -986,8 +986,8 @@ In addition to providing a dedicated EUDC function for binding to a
 key shortcut (@pxref{Inline Query Expansion}), EUDC also provides a
 function to contribute search results to the Emacs in-buffer
 completion system available via the function
-@code{completion-at-point} (@pxref{Identifier
-Inquiries,,,maintaining}) in @code{message-mode} buffers
+@code{completion-at-point} (@pxref{List Identifiers,,,emacs, The GNU
+Emacs Manual}) in @code{message-mode} buffers
 (@pxref{Top,Message,, message, Message}).  When using this mechanism,
 queries are made in the multi-server query mode of operation
 (@pxref{Multi-server Queries}).
@@ -1133,7 +1133,7 @@ that all available servers should be tried.
 @findex eudc-insert-record-at-point-into-bbdb
 @findex eudc-try-bbdb-insert
 With EUDC, you can automatically create BBDB records
-(@pxref{Top,,BBDB,bbdb,BBDB Manual}) from records you get from a
+(@pxref{BBDB,,BBDB,bbdb,BBDB Manual}) from records you get from a
 directory server.  You do this by moving point to the appropriate
 record in a query result display buffer and invoking the command
 @kbd{M-x eudc-insert-record-at-point-into-bbdb} with the

doc/misc/wisent.texi

@@ -1576,9 +1576,6 @@ To use the Wisent parser with @semantic{} you have to define
 your grammar in @dfn{WY} form, a grammar format very close
 to the one used by Bison.
 
-Please see @ref{top, Semantic Grammar Framework Manual,, grammar-fw},
-for more information on @semantic{} grammars.
-
 @menu
 * Grammar styles::
 * Wisent Lex::
@@ -1963,8 +1960,7 @@ See implementation of the function @code{wisent-skip-token} in
 
 @findex semantic-lex
 The lexical analysis step of @semantic{} is performed by the general
-function @code{semantic-lex}.  For more information, see @ref{Writing
-Lexers, Semantic Language Development,,semantic-langdev}.
+function @code{semantic-lex}.
 
 @code{semantic-lex} produces lexical tokens of the form: