Skip to content

Fix typos in the instructions #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 19, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 2/challenge-1/instructions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Challenge 1 - add the Code Scanning GitHub action to a repository
In this challenge, we will enable code scanning on a fork of this repository and observe what vulenrabilities CodeQL finds. The repository contains several intentionally vulnerable code snippets.
In this challenge, we will enable code scanning on a fork of this repository and observe what vulnerabilities CodeQL finds. The repository contains several intentionally vulnerable code snippets.

If you prefer, you can choose another open source project, make a fork of it on your personal GitHub account and then enable Code Scanning on it. You can also choose one of your own public projects instead. If you encounter problems, see documentation for [enabling code scanning](https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#configuring-code-scanning-automatically).

Expand Down
2 changes: 1 addition & 1 deletion 2/challenge-4/instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ from Call call
where call.getLocation().getFile().getRelativePath().regexpMatch("2/challenge-1/.*")
select call
```
2. Hover over `Call` in the third line. This will show you the defnintion of the `Call` type. You can always hover over any part of the query to see if there is a defnition for it.
2. Hover over `Call` in the third line. This will show you the definition of the `Call` type. You can always hover over any part of the query to see if there is a definition for it.
3. Right click anywhere in the writing area of the query file and choose "CodeQL: Run Query on Selected Database"
4. After a few seconds you should see results, like so:

Expand Down