Merge pull request #7443 from github/nickrolfe/behavior

QL4QL: catch behaviour/behavior in ql/non-us-spelling

javascript/ql/experimental/adaptivethreatmodeling/lib/experimental/adaptivethreatmodeling/CodeToFeatures.qll

@@ -178,7 +178,7 @@ module Raw {
 
   /**
    * Returns a generated name for the entity. This name is generated such that
-   * entities with the same names have similar behaviour.
+   * entities with the same names have similar behavior.
    */
   private string getApproximateNameForEntity(Entity entity) {
     count(raw::DataFlow::CallNode call, int index | entityUsedAsArgumentToCall(entity, call, index)) =

javascript/ql/lib/semmle/javascript/dataflow/AbstractValues.qll

@@ -22,7 +22,7 @@
  *     value `nonzero`;
  *
  *   - at other times, the analysis does not have enough information
- *     to precisely model the behaviour of certain program elements:
+ *     to precisely model the behavior of certain program elements:
  *     for example, the current flow analysis is intra-procedural,
  *     so it does not model parameter passing or return values, and
  *     hence has to make worst-case assumptions about the possible

javascript/ql/lib/semmle/javascript/dataflow/DataFlow.qll

@@ -1035,7 +1035,7 @@ module DataFlow {
    * Provides classes representing various kinds of calls.
    *
    * Subclass the classes in this module to introduce new kinds of calls. If you want to
-   * refine the behaviour of the analysis on existing kinds of calls, subclass `InvokeNode`
+   * refine the behavior of the analysis on existing kinds of calls, subclass `InvokeNode`
    * instead.
    */
   module Impl {

javascript/ql/lib/semmle/javascript/meta/ExtractionMetrics.qll

@@ -3,7 +3,7 @@ import javascript
 /**
  * INTERNAL: Do not use in ordinary queries.
  *
- * Extraction metrics for profiling extraction behaviours.
+ * Extraction metrics for profiling extraction behaviors.
  */
 module ExtractionMetrics {
   /**

javascript/ql/src/experimental/Security/CWE-020/PostMessageNoOriginCheck.ql

@@ -1,7 +1,7 @@
 /**
  * @name Missing `MessageEvent.origin` verification in `postMessage` handlers
  * @description Missing the `MessageEvent.origin` verification in `postMessage` handlers, allows any windows to send arbitrary data to the `MessageEvent` listener.
- * This could lead to unexpected behaviour, especially when `MessageEvent.data` is used in an unsafe way.
+ * This could lead to unexpected behavior, especially when `MessageEvent.data` is used in an unsafe way.
  * @kind problem
  * @problem.severity warning
  * @precision high