"modelling" -> "modeling" in docs

Author: owen-mc

docs/codeql/codeql-language-guides/customizing-library-models-for-cpp.rst

@@ -92,7 +92,7 @@ Since we are adding a new source, we need to add a tuple to the ``sourceModel``
 The first five values identify the callable (in this case a free function) to be modeled as a source.
 
 - The first value ``"boost::asio"`` is the namespace name.
-- The second value ``""`` is the name of the type (class) that contains the method. Because we're modelling a free function, the type is left blank.
+- The second value ``""`` is the name of the type (class) that contains the method. Because we're modeling a free function, the type is left blank.
 - The third value ``False`` is a flag that indicates whether or not the sink also applies to all overrides of the method. For a free function, this should be ``False``.
 - The fourth value ``"read_until"`` is the function name.
 - The fifth value is the function input type signature, which can be used to narrow down between functions that have the same name. In this case, we want the model to include all functions in ``boost::asio`` called ``read_until``.
@@ -128,7 +128,7 @@ Since we want to add a new sink, we need to add a tuple to the ``sinkModel`` ext
 The first five values identify the callable (in this case a free function) to be modeled as a sink.
 
 - The first value ``"boost::asio"`` is the namespace name.
-- The second value ``""`` is the name of the type (class) that contains the method. Because we're modelling a free function, the type is left blank.
+- The second value ``""`` is the name of the type (class) that contains the method. Because we're modeling a free function, the type is left blank.
 - The third value ``False`` is a flag that indicates whether or not the sink also applies to all overrides of the method. For a free function, this should be ``False``.
 - The fourth value ``"write"`` is the function name.
 - The fifth value is the function input type signature, which can be used to narrow down between functions that have the same name. In this case, we want the model to include all functions in ``boost::asio`` called ``write``.
@@ -165,7 +165,7 @@ Since we are adding flow through a function, we need to add tuples to the ``summ
 The first five values identify the callable (in this case free function) to be modeled as a summary.
 
 - The first value ``"boost::asio"`` is the namespace name.
-- The second value ``""`` is the name of the type (class) that contains the method. Because we're modelling a free function, the type is left blank.
+- The second value ``""`` is the name of the type (class) that contains the method. Because we're modeling a free function, the type is left blank.
 - The third value ``False`` is a flag that indicates whether or not the sink also applies to all overrides of the method. For a free function, this should be ``False``.
 - The fourth value ``"buffer"`` is the function name.
 - The fifth value is the function input type signature, which can be used to narrow down between functions that have the same name. In this case, we want the model to include all functions in ``boost::asio`` called ``buffer``.
@@ -207,7 +207,7 @@ Since we are adding a barrier, we need to add a tuple to the ``barrierModel`` ex
 The first five values identify the callable (in this case a free function) to be modeled as a barrier.
 
 - The first value ``""`` is the namespace name.
-- The second value ``""`` is the name of the type (class) that contains the method. Because we're modelling a free function, the type is left blank.
+- The second value ``""`` is the name of the type (class) that contains the method. Because we're modeling a free function, the type is left blank.
 - The third value ``False`` is a flag that indicates whether or not the barrier also applies to all overrides of the method. For a free function, this should be ``False``.
 - The fourth value ``"mysql_real_escape_string"`` is the function name.
 - The fifth value is the function input type signature, which can be used to narrow down between functions that have the same name.
@@ -247,7 +247,7 @@ Since we are adding a barrier guard, we need to add a tuple to the ``barrierGuar
 The first five values identify the callable (in this case a free function) to be modeled as a barrier guard.
 
 - The first value ``""`` is the namespace name.
-- The second value ``""`` is the name of the type (class) that contains the method. Because we're modelling a free function, the type is left blank.
+- The second value ``""`` is the name of the type (class) that contains the method. Because we're modeling a free function, the type is left blank.
 - The third value ``False`` is a flag that indicates whether or not the barrier guard also applies to all overrides of the method. For a free function, this should be ``False``.
 - The fourth value ``"is_safe"`` is the function name.
 - The fifth value is the function input type signature, which can be used to narrow down between functions that have the same name.

docs/ql-libraries/dataflow/dataflow.md

@@ -279,7 +279,7 @@ Content ContentSet::getAReadContent();
 which means that a `storeStep(n1, cs, n2)` will be interpreted as storing into _any_
 of `cs.getAStoreContent()`, and dually that a `readStep(n1, cs, n2)` will be
 interpreted as reading from _any_ of `cs.getAReadContent()`. In most cases, there
-will be a simple bijection between `ContentSet` and `Content`, but when modelling
+will be a simple bijection between `ContentSet` and `Content`, but when modeling
 for example flow through arrays it can be more involved (see [Example 4](#example-4)).
 
 It generally makes sense for stores to target `PostUpdateNode`s, but this is not a strict

ruby/ql/docs/flow_summaries.md

@@ -39,7 +39,7 @@ If `preservesValue = true` then value flow is propagated. If it is `false` then
 only taint flow is propagated.
 
 Any call to `chomp` in the database will be translated, in the dataflow graph,
-to a call to this fake definition. 
+to a call to this fake definition.
 
 `input` and `output` define the "from" and "to" locations in the flow summary.
 They use a custom string-based syntax which is similar to that used in `path`
@@ -232,7 +232,7 @@ preceding access path. It takes the same specifiers as `WithElement` and
 `Element`. It is only valid in an input path.
 
 This component has the effect of excluding the relevant elements when copying
-from input to output. It is useful for modelling methods that remove elements
+from input to output. It is useful for modeling methods that remove elements
 from a collection. For example to model a method that removes the first element
 from the receiver, we can do so like this: