summaryrefslogtreecommitdiff
path: root/lisp/progmodes/cc-engine.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2019-11-11 10:30:13 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2019-11-11 10:32:53 -0800
commit6b4a97c1c78f39ce890d100acceceb652d14e20d (patch)
tree9d9f8347a952226adcd73680ed89c5679d6e5326 /lisp/progmodes/cc-engine.el
parent269796288a43520a1dcc481337af472d086faaa4 (diff)
downloademacs-6b4a97c1c78f39ce890d100acceceb652d14e20d.tar.gz
Fix some quoting glitches in doc strings
Diffstat (limited to 'lisp/progmodes/cc-engine.el')
-rw-r--r--lisp/progmodes/cc-engine.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/progmodes/cc-engine.el b/lisp/progmodes/cc-engine.el
index cceb58c290a..15b23bb2e6a 100644
--- a/lisp/progmodes/cc-engine.el
+++ b/lisp/progmodes/cc-engine.el
@@ -5059,10 +5059,10 @@ that region is taken as syntactically significant text.
NOERROR, in addition to the values nil, t, and <anything else>
used in `re-search-forward' can also take the values
-'before-literal and 'after-literal. In these cases, when BOUND
+`before-literal' and `after-literal'. In these cases, when BOUND
is also given and is inside a literal, and a search fails, point
will be left, respectively before or after the literal. Be aware
-that with 'after-literal, if a string or comment is unclosed at
+that with `after-literal', if a string or comment is unclosed at
the end of the buffer, point may be left there, even though it is
inside a literal there.