Apply suggestions from code review

asgerf · nickrolfe · asgerf · commit 1ae97d9d5484 · 2022-05-24T11:57:30.000+02:00
Co-authored-by: Nick Rolfe &lt;nickrolfe@github.com&gt;
diff --git a/javascript/ql/lib/semmle/javascript/ApiGraphs.qll b/javascript/ql/lib/semmle/javascript/ApiGraphs.qll
@@ -56,7 +56,7 @@ module API {
    *
    * ### Access paths and edge labels
    *
-   * Nodes in the API graph nodes are associated with a set of access paths, describing a series of operations
+   * Nodes in the API graph are associated with a set of access paths, describing a series of operations
    * that may be performed to obtain that value.
    *
    * For example, the access path `API::moduleImport("lodash").getMember("extend")` represents the action of
@@ -77,7 +77,7 @@ module API {
    * Because the implementation of the external library is not visible, it is not known exactly what operations
    * it will perform on values that flow there. Instead, the edges starting from a def-node are operations that would
    * lead to an observable effect within the current codebase; without knowing for certain if the library will actually perform
-   * those operations. (When constructing these edge, we assume the library is somewhat well-behaved).
+   * those operations. (When constructing these edges, we assume the library is somewhat well-behaved).
    *
    * For example, given this snippet:
    * ```js

Original file line number	Diff line number	Diff line change
`@@ -56,7 +56,7 @@ module API {`
`56`	`56`	`*`
`57`	`57`	`* ### Access paths and edge labels`
`58`	`58`	`*`
`59`		`- * Nodes in the API graph nodes are associated with a set of access paths, describing a series of operations`
	`59`	`+ * Nodes in the API graph are associated with a set of access paths, describing a series of operations`
`60`	`60`	`* that may be performed to obtain that value.`
`61`	`61`	`*`
`62`	`62`	* For example, the access path `API::moduleImport("lodash").getMember("extend")` represents the action of
`@@ -77,7 +77,7 @@ module API {`
`77`	`77`	`* Because the implementation of the external library is not visible, it is not known exactly what operations`
`78`	`78`	`* it will perform on values that flow there. Instead, the edges starting from a def-node are operations that would`
`79`	`79`	`* lead to an observable effect within the current codebase; without knowing for certain if the library will actually perform`
`80`		`- * those operations. (When constructing these edge, we assume the library is somewhat well-behaved).`
	`80`	`+ * those operations. (When constructing these edges, we assume the library is somewhat well-behaved).`
`81`	`81`	`*`
`82`	`82`	`* For example, given this snippet:`
`83`	`83`	* ```js