Skip to content
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.

Typos in guidelines on eval sheet #51

Closed
Jeroenvh99 opened this issue Oct 11, 2022 · 3 comments
Closed

Typos in guidelines on eval sheet #51

Jeroenvh99 opened this issue Oct 11, 2022 · 3 comments
Assignees
Labels
Core Issues is regarding Core curriculum Scale Issue is in the scale (eval sheet)

Comments

@Jeroenvh99
Copy link

Jeroenvh99 commented Oct 11, 2022

Project Name
This issue is a collection of typos in the guidelines section on libft's eval sheet, but I think the guidelines are pretty similar for every eval sheet in the core

What is the issue

  • Under guidelines: "... work that was turned in the Git ..." -> "that was turned in in the Git".

  • Under guidelines, third point: "... no malicious aliases was used ..." -> "... no malicious aliases were used ..."

  • Under guidlines, fourth point: move the word togehter to the end -> "... the grading (scripts for testing or automation) together."

  • Under guidelines, ninth point: Also move together at the end of the sentence -> "... are strongly encouraged to review the work that was turned in together."

Expectation
See the section above

Additional context
None

@W2Wizard
Copy link
Contributor

Please keep it short next time, its hard to read a giant block of text and trying to figure out differences. If I have enough text I can find the rest.

@Jeroenvh99
Copy link
Author

Ah, I see that you added bullet points, this indeed makes it easier to read

@W2Wizard W2Wizard added Core Issues is regarding Core curriculum Scale Issue is in the scale (eval sheet) labels Oct 13, 2022
@W2Wizard
Copy link
Contributor

Fixes were implemented

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Core Issues is regarding Core curriculum Scale Issue is in the scale (eval sheet)
Projects
None yet
Development

No branches or pull requests

2 participants