[Emacs-diffs] trunk r116027: font-lock.el (font-lock-keywords): Fix typo in docstring

[Bastien Guerry]

------------------------------------------------------------
revno: 116027
revision-id: address@hidden
parent: address@hidden
author: Matthew Leach  <address@hidden>
committer: Bastien Guerry <address@hidden>
branch nick: trunk
timestamp: Tue 2014-01-14 21:37:28 +0100
message:
  font-lock.el (font-lock-keywords): Fix typo in docstring
  
  * font-lock.el (font-lock-keywords): Fix typo in docstring
  (bug#16307).
modified:
  lisp/ChangeLog                 changelog-20091113204419-o5vbwnq5f7feedwu-1432
  lisp/font-lock.el              fontlock.el-20091113204419-o5vbwnq5f7feedwu-603

=== modified file 'lisp/ChangeLog'
--- a/lisp/ChangeLog    2014-01-14 10:50:28 +0000
+++ b/lisp/ChangeLog    2014-01-14 20:37:28 +0000
@@ -1,3 +1,8 @@
+2014-01-14  Matthew Leach  <address@hidden>  (tiny change)
+
+       * font-lock.el (font-lock-keywords): Fix typo in docstring
+       (bug#16307).
+
 2014-01-14  Agustín Martín Domingo  <address@hidden>
 
        * ispell.el (ispell-region): Reset `in-comment' for new line

=== modified file 'lisp/font-lock.el'
--- a/lisp/font-lock.el 2014-01-01 07:43:34 +0000
+++ b/lisp/font-lock.el 2014-01-14 20:37:28 +0000
@@ -458,7 +458,7 @@
 Be careful when composing regexps for this list; a poorly written pattern can
 dramatically slow things down!
 
-A compiled keywords list starts with t.  It is produced internal
+A compiled keywords list starts with t.  It is produced internally
 by `font-lock-compile-keywords' from a user-level keywords list.
 Its second element is the user-level keywords list that was
 compiled.  The remaining elements have the same form as