diff options
Diffstat (limited to 'lisp/progmodes')
| -rw-r--r-- | lisp/progmodes/idlwave.el | 2 | ||||
| -rw-r--r-- | lisp/progmodes/js.el | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/lisp/progmodes/idlwave.el b/lisp/progmodes/idlwave.el index cd2fc7c7079..395c51d5421 100644 --- a/lisp/progmodes/idlwave.el +++ b/lisp/progmodes/idlwave.el @@ -133,7 +133,7 @@ ;; limited to comments only and occurs only when a comment ;; paragraph is filled via `idlwave-fill-paragraph'. ;; -;; Muti-statement lines (using "&") on block begin and end lines can +;; Multi-statement lines (using "&") on block begin and end lines can ;; ruin the formatting. For example, multiple end statements on a ;; line: endif & endif. Using "&" outside of block begin/end lines ;; should be okay. diff --git a/lisp/progmodes/js.el b/lisp/progmodes/js.el index 8ec14cf7ad1..a776ff91f9b 100644 --- a/lisp/progmodes/js.el +++ b/lisp/progmodes/js.el @@ -1928,7 +1928,7 @@ This performs fontification according to `js--class-styles'." ;; identified as such), then the `syntax-propertize' region won’t be ;; extended backwards to the start of the JSXOpeningElement: ;; -;; <div ← This line wasn’t JSX when last edited. +;; <div ← This line wasn't JSX when last edited. ;; attr=""> ← Despite completing the JSX, the next ;; ^ `syntax-propertize' region wouldn’t magically ;; extend back a few lines. @@ -2090,7 +2090,7 @@ JSXElement or a JSXOpeningElement/JSXClosingElement pair." ;; JSXOpeningElement has been found, so keep ;; looking backwards for an enclosing one). (or (not close-tag-pos) (<= start close-tag-pos))))))))) - ;; Don’t return the last tag pos, as it wasn’t enclosing. + ;; Don't return the last tag pos, as it wasn't enclosing. (setq tag-beg nil close-tag-pos nil)) (and tag-beg (list tag-beg-pos tag-end-pos close-tag-pos)))) |