summaryrefslogtreecommitdiff
path: root/lisp/gnus/nntp.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
commit40ba43b4b71df1d51954bdad071e74243c4aea7c (patch)
treee4cb03937e72463278264e9684481d68ece4698c /lisp/gnus/nntp.el
parent24901d610c9ff524e7e7c132dca1cd4312368db0 (diff)
downloademacs-40ba43b4b71df1d51954bdad071e74243c4aea7c.tar.gz
Spelling fixes.
Diffstat (limited to 'lisp/gnus/nntp.el')
-rw-r--r--lisp/gnus/nntp.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/gnus/nntp.el b/lisp/gnus/nntp.el
index 325aa67f80d..9816c208fab 100644
--- a/lisp/gnus/nntp.el
+++ b/lisp/gnus/nntp.el
@@ -1681,7 +1681,7 @@ password contained in '~/.nntp-authinfo'."
;; for the first available article. Obviously, a client can
;; use that entry to avoid making unnecessary requests. The
;; only problem is for a client that assumes that the response
- ;; will always be within the requested ranage. For such a
+ ;; will always be within the requested range. For such a
;; client, we can get N copies of the same entry (one for each
;; XOVER command sent to the server).