Skip to content

Commit 2bea328

Browse files
committed
Update customizing-library-models-for-java-and-kotlin.rst
1 parent 849ec72 commit 2bea328

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/codeql/codeql-language-guides/customizing-library-models-for-java-and-kotlin.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -301,9 +301,9 @@ Threat models
301301

302302
The ``default`` threat model is included by default. The ``default`` grouping only contains one child threat model, the ``remote`` threat model, which represents remote HTTP requests.
303303

304-
You can extend the CodeQL threat model to specify other sources of untrusted data. For example, if your codebase considers local files to be sources of tainted data, you can specify the `local` threat model to be used in CodeQL analysis.
304+
You can extend the CodeQL threat model to specify other sources of untrusted data. For example, if your codebase considers local files to be sources of tainted data, you can specify the ``local`` threat model to be used in CodeQL analysis.
305305

306-
The shared `threat-models` library pack exposes the following extensible predicates:
306+
The shared ``threat-models`` library pack exposes the following extensible predicates:
307307

308308
- ``threatModelConfiguration(string kind, boolean enabled, int priority)``. This is used to configure which threat models are enabled or disabled for the analysis.
309309
- ``threatModelGrouping(string kind, string group)``. This is used to define the taxonomy of threat models as a parent-child hierarchy.
@@ -324,5 +324,5 @@ Each data row consists of three columns:
324324

325325
- The first value ``local`` is the name of the threat model to enable or disable.
326326
- The second value ``true`` is a boolean that you can set to ``true`` to enable the named threat model, or ``false`` to disable it.
327-
- The third value `0` is an integer specifying the order in which to process the row. Rows are processed in ascending order of priority.
327+
- The third value ``0`` is an integer specifying the order in which to process the row. Rows are processed in ascending order of priority.
328328

0 commit comments

Comments
 (0)