Update javascript/ql/lib/semmle/javascript/ApiGraphs.qll

asgerf · yoff · asgerf · commit 73baa49c5d69 · 2022-05-24T11:57:30.000+02:00
Co-authored-by: yoff &lt;lerchedahl@gmail.com&gt;
diff --git a/javascript/ql/lib/semmle/javascript/ApiGraphs.qll b/javascript/ql/lib/semmle/javascript/ApiGraphs.qll
@@ -110,7 +110,7 @@ module API {
    * identifies both `x` parameters.
    *
    * Observe how `getMember("myMethod")` behaves when the member is defined via a getter. When thinking in code patterns,
-   * it might seem obvious that `getMember` should have obtained a reference the getter method itself.
+   * it might seem obvious that `getMember` should have obtained a reference to the getter method itself.
    * But when seeing it as an access to `myMethod` performed by the library, we can deduce that the relevant expression
    * on the client side is actually the return-value of the getter.
    *

Original file line number	Diff line number	Diff line change
`@@ -110,7 +110,7 @@ module API {`
`110`	`110`	* identifies both `x` parameters.
`111`	`111`	`*`
`112`	`112`	* Observe how `getMember("myMethod")` behaves when the member is defined via a getter. When thinking in code patterns,
`113`		- * it might seem obvious that `getMember` should have obtained a reference the getter method itself.
	`113`	+ * it might seem obvious that `getMember` should have obtained a reference to the getter method itself.
`114`	`114`	* But when seeing it as an access to `myMethod` performed by the library, we can deduce that the relevant expression
`115`	`115`	`* on the client side is actually the return-value of the getter.`
`116`	`116`	`*`