Tweaks to the question bank in Asking-questions workshop

We have a problem bank at the end of [this](https://cyf-workshop.netlify.app/asking-questions/) page. I found it difficult to get the trainees to ask questions based on _some_ of them - they had the tendency to try and answer the question right away. Listing here the questions that I remember we had trouble with:

1. "There's a transition on this text, why isn't it working?"
- "Transition" is probably not the right word, because CSS transitions seem to be a completely different beast than styles applied on `:hover`.
- It is not clear what "working" means - perhaps we could have describe what was supposed to happen?
- My suggestion: "This text is supposed to fade into nothing. Why is it flickering out and breaking the layout instead?"

2. "Before running Lighthouse, write down the errors it will give you on this page. Now [validate the HTML](https://validator.w3.org/)."
- They just ran lighthouse and listed the errors before I had a chance to intervene :D
- I personally think the phrasing is rather obvious - do not run light house yet, make predictions first. I think trainees read "lighthouse" and jump into just executing it since they are familiar with the tool.
- My suggestion: Remove references to lighthouse. "What accessibility issues can this page have?". This way it's easier to get trainees to make predictions and elicit ways for them to test their predictions.

3. "Why isn't this paragraph a grid item?"
- Now it was my turn to misunderstand the question. I read it as "Why isn't this paragraph styled as a grid item - why is it not in a table-like layout with borders?". Answer: because it is not styled as a grid item. It's just a list.
- A trainee kindly pointed out that the question probably meant "Why did we choose not to use grids here"?. Answer: because we wanted a list, not a column layout thingy.
- I still can't decide between the two interpretations.