Use more American English

README.md

@@ -102,7 +102,7 @@ programs for checking the syntax and semantics of your programs. By default,
 linters will be re-run in the background to check your syntax when you open
 new buffers or as you make edits to your files.
 
-The behaviour of linting can be configured with a variety of options,
+The behavior of linting can be configured with a variety of options,
 documented in [the Vim help file](doc/ale.txt). For more information on the
 options ALE offers, consult `:help ale-options` for global options and `:help
 ale-integration-options` for options specified to particular linters.
@@ -738,7 +738,7 @@ while you type. ALE uses a timeout which is cancelled and reset every time you
 type, and this delay can be increased so linters are run less often. See
 `:help g:ale_lint_delay` for more information.
 
-If you don't wish to run linters while you type, you can disable that behaviour.
+If you don't wish to run linters while you type, you can disable that behavior.
 Set `g:ale_lint_on_text_changed` to `never`. You won't get as frequent error
 checking, but ALE shouldn't block your ability to edit a document after you save
 a file, so the asynchronous nature of the plugin will still be an advantage.

doc/ale-javascript.txt

@@ -138,7 +138,7 @@ g:ale_javascript_flow_use_respect_pragma
 
   By default, ALE will use the `--respect-pragma` option for `flow`, so only
   files with the `@flow` pragma are checked by ALE. This option can be set to
-  `0` to disable that behaviour, so all files can be checked by `flow`.
+  `0` to disable that behavior, so all files can be checked by `flow`.
 
 
 ===============================================================================

doc/ale.txt

@@ -127,7 +127,7 @@ their relevant options.
 * By showing balloons for your mouse cursor        - |g:ale_set_balloons|
 
 Please consult the documentation for each option, which can reveal some other
-ways of tweaking the behaviour of each way of displaying problems. You can
+ways of tweaking the behavior of each way of displaying problems. You can
 disable or enable whichever options you prefer.
 
 Most settings can be configured for each buffer. (|b:| instead of |g:|),
@@ -2885,7 +2885,7 @@ ALELast                                                               *ALELast*
   the last or first warning or error in the file, respectively.
 
   `ALEPrevious` and `ALENext` take optional flags arguments to custom their
-  behaviour :
+  behavior :
   `-wrap` enable wrapping around the file
   `-error`, `-warning` and `-info` enable jumping to errors, warnings or infos
     respectively, ignoring anything else. They are mutually exclusive and if
@@ -3527,7 +3527,7 @@ ale#linter#Define(filetype, linter)                       *ale#linter#Define()*
   contents of the buffer being checked. All occurrences of `%t` in command
   strings will reference the one temporary file. The temporary file will be
   created inside a temporary directory, and the entire temporary directory
-  will be automatically deleted, following the behaviour of
+  will be automatically deleted, following the behavior of
   |ale#command#ManageDirectory|. This option can be used for some linters which
   do not support reading from stdin.
 
@@ -3552,7 +3552,6 @@ ale#linter#Define(filetype, linter)                       *ale#linter#Define()*
   be used to replace those characters to avoid formatting issues.
 
                                                   *ale-linter-loading-behavior*
-                                                 *ale-linter-loading-behaviour*
 
   Linters for ALE will be loaded by searching |runtimepath| in the following
   format: >