corrections of outdated information

gijscor · web-flow · commit d519e07b69cc · 2018-09-18T08:54:33.000+02:00
Step 1  made no sense, as they refer to previous javaScript exercises, whereas in week 1 they haven't done any JavaScript exercises yet. 
Step 2 also doesn't really makes sense as the students don't yet hand in their homework using pull requests, so commenting can only be done by making an issue, which is not the common way of commenting on code. I think it's much better to do this at a later stage when they make pull requests
diff --git a/Week1/MAKEME.md b/Week1/MAKEME.md
@@ -11,14 +11,13 @@ Topics discussed in class this week:
 
 _Deadline Monday_
 
-All share a video or a resource (this can be a drawing, an article or a podcast) that was helpful for you the last few weeks with learning JavaScript. Please share this in the channel of your class in Slack. Also write as small note about what the resource is about and why you think it's so helpful (you can share more than one if you like).
+All share a video or a resource (this can be a drawing, an article or a podcast) that was helpful for you the last few weeks with learning HTML/CSS. Please share this in the channel of your class in Slack. Also write as small note about what the resource is about and why you think it's so helpful (you can share more than one if you like).
 
 ## Step 2: Feedback
 
 _Deadline Monday_
 
-Give one of your fellow students feedback in Github about their homework of the previous week: Create an issue in their repo, telling them what they did great and what they can improve.
-
+Give feedback on a fellow student on their last HTML/CSS assignment via trello. Make sure to give constructive feedback where you make clear what the person did well, and what parts they can improve of their code / what parts of the website are missing. 
 
 ## Step 3: Git homework
 
