Skip to content

Commit f3f2c31

Browse files
RasmusWLjf205
andauthored
Docs: Apply suggestions from code review
Co-authored-by: James Fletcher <[email protected]>
1 parent 49dbb8c commit f3f2c31

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/codeql/writing-codeql-queries/debugging-data-flow-queries-using-partial-flow.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ As noted in the documentation for ``hasPartialFlow`` (for example, in the
8989
9090
This defines the exploration radius within which ``hasPartialFlow`` returns results.
9191

92-
To get good performance when using ``hasPartialFlow`` it is important to ensure the ``isSink`` predicate of the configuration has no results. Likewise when using ``hasPartialFlowRev`` the ``isSource`` predicate of the configuration should have no results
92+
To get good performance when using ``hasPartialFlow`` it is important to ensure the ``isSink`` predicate of the configuration has no results. Likewise, when using ``hasPartialFlowRev`` the ``isSource`` predicate of the configuration should have no results.
9393

9494
It is also useful to focus on a single source at a time as the starting point for the flow exploration. This is most easily done by adding a temporary restriction in the ``isSource`` predicate.
9595

0 commit comments

Comments
 (0)