Source

semantic / semantic.texi

Diff from to

semantic.texi

 
 The lexer uses the major-mode's syntax table for conversion.  As long as
 that is set up correctly (along with the important
-@code{comment-start-skip} variable) te lexer should already work for you
+@code{comment-start-skip} variable) the lexer should already work for your
 language.
 
 There are three ways to extend the flexer.
 
 @defvar semantic-flex-extensions
-For a given language buffer, this is an associatoin list.  The key is a
+For a given language buffer, this is an association list.  The key is a
 regular expression used to match text in the buffer.  The data element
 is a function which will be called when that text is encountered.
 
 @deffn Command bovinate-debug
 Start parsing the current buffer in debug mode.  Uses the definition set
 with @code{semantic-bovinate-debug-set-table}.  Use space to move to the
-next definition.  It will hightlight the current semantic token in the
+next definition.  It will highlight the current semantic token in the
 source buffer, and the current match symbol.
 
 @key{C-g} halts the debugger.
 @end defun
 
 @defun semantic-recursive-find-nonterminal-by-name name buffer
-Recursivly find the first occurance of @var{NAME}.
+Recursively find the first occurrence of @var{NAME}.
 Start search with @var{BUFFER}.  Recurse through all dependencies till found.
 The return item is of the form (@var{BUFFER} @var{TOKEN}) where @var{BUFFER} is the buffer
 in which @var{TOKEN} (the token found to match @var{NAME}) was found.
 @defun semantic-find-documentation buffer token
 Find documentation from @var{BUFFER}/@var{TOKEN} and return it as a clean string.
 @var{TOKEN} might have @var{DOCUMENTATION} set in it already.  If not, there may be
-some documentation in a comment preceeding TOKEN's definition which we
+some documentation in a comment preceding TOKEN's definition which we
 cal look for.  When appropriate, this can be overridden by a language specific
 enhancement.
 @end defun