Skip to content

Commit e37f412

Browse files
committed
chore: fix readme instructions about grading
github/gitlab irrelevant after #84 also removed some dead links/references
1 parent 6cd34cb commit e37f412

File tree

1 file changed

+2
-9
lines changed

1 file changed

+2
-9
lines changed

README.md

+2-9
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,6 @@
1313
![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/podium/elixir-secure-coding/new%20content)
1414
<br />
1515

16-
![GitHub forks](https://img.shields.io/github/forks/podium/elixir-secure-coding?style=social)
17-
![Twitter URL](https://img.shields.io/twitter/url?style=social&url=https%3A%2F%2Ftwitter.com%2Fintent%2Ftweet%3Furl%3Dhttps%253A%252F%252Fgithub.com%252Fpodium%252Felixir-secure-coding%26text%3DCheck%2520out%2520Elixir%2520Secure%2520Coding%2520Training%2520-%2520originally%2520authored%2520by%2520%40HoldenOullette%2520for%2520%40PodiumHQ%253A)
18-
<br />
19-
2016
### An all-encompassing, opinionated cybersecurity curriculum designed for enterprise use at software companies using the [Elixir](https://elixir-lang.org/) programming language.
2117

2218
[About](#about) |
@@ -72,7 +68,7 @@ Currently the curriculum is broken into the following 8 primary topics, each con
7268
- Service to Service Authentication
7369
- User Authorization
7470

75-
*If you do not see a topic or lesson you would like covered, please review our [open issues](https://github.com/podium/elixir-secure-coding/labels/new%20content) and our [CONTRIBUTING Guide](./CONTRIBUTING.md) before opening a new issue - but we encourage requests!*
71+
*If you do not see a topic or lesson you would like covered, please review our [open issues](https://github.com/erlef/elixir-secure-coding/labels/new%20content) and our [CONTRIBUTING Guide](./CONTRIBUTING.md) before opening a new issue - but we encourage requests!*
7672

7773
## Usage
7874
### For "Learners"
@@ -83,10 +79,7 @@ Using the ESCT as a consumer of the content is easy by just following these simp
8379
3. **Load the Live Markdown files in an instance of Livebook**
8480
- For further instructions on getting Livebook setup locally, please refer to [their documentation](https://livebook.dev/#install).
8581
4. **Complete the training as instructed and save your progress along the way!**
86-
5. **When you think you're finished, create a PR to **your own fork** of the training repo**
87-
- You will receive feedback as to whether you completed it or not in the CI stage of your version control system<sup>*</sup>
88-
89-
*<sup>\*</sup>Feedback functionality will initially work in GitLab, GitHub support is [in the works](https://github.com/podium/elixir-secure-coding/issues/17) but lower priority*
82+
5. **Feedback will be provided directly within Livebook via the "Graded Cell" smart cell**
9083

9184
### For "Educators"
9285
Using the ESCT as a purveyor of the curriculum is relatively straight-forward:

0 commit comments

Comments
 (0)