Make most emulation packages obsolete. [Backport]

[gnu-emacs] / doc / misc / sem-user.texi

diff --git a/doc/misc/sem-user.texi b/doc/misc/sem-user.texi
index 8604d09576360c9002aff3fdb56904af4b880922..ebd301cf5f9f920e30aa123ee736eeae79261562 100644 (file)
--- a/doc/misc/sem-user.texi
+++ b/doc/misc/sem-user.texi
@@ -416,11 +416,11 @@ Customize the system include path for the current major mode (or
 @var{mode}).
 @end deffn
 
-@defun semanticdb-implied-include-tags
+@defvar semanticdb-implied-include-tags
 Include tags implied for all files of a given mode.  You can set this
 variable with @code{defvar-mode-local} for a particular mode so that
 any symbols that exist for all files for that mode are included.
-@end defun
+@end defvar
 
 @c @xref{Search Optimization}, for more information on include paths.
 
@@ -483,9 +483,9 @@ for them once, which will be used over and over for tools such as
 summary-mode, or the analyzer.
 
 @deffn Command semanticdb-create-ebrowse-database dir
-Create an @var{ebrowse} database for directory @var{dir}.
-The database file is stored in ~/.semanticdb, or whichever directory
-is specified by @code{semanticdb-default-system-save-directory}.
+Create an Ebrowse database for directory @var{dir}.  The database file
+is stored in ~/.semanticdb, or whichever directory is specified by
+@code{semanticdb-default-system-save-directory}.
 @end deffn
 
 @node Idle Scheduler
@@ -903,12 +903,12 @@ at a given buffer position.  The return value is an EIEIO object
 describing the context at @var{pos} (@pxref{Top,,,eieio,EIEIO
 manual}).
 
-When called interactively, this displays a @samp{*Semantic Context
+When called interactively, this displays a @file{*Semantic Context
 Analysis*} buffer containing a summary of the context at point.
 @end deffn
 
 @noindent
-The Prefix section of the @samp{*Semantic Context Analysis*} buffer
+The Prefix section of the @file{*Semantic Context Analysis*} buffer
 lists the tags based on the text at point.  If it shows only a simple
 string, the Semantic was unable to identify what the data type was.
 
@@ -983,7 +983,7 @@ If your symbol should be in the scope, but you cannot find it, then
 you may have found a language support bug in the local-variable
 parser, or using statement parser.
 
-Calling @kbd{M-x bovinte} should force a reset on the scope in case
+Calling @kbd{M-x bovinate} should force a reset on the scope in case
 there is merely some bad state.
 
 @example
@@ -1014,7 +1014,7 @@ fully qualified names.  You can examine the typecache with
 @kbd{M-x semanticdb-typecache-dump}.
 
 If your data types are not in the typecache, there may be some parsing
-error or other bug.  Calling @kbd{M-x bovinte} should force a reset on
+error or other bug.  Calling @kbd{M-x bovinate} should force a reset on
 the typecache in case there is merely some bad state.
 
 @example
@@ -1303,7 +1303,7 @@ You can create new types of decorations using the following function:
 Define a new decoration style with @var{name}.
 @var{doc} is a documentation string describing the decoration style @var{name}.
 It is appended to auto-generated doc strings.
-An Optional list of @var{flags} can also be specified.  Flags are:
+An optional list of @var{flags} can also be specified.  Flags are:
   @code{:enabled} <value>  - specify the default enabled value for @var{name}.