Spelling fixes

19 files changed, 48 insertions, 48 deletions

diff --git a/lisp/ChangeLog.5 b/lisp/ChangeLog.5
index 749e7f68b6c..4d762d517ec 100644
--- a/lisp/ChangeLog.5
+++ b/lisp/ChangeLog.5
@@ -7912,7 +7912,7 @@
 
 	* simple.el (choose-completion): Check for
 	next-single-property-change returning nil.
-	* mouse.el (mouse-choose-completion): Dito.
+	* mouse.el (mouse-choose-completion): Ditto.
 
 1994-07-28  Richard Stallman  <rms@mole.gnu.ai.mit.edu>
 
diff --git a/lisp/ChangeLog.8 b/lisp/ChangeLog.8
index cd090533b0b..27d19d93046 100644
--- a/lisp/ChangeLog.8
+++ b/lisp/ChangeLog.8
@@ -618,7 +618,7 @@
 1999-12-12  Martin Stjernholm  <mast@lysator.liu.se>
 
 	Changes for new style variable init system:
-	* cc-langs.el (c-common-init): Dito.
+	* cc-langs.el (c-common-init): Ditto.
 	* cc-styles.el: c-offsets-alist moved to cc-vars.el since it's
 	now customizable.
 	* cc-vars.el: Style variables may now take a value
diff --git a/lisp/char-fold.el b/lisp/char-fold.el
index d8d2ebc72ba..2b0b5b62f4d 100644
--- a/lisp/char-fold.el
+++ b/lisp/char-fold.el
@@ -253,7 +253,7 @@ Each entry is a list of a character and the strings that fold into it."
   :version "27.1")
 
 (defcustom char-fold-exclude char-fold--default-exclude
-  "Character foldings to remove from default decompisitions.
+  "Character foldings to remove from default decompositions.
 Each entry is a list of a character and the strings to remove from folding."
   :type '(alist :key-type (character :tag "Fold to character")
                 :value-type (repeat (string :tag "Fold from string")))
diff --git a/lisp/elec-pair.el b/lisp/elec-pair.el
index f3cbee70486..37a73281c23 100644
--- a/lisp/elec-pair.el
+++ b/lisp/elec-pair.el
@@ -230,7 +230,7 @@ inside a comment or string."
 	(electric-pair-mode nil)
         ;; When adding the "closer" delimiter, a job his function is
         ;; frequently used for, we don't want to munch any extra
-        ;; newlines above us.  That would be the default behaviour of
+        ;; newlines above us.  That would be the default behavior of
         ;; `electric-layout-mode', which potentially kicked in before
         ;; us to add these newlines, and is probably about to kick in
         ;; again after we add the closer.
diff --git a/lisp/electric.el b/lisp/electric.el
index a14deb71afb..7b683347175 100644
--- a/lisp/electric.el
+++ b/lisp/electric.el
@@ -423,10 +423,10 @@ If multiple rules match, only first one is executed.")
                   ;; newlines, re-indentation is prevented.
                   ;;
                   ;; FIXME: when `newline'ing, we exceptionally
-                  ;; prevent a specific behaviour of
+                  ;; prevent a specific behavior of
                   ;; `eletric-pair-mode', that of opening an extra
                   ;; newline between newly inserted matching paris.
-                  ;; In theory that behaviour should be provided by
+                  ;; In theory that behavior should be provided by
                   ;; `electric-layout-mode' instead, which should be
                   ;; possible given the current API.
                   ;;
diff --git a/lisp/emacs-lisp/backtrace.el b/lisp/emacs-lisp/backtrace.el
index 0c4c7987c3c..40784893391 100644
--- a/lisp/emacs-lisp/backtrace.el
+++ b/lisp/emacs-lisp/backtrace.el
@@ -709,7 +709,7 @@ line and recenter window line accordingly."
 (defun backtrace-print-to-string (obj &optional limit)
   "Return a printed representation of OBJ formatted for backtraces.
 Attempt to get the length of the returned string under LIMIT
-charcters with appropriate settings of `print-level' and
+characters with appropriate settings of `print-level' and
 `print-length.'  LIMIT defaults to `backtrace-line-length'."
   (backtrace--with-output-variables backtrace-view
     (backtrace--print-to-string obj limit)))
diff --git a/lisp/emacs-lisp/rx.el b/lisp/emacs-lisp/rx.el
index 0dc6e198663..a92c613b9aa 100644
--- a/lisp/emacs-lisp/rx.el
+++ b/lisp/emacs-lisp/rx.el
@@ -275,7 +275,7 @@ Return (REGEXP . PRECEDENCE)."
   ;;        -> "[A-Z@%[:digit:][:space:][:word:]]"
   ;;
   ;; Problem: If a subpattern is carefully written to be
-  ;; optimisable by regexp-opt, how do we prevent the transforms
+  ;; optimizable by regexp-opt, how do we prevent the transforms
   ;; above from destroying that property?
   ;; Example: (or "a" (or "abc" "abd" "abe"))
   (cond
diff --git a/lisp/faces.el b/lisp/faces.el
index 0f31628f5f9..df15764cc4a 100644
--- a/lisp/faces.el
+++ b/lisp/faces.el
@@ -1773,7 +1773,7 @@ If FRAME is nil, that stands for the selected frame."
 (defun defined-colors-with-face-attributes (&optional frame)
   "Return a list of colors supported for a particular frame.
 See `defined-colors' for arguments and return value. In contrast
-to `define-colorss' the elements of the returned list are color
+to `define-colors' the elements of the returned list are color
 strings with text properties, that make the color names render
 with the color they represent as background color."
   (mapcar
diff --git a/lisp/font-lock.el b/lisp/font-lock.el
index 01c19e6e874..c20b410a687 100644
--- a/lisp/font-lock.el
+++ b/lisp/font-lock.el
@@ -1101,7 +1101,7 @@ accessible portion of the current buffer."
 Called with two arguments BEG and END.")
 
 (defun font-lock-debug-fontify ()
-  "Reinitialise the font-lock machinery and (re-)fontify the buffer.
+  "Reinitialize the font-lock machinery and (re-)fontify the buffer.
 This functions is a convenience functions when developing font
 locking for a mode, and is not meant to be called from lisp functions."
   (interactive)
diff --git a/lisp/gnus/gnus-art.el b/lisp/gnus/gnus-art.el
index cfb185b3d1c..5745bf12bde 100644
--- a/lisp/gnus/gnus-art.el
+++ b/lisp/gnus/gnus-art.el
@@ -2088,7 +2088,7 @@ you're expecting some kind of apostrophe or quotation mark, then
 try this wash."
   (interactive)
   (article-translate-strings gnus-article-smartquotes-map))
-(define-obsolete-function-alias 'article-treat-dumquotes
+(define-obsolete-function-alias 'article-treat-dumbquotes
   #'article-treat-smartquotes "27.1")
 
 (defvar org-entities)
diff --git a/lisp/net/goto-addr.el b/lisp/net/goto-addr.el
index 40a067e6251..8aa5f16083e 100644
--- a/lisp/net/goto-addr.el
+++ b/lisp/net/goto-addr.el
@@ -100,7 +100,7 @@ A value of t means there is no limit--fontify regardless of the size."
   '("mailto:" "data:")
   "List of URI schemes to exclude from `goto-address-uri-schemes'.
 
-Customisations to this variable made after goto-addr is loaded
+Customizations to this variable made after goto-addr is loaded
 will have no effect.")
 
 (defvar goto-address-uri-schemes
@@ -111,7 +111,7 @@ will have no effect.")
               (copy-sequence thing-at-point-uri-schemes))
   "List of URI schemes matched by `goto-address-url-regexp'.
 
-Customisations to this variable made after goto-addr is loaded
+Customizations to this variable made after goto-addr is loaded
 will have no effect.")
 
 (defvar goto-address-url-regexp
diff --git a/lisp/net/nsm.el b/lisp/net/nsm.el
index 5dc5244e6d5..e430daa3823 100644
--- a/lisp/net/nsm.el
+++ b/lisp/net/nsm.el
@@ -384,7 +384,7 @@ Security (DTLS)\", \"(4.1.  General Guidelines)\"
 This check is a response to Logjam[1].  Logjam is an attack that
 allows an attacker with sufficient resource, and positioned
 between the user and the server, to downgrade vulnerable TLS
-connections to insecure 512-bit export grade crypotography.
+connections to insecure 512-bit export grade cryptography.
 
 The Logjam paper suggests using 1024-bit prime on the client to
 mitigate some effects of this attack, and upgrade to 2048-bit as
@@ -550,7 +550,7 @@ Security (TLS) and Datagram Transport Layer Security (DTLS)\",
 Due to its use of 64-bit block size, it is known that a
 ciphertext collision is highly likely when 2^32 blocks are
 encrypted with the same key bundle under 3-key 3DES.  Practical
-birthday attacks of this kind have been demostrated by Sweet32[1].
+birthday attacks of this kind have been demonstrated by Sweet32[1].
 As such, NIST is in the process of disallowing its use in TLS[2].
 
 [1]: Bhargavan, Leurent (2016).  \"On the Practical (In-)Security of
@@ -752,7 +752,7 @@ protocol."
         ;; Plain connection allowed.
         (memq :none saved-fingerprints)
         ;; We are pinning certs, and we have seen this host before,
-        ;; but the credientials for this host differs from the last
+        ;; but the credentials for this host differs from the last
         ;; times we saw it.
         (member (nsm-fingerprint status) saved-fingerprints))))
 
diff --git a/lisp/net/tramp-cmds.el b/lisp/net/tramp-cmds.el
index 96b11c7f524..607b0257206 100644
--- a/lisp/net/tramp-cmds.el
+++ b/lisp/net/tramp-cmds.el
@@ -359,7 +359,7 @@ The remote connection identified by SOURCE is flushed by
   ;; Append local file name if none is specified.
   (when (string-equal (file-remote-p target) target)
     (setq target (concat target (file-remote-p source 'localname))))
-  ;; Make them directoy names.
+  ;; Make them directory names.
   (setq source (directory-file-name source)
 	target (directory-file-name target))
 
diff --git a/lisp/org/org-agenda.el b/lisp/org/org-agenda.el
index 2404ca43dcb..2f0bd5f4e17 100644
--- a/lisp/org/org-agenda.el
+++ b/lisp/org/org-agenda.el
@@ -7636,7 +7636,7 @@ and deselects entries with tag `John' or matching the regexp `plot'.
 
 During entry of the filter, completion for tags, categories and effort
 values is offered.  Since the syntax for categories and tags is identical
-there should be no overlap between categoroes and tags.  If there is, tags
+there should be no overlap between categories and tags.  If there is, tags
 get priority.
 
 A single `\\[universal-argument]' prefix arg STRIP-OR-ACCUMULATE will negate the
diff --git a/lisp/org/org-table.el b/lisp/org/org-table.el
index 5f42db50688..a2e77e07392 100644
--- a/lisp/org/org-table.el
+++ b/lisp/org/org-table.el
@@ -1709,7 +1709,7 @@ The function assumes `org-table-copy-increment' is non-nil."
 	 (number-suffix-regexp (rx (and (one-or-more digit) string-end)))
 	 (analyze
 	  (lambda (field)
-	    ;; Analyse string FIELD and return information related to
+	    ;; Analyze string FIELD and return information related to
 	    ;; increment or nil.  When non-nil, return value has the
 	    ;; following scheme: (TYPE VALUE PATTERN) where
 	    ;; - TYPE is a symbol among `number', `prefix', `suffix'
diff --git a/lisp/org/org.el b/lisp/org/org.el
index f25c53caaff..11bc3641022 100644
--- a/lisp/org/org.el
+++ b/lisp/org/org.el
@@ -10008,7 +10008,7 @@ By default the available states are \"TODO\" and \"DONE\".  So, for this
 example: when the item starts with TODO, it is changed to DONE.
 When it starts with DONE, the DONE is removed.  And when neither TODO nor
 DONE are present, add TODO at the beginning of the heading.
-You can set up single-charcter keys to fast-select the new state.  See the
+You can set up single-character keys to fast-select the new state.  See the
 `org-todo-keywords' and `org-use-fast-todo-selection' for details.
 
 With `\\[universal-argument]' prefix ARG, force logging the state change \
diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el
index 1b3b92deaf5..0eed7acd0d7 100644
--- a/lisp/progmodes/python.el
+++ b/lisp/progmodes/python.el
@@ -3737,9 +3737,9 @@ Pdbtracking would open the file for current stack frame found in pdb output by
 `python-pdbtrack-stacktrace-info-regexp' and add overlay arrow in currently
 inspected line in that file.
 
-After command listed in `python-pdbtrack-continue-command' or
-`python-pdbtrack-exit-command' is sent to pdb, pdbtracking session is
-considered over.  Overlay arrow will be removed from currentry tracked
+After the command listed in `python-pdbtrack-continue-command' or
+`python-pdbtrack-exit-command' is sent to pdb, the pdbtracking session is
+considered over.  The overlay arrow will be removed from the currently tracked
 buffer.  Additionally, if `python-pdbtrack-kill-buffers' is non-nil, all
 files opened by pdbtracking will be killed."
   :type 'boolean
diff --git a/lisp/simple.el b/lisp/simple.el
index a0250cc2ac4..6d5030073bb 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -50,7 +50,7 @@ wait this many seconds after Emacs becomes idle before doing an update."
 The `undo' command will normally consider \"similar\" changes
 (like inserting characters) to be part of the same change.  This
 is called \"amalgamating\" the changes.  This variable says what
-the maximum number of changes condidered is when amalgamating.  A
+the maximum number of changes considered is when amalgamating.  A
 value of 1 means that nothing is amalgamated.")
 
 (defgroup killing nil
diff --git a/lisp/so-long.el b/lisp/so-long.el
index 49595a3fd91..3df2de97297 100644
--- a/lisp/so-long.el
+++ b/lisp/so-long.el
@@ -38,7 +38,7 @@
 ;; compacted into the smallest file size possible, which often entails removing
 ;; newlines should they not be strictly necessary).  This can result in lines
 ;; which are many thousands of characters long, and most programming modes
-;; simply aren't optimised (remotely) for this scenario, so performance can
+;; simply aren't optimized (remotely) for this scenario, so performance can
 ;; suffer significantly.
 ;;
 ;; When such files are detected, the command `so-long' is automatically called,
@@ -90,7 +90,7 @@
 ;; * Overview of modes and commands
 ;; --------------------------------
 ;; - `global-so-long-mode' - A global minor mode which enables the automated
-;;    behaviour, causing the user's preferred action to be invoked whenever a
+;;    behavior, causing the user's preferred action to be invoked whenever a
 ;;    newly-visited file contains excessively long lines.
 ;; - `so-long-mode' - A major mode, and the default action.
 ;; - `so-long-minor-mode' - A minor mode version of the major mode, and an
@@ -111,7 +111,7 @@
 ;;
 ;; On rare occasions you may choose to manually invoke the `so-long' command,
 ;; which invokes your preferred `so-long-action' (exactly as the automatic
-;; behaviour would do if it had detected long lines).  You might use this if a
+;; behavior would do if it had detected long lines).  You might use this if a
 ;; problematic file did not meet your configured criteria, and you wished to
 ;; trigger the performance improvements manually.
 ;;
@@ -120,7 +120,7 @@
 ;; available to `so-long' but, like any other mode, they can be invoked directly
 ;; if you have a need to do that (see also "Other ways of using so-long" below).
 ;;
-;; If the behaviour ever triggers when you did not want it to, you can use the
+;; If the behavior ever triggers when you did not want it to, you can use the
 ;; `so-long-revert' command to restore the buffer to its original state.
 
 ;; * Basic configuration
@@ -199,7 +199,7 @@
 ;;
 ;; Note that `so-long-minor-modes' is not useful for other global minor modes
 ;; (as distinguished from globalized minor modes), but in some cases it will be
-;; possible to inhibit or otherwise counter-act the behaviour of a global mode
+;; possible to inhibit or otherwise counter-act the behavior of a global mode
 ;; by overriding variables, or by employing hooks (see below).  You would need
 ;; to inspect the code for a given global mode (on a case by case basis) to
 ;; determine whether it's possible to inhibit it for a single buffer -- and if
@@ -211,7 +211,7 @@
 ;; If `so-long-action' is set to either `so-long-mode' or `so-long-minor-mode',
 ;; the buffer-local value for each variable in the list is set to the associated
 ;; value in the alist.  Use this to enforce values which will improve
-;; performance or otherwise avoid undesirable behaviours.  If `so-long-revert'
+;; performance or otherwise avoid undesirable behaviors.  If `so-long-revert'
 ;; is called, then the original values are restored.
 
 ;; * Hooks
@@ -325,7 +325,7 @@
 ;; meaning you would need to add to `safe-local-variable-values' in order to
 ;; avoid being queried about them.
 ;;
-;; Finally, the `so-long-predicate' user option enables the automated behaviour
+;; Finally, the `so-long-predicate' user option enables the automated behavior
 ;; to be determined by a custom function, if greater control is needed.
 
 ;; * Implementation notes
@@ -342,7 +342,7 @@
 
 ;; * Caveats
 ;; ---------
-;; The variables affecting the automated behaviour of this library (such as
+;; The variables affecting the automated behavior of this library (such as
 ;; `so-long-action') can be used as file- or dir-local values in Emacs 26+, but
 ;; not in previous versions of Emacs.  This is on account of improvements made
 ;; to `normal-mode' in 26.1, which altered the execution order with respect to
@@ -399,7 +399,7 @@
 ;; 0.6   - Added `so-long-minor-modes' and `so-long-hook'.
 ;; 0.5   - Renamed library to "so-long.el".
 ;;       - Added explicit `so-long-enable' command to activate our advice.
-;; 0.4   - Amended/documented behaviour with file-local 'mode' variables.
+;; 0.4   - Amended/documented behavior with file-local 'mode' variables.
 ;; 0.3   - Defer to a file-local 'mode' variable.
 ;; 0.2   - Initial release to EmacsWiki.
 ;; 0.1   - Experimental.
@@ -500,7 +500,7 @@ files would prevent Emacs from handling them correctly."
 (defcustom so-long-invisible-buffer-function #'so-long-deferred
   "Function called in place of `so-long' when the buffer is not displayed.
 
-This affects the behaviour of `global-so-long-mode'.
+This affects the behavior of `global-so-long-mode'.
 
 We treat invisible buffers differently from displayed buffers because, in
 cases where a library is using a buffer for behind-the-scenes processing,
@@ -548,7 +548,7 @@ Defaults to `so-long-detected-long-line-p'."
 (defun so-long--action-type ()
   "Generate a :type for `so-long-action' based on `so-long-action-alist'."
   ;; :type seemingly cannot be a form to be evaluated on demand, so we
-  ;; endeavour to keep it up-to-date with `so-long-action-alist' by
+  ;; endeavor to keep it up-to-date with `so-long-action-alist' by
   ;; calling this from `so-long--action-alist-setter'.
   `(radio ,@(mapcar (lambda (x) (list 'const :tag (cadr x) (car x)))
                     (assq-delete-all nil so-long-action-alist))
@@ -609,7 +609,7 @@ will be automatically processed; but custom actions can also do these things.
 The value `longlines-mode' causes that minor mode to be enabled.  See
 longlines.el for more details.
 
-Each action likewise determines the behaviour of `so-long-revert'.
+Each action likewise determines the behavior of `so-long-revert'.
 
 If the value is nil, or not defined in `so-long-action-alist', then no action
 will be taken."
@@ -756,7 +756,7 @@ By default this happens if `so-long-action' is set to either `so-long-mode'
 or `so-long-minor-mode'.  If `so-long-revert' is subsequently invoked, then the
 disabled modes are re-enabled by calling them with the numeric argument 1.
 
-`so-long-hook' can be used where more custom behaviour is desired.
+`so-long-hook' can be used where more custom behavior is desired.
 
 Please submit bug reports to recommend additional modes for this list, whether
 they are in Emacs core, GNU ELPA, or elsewhere."
@@ -833,7 +833,7 @@ If nil, no mode line indicator will be displayed."
 ;; Modes that go slowly and line lengths excessive
 ;; Font-lock performance becoming oppressive
 ;; All of my CPU tied up with strings
-;; These are a few of my least-favourite things
+;; These are a few of my least-favorite things
 
 (defvar-local so-long-original-values nil
   "Alist holding the buffer's original `major-mode' value, and other data.
@@ -916,7 +916,7 @@ If RESET is non-nil, remove any existing values before storing the new ones."
                  ;; triggered by mouse when some other window is selected.
                  "Revert the current action and invoke the chosen replacement.
 
-This commmand calls `so-long' with the selected action as an argument.")
+This command calls `so-long' with the selected action as an argument.")
                sym)
             :enable (not (and so-long--active
                               (eq ',actionfunc so-long-function)
@@ -1129,7 +1129,7 @@ This minor mode is a standard `so-long-action' option."
   (if so-long-minor-mode ;; We are enabling the mode.
       (progn
         ;; Housekeeping.  `so-long-minor-mode' might be invoked directly rather
-        ;; than via `so-long', so replicate the necessary behaviours.  The minor
+        ;; than via `so-long', so replicate the necessary behaviors.  The minor
         ;; mode also cares about whether `so-long' was already active, as we do
         ;; not want to remember values which were potentially overridden already.
         (unless (or so-long--calling so-long--active)
@@ -1201,9 +1201,9 @@ values), despite potential performance issues, type \\[so-long-revert].
 
 Use \\[so-long-commentary] for more information.
 
-Use \\[so-long-customize] to configure the behaviour."
+Use \\[so-long-customize] to configure the behavior."
   ;; Housekeeping.  `so-long-mode' might be invoked directly rather than via
-  ;; `so-long', so replicate the necessary behaviours.  We could use this same
+  ;; `so-long', so replicate the necessary behaviors.  We could use this same
   ;; test in `so-long-after-change-major-mode' to run `so-long-hook', but that's
   ;; not so obviously the right thing to do, so I've omitted it for now.
   (unless so-long--calling
@@ -1249,7 +1249,7 @@ Use \\[so-long-customize] to configure the behaviour."
 This advice acts before `so-long-mode', with the previous mode still active."
   (unless (derived-mode-p 'so-long-mode)
     ;; Housekeeping.  `so-long-mode' might be invoked directly rather than
-    ;; via `so-long', so replicate the necessary behaviours.
+    ;; via `so-long', so replicate the necessary behaviors.
     (unless so-long--calling
       (so-long-remember-all :reset))
     ;; Remember the original major mode, regardless.
@@ -1334,7 +1334,7 @@ This is the `so-long-revert-function' for `so-long-mode'."
     ;; Emacs 26+ has already called `hack-local-variables' (during
     ;; `run-mode-hooks'; provided there was a `buffer-file-name'), but for older
     ;; versions we need to call it here.  In Emacs 26+ the revised 'HANDLE-MODE'
-    ;; argument is set to `no-mode' (being the non-nil-and-non-t behaviour),
+    ;; argument is set to `no-mode' (being the non-nil-and-non-t behavior),
     ;; which we mimic here by binding `so-long--hack-local-variables-no-mode',
     ;; in order to prevent a local 'mode' variable from clobbering the major
     ;; mode we have just called.
@@ -1371,7 +1371,7 @@ because we do not want to downgrade the major mode in that scenario."
     ;; Act only if `so-long-mode' would be enabled by the current action.
     (when (and (symbolp (so-long-function))
                (provided-mode-derived-p (so-long-function) 'so-long-mode))
-      ;; Downgrade from `so-long-mode' to the `so-long-minor-mode' behaviour.
+      ;; Downgrade from `so-long-mode' to the `so-long-minor-mode' behavior.
       (setq so-long-function 'turn-on-so-long-minor-mode
             so-long-revert-function 'turn-off-so-long-minor-mode))))
 
@@ -1391,7 +1391,7 @@ and cannot be conveniently intercepted, so we are forced to replicate it here.
 
 This special-case code will ultimately be removed from Emacs, as it exists to
 deal with a deprecated feature; but until then we need to replicate it in order
-to inhibit our own behaviour in the presence of a header comment `mode'
+to inhibit our own behavior in the presence of a header comment `mode'
 declaration.
 
 If a file-local mode is detected in the header comment, then we call the
@@ -1526,7 +1526,7 @@ by testing the value against `major-mode'; but as we may have changed the
 major mode to `so-long-mode' by this point, that protection is insufficient
 and so we need to perform our own test.
 
-We likewise need to support an equivalent of the `no-mode' behaviour in 26.1+
+We likewise need to support an equivalent of the `no-mode' behavior in 26.1+
 to ensure that `so-long-mode-revert' will not restore a file-local mode again
 after it has already reverted to the original mode.
 
@@ -1673,7 +1673,7 @@ When such files are detected by `so-long-predicate', we invoke the selected
 
 Use \\[so-long-commentary] for more information.
 
-Use \\[so-long-customize] to configure the behaviour."
+Use \\[so-long-customize] to configure the behavior."
   :global t
   :group 'so-long
   (if global-so-long-mode