From e28669e4876d8d1c6499a4c2e5a382a24780717f Mon Sep 17 00:00:00 2001 From: yoff Date: Thu, 27 Jan 2022 10:31:43 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Taus --- .../python/dataflow/new/internal/DataFlowPrivate.qll | 8 ++++---- .../python/dataflow/new/internal/DataFlowPublic.qll | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPrivate.qll b/python/ql/lib/semmle/python/dataflow/new/internal/DataFlowPrivate.qll index f8b9dea236e..39f0dfc457c 100644 --- 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 index d0b4e0aeba1..e167533a408 100644 --- 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;