# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 886745430 0
# Node ID 26c5d61bc3fd29fd29d549ef2070e7c10d528e52
# Parent  ffbaaba0bf769fb3f440a563644a86942ac5e508
(font-lock-keywords): Doc fix.

diff -r ffbaaba0bf76 -r 26c5d61bc3fd lisp/font-lock.el
--- a/lisp/font-lock.el	Thu Feb 05 03:31:41 1998 +0000
+++ b/lisp/font-lock.el	Fri Feb 06 06:10:30 1998 +0000
@@ -295,7 +295,7 @@
 
 (defvar font-lock-keywords nil
   "A list of the keywords to highlight.
-Each element should be of the form:
+Each element should have one of these forms:
 
  MATCHER
  (MATCHER . MATCH)
@@ -318,7 +318,7 @@
 
  (MATCH FACENAME OVERRIDE LAXMATCH)
 
-Where MATCHER can be either the regexp to search for, or the function name to
+where MATCHER can be either the regexp to search for, or the function name to
 call to make the search (called with one argument, the limit of the search) and
 return non-nil if it succeeds (and set `match-data' appropriately).
 MATCHER regexps can be generated via the function `regexp-opt'.  MATCH is the
@@ -351,7 +351,7 @@
 
  (MATCHER PRE-MATCH-FORM POST-MATCH-FORM MATCH-HIGHLIGHT ...)
 
-Where MATCHER is as for MATCH-HIGHLIGHT with one exception; see below.
+where MATCHER is as for MATCH-HIGHLIGHT with one exception; see below.
 PRE-MATCH-FORM and POST-MATCH-FORM are evaluated before the first, and after
 the last, instance MATCH-ANCHORED's MATCHER is used.  Therefore they can be
 used to initialise before, and cleanup after, MATCHER is used.  Typically,