Update question template

Author: bkoelman

.github/ISSUE_TEMPLATE/question.md

@@ -7,14 +7,25 @@ assignees: ''
 
 ---
 
+<!--
+Remember that no-one is getting paid to answer your question. You're basically asking other people to give up their time to help you out of the goodness of their heart – it's up to you to do all you can to make that as simple as possible, so read https://codeblog.jonskeet.uk/2012/11/24/stack-overflow-question-checklist/ first.
+-->
+
 #### SUMMARY
-<!-- Explain what you're trying to accomplish, how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. -->
+<!--
+Explain what you're trying to accomplish, how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself.
+-->
 
 #### DETAILS
-<!-- What details can you include that will help us identify and solve your problem? -->
+<!--
+What details can you include that will help us identify and solve your problem?
+If your program produces different results from what you expected, state what you expected, why you expected it, and the actual results.
+-->
+
 
 #### STEPS TO REPRODUCE
-<!-- Not all questions benefit from including code, but if your problem is with the code you've written, you should consider including your models, DbContext, controllers, resource services, repositories, resource definitions, etc. Include the request URL with body (if applicable) and the full exception stack trace (set `options.IncludeExceptionStackTraceInErrors` to `true`) in case of errors. It may also be helpful to include the produced SQL, which can be made visible in logs by adding this to appsettings.json:
+<!--
+Not all questions benefit from including code, but if your problem is with the code you've written, you should consider including your models, DbContext, controllers, resource services, repositories, resource definitions, etc. Include the request URL with the response body (if applicable) and the full exception stack trace (set `options.IncludeExceptionStackTraceInErrors` to `true`) in case of errors. It may also be helpful to include the produced SQL, which can be made visible in logs by adding this to appsettings.json:
 
 ```json
 {