summaryrefslogtreecommitdiff
path: root/lisp/frameset.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2013-08-15 22:15:51 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2013-08-15 22:15:51 -0700
commit526e5233cc0e2375798bdc79329a893302fdfb4b (patch)
treea4c1d95440225335cd6864a23e6fa1f6c5d6b28b /lisp/frameset.el
parentc8068af56770f8b0be93218e76dd17ea508f3365 (diff)
downloademacs-526e5233cc0e2375798bdc79329a893302fdfb4b.tar.gz
Spelling fixes.
Diffstat (limited to 'lisp/frameset.el')
-rw-r--r--lisp/frameset.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/frameset.el b/lisp/frameset.el
index 7cdab7e3fcc..53ab0a5f081 100644
--- a/lisp/frameset.el
+++ b/lisp/frameset.el
@@ -182,7 +182,7 @@ Properties can be set with
;; Let's say that Emacs' frame parameters were never designed as a tool to
;; precisely record (or restore) a frame's state. They grew organically,
;; and their uses and behaviors reflect their history. In using them to
-;; implement framesets, the unwary implementor, or the prospective package
+;; implement framesets, the unwary implementer, or the prospective package
;; writer willing to use framesets in their code, might fall victim of some
;; unexpected... oddities.
;;