From: Glenn Morris <rgm@gnu.org>
Date: Sat, 28 Oct 2017 00:09:17 +0000 (-0400)
Subject: * lisp/button.el (button-activate): Fix doc typo.
X-Git-Tag: emacs-26.0.91~450
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=8bd9524a7c57c8fb208c0ecd3a7be96fbad74b0c;p=emacs.git

* lisp/button.el (button-activate): Fix doc typo.
---

diff --git a/lisp/button.el b/lisp/button.el
index a6090477c55..32cd995f5e4 100644
--- a/lisp/button.el
+++ b/lisp/button.el
@@ -232,7 +232,7 @@ property instead of `action'; if the button has no `mouse-action',
 the value of `action' is used instead.
 
 The action can either be a marker or a function.  If it's a
-marker then goto it.  Otherwise it it is a function then it is
+marker then goto it.  Otherwise if it is a function then it is
 called with BUTTON as only argument.  BUTTON is either an
 overlay, a buffer position, or (for buttons in the mode-line or
 header-line) a string."
diff --git a/lisp/doc-view.el b/lisp/doc-view.el
index a222076edb8..7213ea2ff6b 100644
--- a/lisp/doc-view.el
+++ b/lisp/doc-view.el
@@ -451,7 +451,7 @@ Typically \"page-%s.png\".")
     (if (and (eq 'pdf doc-view-doc-type)
              (executable-find "pdfinfo"))
         ;; We don't want to revert if the PDF file is corrupted which
-        ;; might happen when it it currently recompiled from a tex
+        ;; might happen when it is currently recompiled from a tex
         ;; file.  (TODO: We'd like to have something like that also
         ;; for other types, at least PS, but I don't know a good way
         ;; to test if a PS file is complete.)
diff --git a/lisp/url/url-queue.el b/lisp/url/url-queue.el
index 06a77404b58..84da6f60260 100644
--- a/lisp/url/url-queue.el
+++ b/lisp/url/url-queue.el
@@ -177,7 +177,7 @@ The variable `url-queue-timeout' sets a timeout."
   (with-current-buffer
       (if (and (bufferp (url-queue-buffer job))
 	       (buffer-live-p (url-queue-buffer job)))
-	  ;; Use the (partially filled) process buffer it it exists.
+	  ;; Use the (partially filled) process buffer if it exists.
 	  (url-queue-buffer job)
 	;; If not, just create a new buffer, which will probably be
 	;; killed again by the caller.