Apply suggestions from code review

yoff · tausbn · web-flow · commit e28669e4876d · 2022-01-27T10:31:43.000+01:00
Co-authored-by: Taus &lt;tausbn@github.com&gt;
diff --git a/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPrivate.qll b/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPrivate.qll
@@ -1563,7 +1563,7 @@ import IterableUnpacking
  * There are a number of patterns available for the match statement.
  * Each one transfers data and content differently to its parts.
  *
- * Furthermore, given a successful match, we can infer some daa about
+ * Furthermore, given a successful match, we can infer some data about
  * the subject. Consider the example:
  * ```python
  * match choice:
@@ -1581,7 +1581,7 @@ import IterableUnpacking
  * By the binding rules, there is data flow from `choice` to `c`. But we
  * can infer the value of `c` to be either `'y'` or `'Y'` if the match succeeds.
  *
- * We will treat such inference separately as guards. First we will model the data flow
+ * We will treat such inferences separately as guards. First we will model the data flow
  * stemming from the bindings and the matching of shape. Below, 'subject' is not necessarily the
  * top-level subject of the match, but rather the part recursively matched by the current pattern.
  * For instance, in the example:
@@ -1696,7 +1696,7 @@ module MatchUnpacking {
    * syntax (toplevel): `case *var:`
    *
    * We decompose this flow into a read step and a store step. The read step
-   * reads both tupe and list content, the store step only stores list content.
+   * reads both tuple and list content, the store step only stores list content.
    * This way, we convert all content to list content.
    *
    * This is the read step.
@@ -1724,7 +1724,7 @@ module MatchUnpacking {
    * syntax (toplevel): `case *var:`
    *
    * We decompose this flow into a read step and a store step. The read step
-   * reads both tupe and list content, the store step only stores list content.
+   * reads both tuple and list content, the store step only stores list content.
    * This way, we convert all content to list content.
    *
    * This is the store step.
diff --git a/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPublic.qll b/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPublic.qll
@@ -485,7 +485,7 @@ class IterableElementNode extends Node, TIterableElementNode {
 }
 
 /**
- * A synthetic node representing elemnt content of a star pattern.
+ * A synthetic node representing element content of a star pattern.
  */
 class StarPatternElementNode extends Node, TStarPatternElementNode {
   CfgNode consumer;

Original file line number	Diff line number	Diff line change
`@@ -1563,7 +1563,7 @@ import IterableUnpacking`
`1563`	`1563`	`* There are a number of patterns available for the match statement.`
`1564`	`1564`	`* Each one transfers data and content differently to its parts.`
`1565`	`1565`	`*`
`1566`		`- * Furthermore, given a successful match, we can infer some daa about`
	`1566`	`+ * Furthermore, given a successful match, we can infer some data about`
`1567`	`1567`	`* the subject. Consider the example:`
`1568`	`1568`	* ```python
`1569`	`1569`	`* match choice:`
`@@ -1581,7 +1581,7 @@ import IterableUnpacking`
`1581`	`1581`	* By the binding rules, there is data flow from `choice` to `c`. But we
`1582`	`1582`	* can infer the value of `c` to be either `'y'` or `'Y'` if the match succeeds.
`1583`	`1583`	`*`
`1584`		`- * We will treat such inference separately as guards. First we will model the data flow`
	`1584`	`+ * We will treat such inferences separately as guards. First we will model the data flow`
`1585`	`1585`	`* stemming from the bindings and the matching of shape. Below, 'subject' is not necessarily the`
`1586`	`1586`	`* top-level subject of the match, but rather the part recursively matched by the current pattern.`
`1587`	`1587`	`* For instance, in the example:`
`@@ -1696,7 +1696,7 @@ module MatchUnpacking {`
`1696`	`1696`	* syntax (toplevel): `case *var:`
`1697`	`1697`	`*`
`1698`	`1698`	`* We decompose this flow into a read step and a store step. The read step`
`1699`		`- * reads both tupe and list content, the store step only stores list content.`
	`1699`	`+ * reads both tuple and list content, the store step only stores list content.`
`1700`	`1700`	`* This way, we convert all content to list content.`
`1701`	`1701`	`*`
`1702`	`1702`	`* This is the read step.`
`@@ -1724,7 +1724,7 @@ module MatchUnpacking {`
`1724`	`1724`	* syntax (toplevel): `case *var:`
`1725`	`1725`	`*`
`1726`	`1726`	`* We decompose this flow into a read step and a store step. The read step`
`1727`		`- * reads both tupe and list content, the store step only stores list content.`
	`1727`	`+ * reads both tuple and list content, the store step only stores list content.`
`1728`	`1728`	`* This way, we convert all content to list content.`
`1729`	`1729`	`*`
`1730`	`1730`	`* This is the store step.`
Original file line number	Diff line number	Diff line change
`@@ -485,7 +485,7 @@ class IterableElementNode extends Node, TIterableElementNode {`
`485`	`485`	`}`
`486`	`486`
`487`	`487`	`/**`
`488`		`- * A synthetic node representing elemnt content of a star pattern.`
	`488`	`+ * A synthetic node representing element content of a star pattern.`
`489`	`489`	`*/`
`490`	`490`	`class StarPatternElementNode extends Node, TStarPatternElementNode {`
`491`	`491`	`CfgNode consumer;`