From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 2 Apr 2022 10:20:56 +0000 (+0300)
Subject: ; * lisp/font-lock.el (font-lock-keywords): Doc fix.
X-Git-Tag: emacs-28.1~3
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=9b5e9715ea64f971e215e91898e3ef49b159cdbe;p=emacs.git

; * lisp/font-lock.el (font-lock-keywords): Doc fix.
---

diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 7d264cf9824..c9c390840ff 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -349,7 +349,7 @@ This can be an \"!\" or the \"n\" in \"ifndef\".")
 ;; Fontification variables:
 
 (defvar font-lock-keywords nil
-  "A list of the keywords to highlight.
+  "A list of keywords and corresponding font-lock highlighting rules.
 There are two kinds of values: user-level, and compiled.
 
 A user-level keywords list is what a major mode or the user would
@@ -374,10 +374,10 @@ point, and set `match-data' appropriately if it succeeds; like
 `re-search-forward' would).  MATCHER regexps can be generated via
 the function `regexp-opt'.
 
-FORM is an expression, whose value should be a keyword element,
-evaluated when the keyword is (first) used in a buffer.  This
-feature can be used to provide a keyword that can only be
-generated when Font Lock mode is actually turned on.
+FORM is an expression, whose value should be a keyword element
+of one of the above forms, evaluated when the keyword is (first)
+used in a buffer.  This feature can be used to provide a keyword
+that can only be generated when Font Lock mode is actually turned on.
 
 HIGHLIGHT should be either MATCH-HIGHLIGHT or MATCH-ANCHORED.