Fix non-US spelling of 'behavior'

cpp/ql/lib/DefaultOptions.qll

@@ -73,7 +73,7 @@ class Options extends string {
    *   __assume(0);
    * ```
    * (note that in this case if the hint is wrong and the expression is reached at
-   * runtime, the program's behaviour is undefined)
+   * runtime, the program's behavior is undefined)
    */
   predicate exprExits(Expr e) {
     e.(AssumeExpr).getChild(0).(CompileTimeConstantInt).getIntValue() = 0 or

cpp/ql/lib/Options.qll

@@ -50,7 +50,7 @@ class CustomOptions extends Options {
    *   __assume(0);
    * ```
    * (note that in this case if the hint is wrong and the expression is reached at
-   * runtime, the program's behaviour is undefined)
+   * runtime, the program's behavior is undefined)
    */
   override predicate exprExits(Expr e) { Options.super.exprExits(e) }
 

cpp/ql/lib/experimental/semmle/code/cpp/rangeanalysis/InBoundsPointerDeref.qll

@@ -5,7 +5,7 @@
  * `Instruction` level), and then using the array length analysis and the range
  * analysis together to prove that some of these pointer dereferences are safe.
  *
- * The analysis is soundy, i.e. it is sound if no undefined behaviour is present
+ * The analysis is soundy, i.e. it is sound if no undefined behavior is present
  * in the program.
  * Furthermore, it crucially depends on the soundiness of the range analysis and
  * the array length analysis.

cpp/ql/lib/semmle/code/cpp/exprs/Lambda.qll

@@ -118,7 +118,7 @@ class LambdaCapture extends Locatable, @lambdacapture {
    * An identifier is captured by reference if:
    *   - It is explicitly captured by reference.
    *   - It is implicitly captured, and the lambda's default capture mode is by-reference.
-   *   - The identifier is "this". [Said behaviour is dictated by the C++11 standard, but it
+   *   - The identifier is "this". [Said behavior is dictated by the C++11 standard, but it
    *                                is actually "*this" being captured rather than "this".]
    */
   predicate isCapturedByReference() { lambda_capture(this, _, _, _, true, _, _) }

cpp/ql/src/Likely Bugs/Format/SnprintfOverflow.qhelp

@@ -3,7 +3,7 @@
   "qhelp.dtd">
 <qhelp>
 <overview>
-<p>The return value of a call to <code>snprintf</code> is the number of characters that <i>would have</i> been written to the buffer assuming there was sufficient space.  In the event that the operation reaches the end of the buffer and more than one character is discarded, the return value will be greater than the buffer size.  This can cause incorrect behaviour, for example:
+<p>The return value of a call to <code>snprintf</code> is the number of characters that <i>would have</i> been written to the buffer assuming there was sufficient space.  In the event that the operation reaches the end of the buffer and more than one character is discarded, the return value will be greater than the buffer size.  This can cause incorrect behavior, for example:
 </p>
 </overview>
 

csharp/ql/lib/semmle/code/csharp/security/dataflow/ReDoSQuery.qll

@@ -75,7 +75,7 @@ class ExponentialRegexDataflow extends DataFlow2::Configuration {
 
 /**
  * An expression passed as the `input` to a call to a `Regex` method, where the regex appears to
- * have exponential behaviour.
+ * have exponential behavior.
  */
 class ExponentialRegexSink extends DataFlow::ExprNode, Sink {
   ExponentialRegexSink() {

java/ql/lib/semmle/code/java/dataflow/FlowSteps.qll

@@ -130,7 +130,7 @@ private class NumberTaintPreservingCallable extends TaintPreservingCallable {
  * included in this type however, then a tainted `Container` would imply that its `field` is also
  * tainted (but not vice versa).
  *
- * Note that `TaintTracking::Configuration` applies this behaviour by default to array, collection,
+ * Note that `TaintTracking::Configuration` applies this behavior by default to array, collection,
  * map-key and map-value content, so that e.g. a tainted `Map` is assumed to have tainted keys and values.
  */
 abstract class TaintInheritingContent extends DataFlow::Content { }

java/ql/src/utils/flowtestcasegenerator/GenerateFlowTestCase.qll

@@ -85,7 +85,7 @@ SupportMethod getASupportMethod() {
 }
 
 /**
- * Returns a CSV specification of the taint-/value-propagation behaviour of a test support method (`get` or `newWith` method).
+ * Returns a CSV specification of the taint-/value-propagation behavior of a test support method (`get` or `newWith` method).
  */
 query string getASupportMethodModel() { result = getASupportMethod().getCsvModel() }
 

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

python/ql/lib/semmle/python/objects/Callables.qll

@@ -382,7 +382,7 @@ class BuiltinMethodObjectInternal extends CallableObjectInternal, TBuiltinMethod
 /**
  * Class representing bound-methods.
  * Note that built-in methods, such as `[].append` are also represented as bound-methods.
- * Although built-in methods and bound-methods are distinct classes in CPython, their behaviour
+ * Although built-in methods and bound-methods are distinct classes in CPython, their behavior
  * is the same and we treat them identically.
  */
 class BoundMethodObjectInternal extends CallableObjectInternal, TBoundMethod {