Skip to content

Commit 56f51ee

Browse files
committed
use parameterized rather than parameterised
1 parent deecf76 commit 56f51ee

2 files changed

Lines changed: 17 additions & 17 deletions

File tree

docs/codeql/ql-language-reference/modules.rst

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -133,14 +133,14 @@ defined :ref:`above <library-modules>`:
133133
This defines an explicit module named ``M``. The body of this module defines
134134
the class ``OneTwo``.
135135

136-
.. _parameterised-modules:
136+
.. _parameterized-modules:
137137

138-
Parameterised modules
138+
Parameterized modules
139139
=====================
140140

141-
Parameterised modules are QL's approach to generic programming.
142-
Similar to explicit modules, parameterised modules are defined within other modules using the keywork ``module``.
143-
In addition to the module name, parameterised modules declare one or more parameters between the name and the module body.
141+
Parameterized modules are QL's approach to generic programming.
142+
Similar to explicit modules, parameterized modules are defined within other modules using the keywork ``module``.
143+
In addition to the module name, parameterized modules declare one or more parameters between the name and the module body.
144144

145145
For example, consider the module ``ApplyFooThenBar``, which takes two predicate parameters and defines a new predicate
146146
that applies them one after the other:
@@ -154,9 +154,9 @@ that applies them one after the other:
154154
}
155155
}
156156
157-
Parameterised modules cannot be directly referenced.
157+
Parameterized modules cannot be directly referenced.
158158
Instead, they are instantiated with arguments passed between ``<`` and ``>``.
159-
Instantiated parameterised modules can be used as a module expression, identical to explicit module references.
159+
Instantiated parameterized modules can be used as a module expression, identical to explicit module references.
160160

161161
For example, we can instantiate ``ApplyFooThenBar`` with two identical arguments ``increment``, creating a module
162162
containing a predicate that adds 2:
@@ -170,7 +170,7 @@ containing a predicate that adds 2:
170170
171171
select IncrementTwice::apply(40) // 42
172172
173-
The parameters of a parameterised module are (meta-)typed with :ref:`signatures <signatures>`.
173+
The parameters of a parameterized module are (meta-)typed with :ref:`signatures <signatures>`.
174174

175175
For example, in the previous two snippets, we relied on the predicate signature ``transformer``:
176176

@@ -179,8 +179,8 @@ For example, in the previous two snippets, we relied on the predicate signature
179179
bindingset[x]
180180
signature int transformer(int x);
181181
182-
The instantiation of parameterised modules is applicative, meaning that repeated instantiation of a module using
183-
identical arguments results in the same object. This is particularly relevant for type definitions inside parameterised
182+
The instantiation of parameterized modules is applicative, meaning that repeated instantiation of a module using
183+
identical arguments results in the same object. This is particularly relevant for type definitions inside parameterized
184184
modules as :ref:`classes <classes>` or via :ref:`newtype <algebraic-datatypes>`.
185185

186186
For example, the following generates an error for the second call to ``foo``, but not for the first:
@@ -211,10 +211,10 @@ between the two parameters:
211211
212212
module Extends<TSig T> { signature class Type extends T; }
213213
214-
module ParameterisedModule<TSig T1, Extends<T1>::Type T2> { ... }
214+
module ParameterizedModule<TSig T1, Extends<T1>::Type T2> { ... }
215215
216216
Dependently typed parameters are particularly useful in combination with
217-
:ref:`parameterised module signatures <parameterised-module-signatures>`.
217+
:ref:`parameterized module signatures <parameterized-module-signatures>`.
218218

219219
.. _module-bodies:
220220

docs/codeql/ql-language-reference/signatures.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
Signatures
88
##########
99

10-
Parameterised modules use signatures as a type system for their parameters.
10+
Parameterized modules use signatures as a type system for their parameters.
1111
There are three categories of signatures: **predicate signatures**, **type signatures**, and **module signatures**.
1212

1313
Predicate signatures
@@ -76,7 +76,7 @@ In detail, a type signature definition consists of:
7676
#. The keyword ``module``.
7777
#. The name of the module signature. This is an `identifier <https://codeql.github.com/docs/ql-language-reference/ql-language-specification/#identifiers>`_
7878
starting with a uppercase letter.
79-
#. Optionally, a list of parameters for :ref:`parameterised module signatures <parameterised-module-signatures>`.
79+
#. Optionally, a list of parameters for :ref:`parameterized module signatures <parameterized-module-signatures>`.
8080
#. The module signature body, consisting of type signatures and predicate signatures enclosed in braces.
8181
The ``signature`` keyword is omitted for these contained signatures.
8282

@@ -95,12 +95,12 @@ For example:
9595
predicate restriction(T t) { t = A() }
9696
}
9797
98-
.. _parameterised-module-signatures:
98+
.. _parameterized-module-signatures:
9999

100-
Parameterised module signatures
100+
Parameterized module signatures
101101
-------------------------------
102102

103-
Module signatures can themselves be paramterised in exactly the same way as parameterised modules.
103+
Module signatures can themselves be parameterized in exactly the same way as parameterized modules.
104104
This is particularly useful in combination with the dependent typing of module parameters.
105105

106106
For example:

0 commit comments

Comments
 (0)