spelling: flow

jsoref · jsoref · commit df9c8c7661ac · 2022-10-13T11:21:09.000-04:00
Signed-off-by: Josh Soref &lt;2119212+jsoref@users.noreply.github.com&gt;
diff --git a/python/ql/lib/semmle/python/dataflow/new/internal/FlowSummaryImplSpecific.qll b/python/ql/lib/semmle/python/dataflow/new/internal/FlowSummaryImplSpecific.qll
@@ -13,7 +13,7 @@
  * Having both extracted and non-extracted callables means that we now have three types of calls:
  * - Extracted calls to extracted callables, either `NormalCall` or `SpecialCall`. These are handled by standard data flow.
  * - Extracted calls to non-extracted callables, `LibraryCall`. These are handled by loking up the relevant summary when the
- *   global data flwo graph is connected up via `getViableCallable`.
+ *   global data flow graph is connected up via `getViableCallable`.
  * - Non-extracted calls, `SummaryCall`. These are synthesised by the flow summary framework.
  *
  * The first two can be referred to as `ExtractedDataFlowCall`. In fact, `LibraryCall` is a subclass of `NormalCall`, where

Original file line number	Diff line number	Diff line change
`@@ -13,7 +13,7 @@`
`13`	`13`	`* Having both extracted and non-extracted callables means that we now have three types of calls:`
`14`	`14`	* - Extracted calls to extracted callables, either `NormalCall` or `SpecialCall`. These are handled by standard data flow.
`15`	`15`	* - Extracted calls to non-extracted callables, `LibraryCall`. These are handled by loking up the relevant summary when the
`16`		- * global data flwo graph is connected up via `getViableCallable`.
	`16`	+ * global data flow graph is connected up via `getViableCallable`.
`17`	`17`	* - Non-extracted calls, `SummaryCall`. These are synthesised by the flow summary framework.
`18`	`18`	`*`
`19`	`19`	* The first two can be referred to as `ExtractedDataFlowCall`. In fact, `LibraryCall` is a subclass of `NormalCall`, where