Skip to content

Commit 32b264b

Browse files
yoffmchammer01
andauthored
Apply suggestions from code review
Co-authored-by: mc <[email protected]>
1 parent ac04308 commit 32b264b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/codeql/codeql-language-guides/using-api-graphs-in-python.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,9 @@ following snippet demonstrates.
3131
3232
➤ `See this in the query console on LGTM.com <https://lgtm.com/query/1876172022264324639/>`__.
3333

34-
This query selects the API graph node corresponding to the ``re`` module. This node represent the fact that the ``re`` module has been imported rather than a specific place in the program where the import happens. Therefore, there will be at most one result per project, and it will not have a useful location, so you have to click `Show 1 non-source result` in order to see it.
34+
This query selects the API graph node corresponding to the ``re`` module. This node represents the fact that the ``re`` module has been imported rather than a specific location in the program where the import happens. Therefore, there will be at most one result per project, and it will not have a useful location, so you'll have to click `Show 1 non-source result` in order to see it.
3535

36-
To find places in the program where the ``re`` module is referenced, you can use the ``getAUse`` method. The following query selects all references to the ``re`` module in the current database.
36+
To find where the ``re`` module is referenced in the program, you can use the ``getAUse`` method. The following query selects all references to the ``re`` module in the current database.
3737

3838
.. code-block:: ql
3939

0 commit comments

Comments
 (0)