summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp
diff options
context:
space:
mode:
authorJim Blandy <jimb@redhat.com>1993-03-16 18:36:27 +0000
committerJim Blandy <jimb@redhat.com>1993-03-16 18:36:27 +0000
commit2e94b813469ad3d55695c3fda31026bbdb899db5 (patch)
treec6f3a0a950b101e63c904d3e7b5b33c57ca6ce6c /lisp/emacs-lisp
parent1db01b1ab5e321cce8de06006766ce1b8b7a17e7 (diff)
downloademacs-2e94b813469ad3d55695c3fda31026bbdb899db5.tar.gz
emacs-2e94b813469ad3d55695c3fda31026bbdb899db5.tar.bz2
emacs-2e94b813469ad3d55695c3fda31026bbdb899db5.zip
Doc fix.
Diffstat (limited to 'lisp/emacs-lisp')
-rw-r--r--lisp/emacs-lisp/bytecomp.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index eb2b1a22c31..bab4e9de04d 100644
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -1258,7 +1258,7 @@ With argument, insert value in current buffer after the form."
;; (emacs-lisp-mode)
(setq case-fold-search nil)
- ;; This is a kludge. Some operating systems (OS/2) need to
+ ;; This is a kludge. Some operating systems (OS/2, DOS) need to
;; write files containing binary information specially.
;; Under most circumstances, such files will be in binary
;; overwrite mode, so those OS's use that flag to guess how