diff options
| author | Glenn Morris <rgm@gnu.org> | 2017-11-27 19:28:28 -0500 |
|---|---|---|
| committer | Glenn Morris <rgm@gnu.org> | 2017-11-27 19:28:28 -0500 |
| commit | 22ff46e6d85e3f023eb84ef7e8fe3de8947caf81 (patch) | |
| tree | c654e0bf610c5ea0a8897f5e1476e8e60c0448f4 | |
| parent | 340f74daa8ac5fab0efc35d12ef5cf5cb3507b22 (diff) | |
| download | emacs-22ff46e6d85e3f023eb84ef7e8fe3de8947caf81.tar.gz | |
; Fix some comment typos
| -rw-r--r-- | lisp/gnus/message.el | 4 | ||||
| -rw-r--r-- | lisp/gnus/mm-decode.el | 2 | ||||
| -rw-r--r-- | lisp/gnus/smime.el | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/lisp/gnus/message.el b/lisp/gnus/message.el index d9f3427b95b..22de7fee81d 100644 --- a/lisp/gnus/message.el +++ b/lisp/gnus/message.el @@ -4775,7 +4775,7 @@ to find out how to use this." message-qmail-inject-program nil nil nil ;; qmail-inject's default behavior is to look for addresses on the ;; command line; if there're none, it scans the headers. - ;; yes, it does The Right Thing w.r.t. Resent-To and it's kin. + ;; yes, it does The Right Thing w.r.t. Resent-To and its kin. ;; ;; in general, ALL of qmail-inject's defaults are perfect for simply ;; reading a formatted (i. e., at least a To: or Resent-To header) @@ -4793,7 +4793,7 @@ to find out how to use this." (if (functionp message-qmail-inject-args) (funcall message-qmail-inject-args) message-qmail-inject-args))) - ;; qmail-inject doesn't say anything on it's stdout/stderr, + ;; qmail-inject doesn't say anything on its stdout/stderr, ;; we have to look at the retval instead (0 nil) (100 (error "qmail-inject reported permanent failure")) diff --git a/lisp/gnus/mm-decode.el b/lisp/gnus/mm-decode.el index c6ac0567fbb..82b378e6270 100644 --- a/lisp/gnus/mm-decode.el +++ b/lisp/gnus/mm-decode.el @@ -676,7 +676,7 @@ MIME-Version header before proceeding." (mm-alist-to-plist (cdr ctl)) (car ctl)) ;; what really needs to be done here is a way to link a - ;; MIME handle back to it's parent MIME handle (in a multilevel + ;; MIME handle back to its parent MIME handle (in a multilevel ;; MIME article). That would probably require changing ;; the mm-handle API so we simply store the multipart buffer ;; name as a text property of the "multipart/whatever" string. diff --git a/lisp/gnus/smime.el b/lisp/gnus/smime.el index f62b65a0661..21f8c09e1cb 100644 --- a/lisp/gnus/smime.el +++ b/lisp/gnus/smime.el @@ -67,7 +67,7 @@ ;; ;; To be able to verify messages you need to build up trust with ;; someone. Perhaps you trust the CA that issued your certificate, at -;; least I did, so I export it's certificates from my PKCS#12 +;; least I did, so I export its certificates from my PKCS#12 ;; certificate with: ;; ;; $ openssl pkcs12 -in mykey.p12 -cacerts -nodes > cacert.pem |