summaryrefslogtreecommitdiff
path: root/lisp/font-lock.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
commit40ba43b4b71df1d51954bdad071e74243c4aea7c (patch)
treee4cb03937e72463278264e9684481d68ece4698c /lisp/font-lock.el
parent24901d610c9ff524e7e7c132dca1cd4312368db0 (diff)
downloademacs-40ba43b4b71df1d51954bdad071e74243c4aea7c.tar.gz
emacs-40ba43b4b71df1d51954bdad071e74243c4aea7c.tar.bz2
emacs-40ba43b4b71df1d51954bdad071e74243c4aea7c.zip
Spelling fixes.
Diffstat (limited to 'lisp/font-lock.el')
-rw-r--r--lisp/font-lock.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index d410b8eb51a..c319974fb41 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -981,7 +981,7 @@ The value of this variable is used when Font Lock mode is turned on."
;; rules one way and C code another. Neat!
;;
;; A further reason to use the fontification indirection feature is when the
-;; default syntactual fontification, or the default fontification in general,
+;; default syntactic fontification, or the default fontification in general,
;; is not flexible enough for a particular major mode. For example, perhaps
;; comments are just too hairy for `font-lock-fontify-syntactically-region' to
;; cope with. You need to write your own version of that function, e.g.,