hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2026-04-22 23:35:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Review fix.

Browse Source
This commit is contained in:
Anders Schack-Mulligen
2023-07-19 09:14:33 +02:00
parent aaea1ad2fa
commit afc46576f0
6 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-cpp-new.rst
View File

@@ -222,7 +222,7 @@ Global taint tracking is to global data flow as local taint tracking is to local
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Examples
~~~~~~~~

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-cpp.rst
View File

@@ -207,7 +207,7 @@ Global taint tracking is to global data flow as local taint tracking is to local
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Examples
~~~~~~~~

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-csharp.rst
View File

@@ -200,7 +200,7 @@ Global taint tracking is to global data flow what local taint tracking is to loc
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Flow sources
~~~~~~~~~~~~

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-java.rst
View File

@@ -214,7 +214,7 @@ Global taint tracking is to global data flow as local taint tracking is to local
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Flow sources
~~~~~~~~~~~~

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-python.rst
View File

@@ -258,7 +258,7 @@ Global taint tracking is to global data flow what local taint tracking is to loc
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Predefined sources and sinks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2
docs/codeql/codeql-language-guides/analyzing-data-flow-in-ruby.rst
View File

@@ -281,7 +281,7 @@ The global taint tracking library is used by applying the module ``TaintTracking
module MyFlow = TaintTracking::Global<MyFlowConfiguration>;
The resulting module is completely similar to the one obtained from ``DataFlow::Global<ConfigSig>``.
The resulting module has an identical signature to the one obtained from ``DataFlow::Global<ConfigSig>``.
Predefined sources and sinks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~