This repo is for a single team to use as their course home to practice collaboratively maintaining a set of documents.
In your cheatsheets, use 3 back ticks ` to separate out the code and optionally label it withthe type of code, like the following for bash code
```bash
# some code here
```
and use headings to make things clear
Use the following as a template in your reviews.
Is the contribution clear and concise? Identify any aspect of the writing that tripped you up as a reader.
Are the statements in the contribution verifiable (either testable or cited source)? If so, how do you know they are correct?
Does the contribution offer complete information? Does it rely on specific outside knowledge or could another CS student not taking our class understand it?
Identify one strength in the contribution, and identify one aspect that could be strengthened further.