Update 2.3.1_research_question.md

Author: vmkhot

_episodes/2.3.1_research_question.md

@@ -32,10 +32,11 @@ Here are a few papers that caught our eye, maybe they inspire you (feel free to
 Choose one type of project that better fits your interests:  
 
 1. Go into detail into analyses  
-2. Build a broader research proposal  
+2. Build a broader research proposal
 
-{:start='1'}
-1. This type of project is more hands-on. You might write your own script(s), run your own analyses and produce your own plots. The idea here would be to focus on one of the methods/analyses we covered in the course and to go deeper into the analysis. In any case, the question you want to address should be clearly defined.
+## Detailed Analyses
+
+This type of project is more hands-on. You might write your own script(s), run your own analyses and produce your own plots. The idea here would be to focus on one of the methods/analyses we covered in the course and to go deeper into the analysis. In any case, the question you want to address should be clearly defined.
 
 An example: "What are the differences between functional annotation done with Pharokka and Genomad?". 
 
@@ -47,11 +48,14 @@ Below are what should be included in your documentation/presentation for project
 - What will be the inputs and outputs?
 - Which programs will (do you plan to) use?
 
-- What are your expected results?
-- 
+Note that hypotheses do not need be proven. We want to see from you as results:
+
+Output (a table or a figure)
+Interpretation of the output: what does the data tell you?
+Does it answer your question? It does not have to. In a negative case, can you say what you might do differently next time
 
-{:start='2'}
-2. This type of project is more in the style of a research proposal with a broader scope. You should focus on the biological questions and how to address them using viromics.
+## Research Proposal Style
+This type of project is more in the style of a research proposal with a broader scope. You should focus on the biological questions and how to address them using viromics.
 
 Your hypothesis and aims should be clear and backed-up by the literature.
 
@@ -64,21 +68,14 @@ Below are what should be included in your documentation/presentation for project
 - Estimate the complexity of the problem  
 
 
+# Presentation  
 
-- expected results
-- Hypotheses don't need be proven - can be null hypothesis
-- If you choose to do the detailed analyses:
-    - Generate an output (a table or a figure)
-    - Interpretation of the output: what does the data tell you? 
-    - Does it answer your question? (It doesn't have to, you can say what you might do differently next time)
-
-Presentation  
-
-- comprehensive
-- has to connect back to hypothesis
-
-# Exercise
+- Present the project you worked on
+- Limitations
+- Things you found particularly interesting
+- Any lessons learnt
 
+Your project notes should still go into your lab book
 
 > ## Exercise
 > 1. Once you have an idea of a research question, take some time to talk about your idea with your fellow students.