summaryrefslogtreecommitdiff
path: root/lisp/composite.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2013-11-04 23:44:14 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2013-11-04 23:44:14 -0800
commita67c4ae05909874c97f86b11dcb8ddc88b3e960c (patch)
tree24080844d67cc6e7ba3fa0f043f56612fa679edf /lisp/composite.el
parentdf5b49306e8e82e2f18ed3243700c11ca7835750 (diff)
downloademacs-a67c4ae05909874c97f86b11dcb8ddc88b3e960c.tar.gz
Spelling fixes.
Diffstat (limited to 'lisp/composite.el')
-rw-r--r--lisp/composite.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/composite.el b/lisp/composite.el
index e0585f80880..f2f4437cadb 100644
--- a/lisp/composite.el
+++ b/lisp/composite.el
@@ -630,14 +630,14 @@ All non-spacing characters have this function in
((and (= class 0)
(eq (get-char-code-property (lglyph-char glyph)
'general-category) 'Me))
- ;; Artificially layouting glyphs in an enclosing
+ ;; Artificially laying out glyphs in an enclosing
;; mark is difficult. All we can do is to adjust
;; the x-offset and width of the base glyph to
;; align it at the center of the glyph of the
;; enclosing mark hoping that the enclosing mark
;; is big enough. We also have to adjust the
;; x-offset and width of the mark ifself properly
- ;; depending on how the glyph is designed
+ ;; depending on how the glyph is designed.
;; (non-spacing or not). For instance, when we
;; have these glyphs: