Fix typos in comments.

lisp/cedet/semantic/util-modes.el

@@ -1022,7 +1022,7 @@ Argument EVENT describes the event that caused this function to be called."
 ;;;;
 
 ;; Highlight the first like of the function we are in if it is different
-;; from the the tag going off the top of the screen.
+;; from the tag going off the top of the screen.
 
 ;;;###autoload
 (defun global-semantic-highlight-func-mode (&optional arg)

lisp/dired.el

@@ -937,7 +937,7 @@ BEG..END is the line where the file info is located."
   ;; spaces there (and within the filename as well, of course).
   (save-excursion
     (let (file file-col other other-col)
-      ;; Check the there is indeed a file, and that there is anoter adjacent
+      ;; Check that there is indeed a file, and that there is anoter adjacent
       ;; file with which to align, and that additional spaces are needed to
       ;; align the filenames.
       (when (and (setq file (progn (goto-char beg)

lisp/international/fontset.el

@@ -292,7 +292,7 @@
 ;;	or a string FONT-NAME,
 ;;	or an object created by `font-spec'.
 ;;
-;; FAMILY may be nil, in which case, the the corresponding name of
+;; FAMILY may be nil, in which case, the corresponding name of
 ;; default face is used.  If REGISTRY contains a character `-', the
 ;; string before that is embedded in `CHARSET_REGISTRY' field, and the
 ;; string after that is embedded in `CHARSET_ENCODING' field.  If it

lisp/international/mule-cmds.el

@@ -854,7 +854,7 @@ and TO is ignored."
   (let ((no-other-defaults nil)
 	auto-cs)
     (unless (or (stringp from) find-file-literally)
-      ;; Find an auto-coding that is specified for the the current
+      ;; Find an auto-coding that is specified for the current
       ;; buffer and file from the region FROM and TO.
       (save-excursion
 	(save-restriction

lisp/mh-e/mh-utils.el

@@ -282,7 +282,7 @@ and displayed in a help buffer."
   "Display cheat sheet for the commands of the current prefix in minibuffer."
   (interactive)
   ;; We got here because the user pressed a "?", but he pressed a prefix key
-  ;; before that. Since the the key vector starts at index 0, the index of the
+  ;; before that. Since the key vector starts at index 0, the index of the
   ;; last keystroke is length-1 and thus the second to last keystroke is at
   ;; length-2. We use that information to obtain a suitable prefix character
   ;; from the recent keys.

lisp/progmodes/cc-engine.el

@@ -4382,7 +4382,7 @@ comment at the start of cc-engine.el for more info."
 
 (defun c-forward-<>-arglist (all-types)
   ;; The point is assumed to be at a "<".  Try to treat it as the open
-  ;; paren of an angle bracket arglist and move forward to the the
+  ;; paren of an angle bracket arglist and move forward to the
   ;; corresponding ">".  If successful, the point is left after the
   ;; ">" and t is returned, otherwise the point isn't moved and nil is
   ;; returned.  If ALL-TYPES is t then all encountered arguments in

lisp/progmodes/idlw-complete-structtag.el

@@ -79,7 +79,7 @@
 ;; Notes
 ;; -----
 ;;  - The structure definition assignment "state = {...}" must use the
-;;    same variable name as the the completion location "state.*".
+;;    same variable name as the completion location "state.*".
 ;;  - The structure definition must be in the same file.
 ;;  - The structure definition is searched backwards and then forward
 ;;    from the current position, until a definition with tags is found.

lisp/smerge-mode.el

@@ -705,7 +705,7 @@ An error is raised if not inside a conflict."
 	   ((save-excursion
 	      (goto-char mine-start)
 	      (re-search-forward smerge-begin-re end t))
-	    ;; There's a nested conflict and we're after the the beginning
+	    ;; There's a nested conflict and we're after the beginning
 	    ;; of the outer one but before the beginning of the inner one.
 	    ;; Of course, maybe this is not a nested conflict but in that
 	    ;; case it can only be something nastier that we don't know how

lisp/textmodes/table.el

@@ -4968,7 +4968,7 @@ only and must not be specified."
 	   (px (or internal-px (car (if (eq pivot 'left) lu-coordinate rb-coordinate))))
 	   (ty (- (cdr lu-coordinate) 2))
 	   (by (+ (cdr rb-coordinate) 2)))
-      ;; in case of finding the the first cell, get the last adding item on the list
+      ;; in case of finding the first cell, get the last adding item on the list
       (if (and (null internal-dir) first-only) (setq top-to-bottom (null top-to-bottom)))
       ;; travel up and process as recursion traces back (reverse order)
       (and cell
@@ -5008,7 +5008,7 @@ only and must not be specified."
 	   (py (or internal-py (if (eq pivot 'top) (cdr lu-coordinate) (1+ (cdr rb-coordinate)))))
 	   (lx (1- (car lu-coordinate)))
 	   (rx (1+ (car rb-coordinate))))
-      ;; in case of finding the the first cell, get the last adding item on the list
+      ;; in case of finding the first cell, get the last adding item on the list
       (if (and (null internal-dir) first-only) (setq left-to-right (null left-to-right)))
       ;; travel left and process as recursion traces back (reverse order)
       (and cell

lisp/vc-dir.el

@@ -321,7 +321,7 @@ If BODY uses EVENT, it should be a variable,
 
 (defun vc-dir-node-directory (node)
   ;; Compute the directory for NODE.
-  ;; If it's a directory node, get it from the the node.
+  ;; If it's a directory node, get it from the node.
   (let ((data (ewoc-data node)))
     (or (vc-dir-fileinfo->directory data)
 	;; Otherwise compute it from the file name.