Describe the bug
Some attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been okay for them to pick from, but I think they may have been stuck on how to imagine the topics as issues, and I can't say for sure how many did not gloss over the instructions (also because their application might have been unclear in the context).

In addition, I noticed that some attendees created files without extensions (so either did not know about Markdown files, or it did not occur to mimic them from the README.md), though GitHub handled this like a champ. The second point might not need solving at all for the purposes of the exercise, because I am in two minds about adding to their load at this stage by explaining Markdown files.

To Reproduce
Steps to reproduce the behavior:

• Well, impossible to reproduce right now unless we put some fresh beginner eyes on this, but it's here: https://github.com/feiphoon/github-workshop/tree/master/workshop/03-creating-issues

Expected behavior
For them to create an issue each, with appropriate title & description, and information to resolve the issue, that can be clearly actioned in and connected to the next part of the exercise.

Suggestions to solve
Open to discussion.

• A screenshot of an issue form showing sample text
• A set of precise content to transfer and input, with instructions on how to solve, but without any solutions.
• To point out Markdown, or to let that slide for now?