spelling: mutually

jsoref · jsoref · commit 02f3ce1c439e · 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
@@ -20,7 +20,7 @@
  * `getCallable` is set to `none()`. The member predicate `ExtractedDataFlowCall::getCallable` is _not_ the mechanism for
  * call resolution in global data flow. That mechanism is `getViableCallable`.
  * Resolving a call to a non-extracted callable goes via `LibraryCallable::getACall`, which may involve type tracking.
- * To avoid that type tracking becomes mutualy recursive with data flow, type tracking must use a call graph not including summaries.
+ * To avoid that type tracking becomes mutually recursive with data flow, type tracking must use a call graph not including summaries.
  * Type tracking sees the callgraph given by `ExtractedDataFlowCall::getACallable`.
  *
  * We do not support summaries of special methods via the special methods framework,

Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@`
`20`	`20`	* `getCallable` is set to `none()`. The member predicate `ExtractedDataFlowCall::getCallable` is _not_ the mechanism for
`21`	`21`	* call resolution in global data flow. That mechanism is `getViableCallable`.
`22`	`22`	* Resolving a call to a non-extracted callable goes via `LibraryCallable::getACall`, which may involve type tracking.
`23`		`- * To avoid that type tracking becomes mutualy recursive with data flow, type tracking must use a call graph not including summaries.`
	`23`	`+ * To avoid that type tracking becomes mutually recursive with data flow, type tracking must use a call graph not including summaries.`
`24`	`24`	* Type tracking sees the callgraph given by `ExtractedDataFlowCall::getACallable`.
`25`	`25`	`*`
`26`	`26`	`* We do not support summaries of special methods via the special methods framework,`