diff --git a/projects/instructions.tex b/projects/instructions.tex
index cff660e..d8d7b52 100644
--- a/projects/instructions.tex
+++ b/projects/instructions.tex
@@ -1,65 +1,73 @@
 \setlength{\fboxsep}{2ex}
 \fbox{\parbox{0.95\linewidth}{\small 
 
-    This is your project assignment. Please read the instructions before starting your work. 
-    Do not understand the assignment as an exhaustive TODO list, rather the questions below are hints that are meant to guide you and allow for a smoother start. Do not feel limited by the questions; we want to see you diving into it.
+    This is your specific project assignment. The project applies
+    topics from the course on real or simulated data, or is about
+    concepts we haven't covered yet. Work yourself into the data and
+    the topic and in the end present your insights to your fellow
+    students. The instructions to your project are meant as a guide to
+    get you started, but feel free to come up with own ideas. Do not
+    feel limited by the questions. We want to see you diving into it.
+    Do not hesitate to contact us for help on problems and to discuss
+    your ideas.
     
+    \vspace{1ex}
     Happy hacking!
 
-    \vspace{1ex}
+    \vspace{2ex}
     \textbf{Evaluation criteria:}
-
-      You can view the evaluation criteria on the
-      \emph{SciCompScoreSheet.pdf} on Ilias.
-
-      \vspace{1ex}
-      \textbf{Dates:}
-
-      The code and the presentation must be uploaded to ILIAS
-      \textbf{at latest on Sunday, February 21st, 2021, 23:59h}. We
-      will store all presentations on one computer to allow for fast
-      transitions between talks. 
-
-      The presentations are on Monday February 22nd, 09:30--12:00, Tuesday
-      February 23rd, 9:30--11:00 and Wednesday 24th, 09:30--12:00.
-
-      \vspace{1ex}
-      \textbf{Files:}
-
-      \textbf{Hand in your presentation as a pdf file.} Bundle everything (the
-      pdf, the code, and the data) into a {\em single} zip-file named with your last name.
-
-      \textbf{Hint:} create the zip file you want to upload, unpack it
-       somewhere else on your computer and check if your main script is still running properly.
-
-      \vspace{1ex}
-      \textbf{Code:}
-
-      The code must be executable without any further adjustments from
-      our side. (Test it!) A single \texttt{main.m} script coordinates
-      the analysis by calling functions and/or sub-scripts (see Box 1.10 in chapter 1) which produce
-      the {\em same} figures (\texttt{saveas()}-function, pdf or png
-      format) that you use in your slides (your code can also generate
-      additional figures). The code must be comprehensible by a third
-      person (use proper and consistent variable and function names, see chapter 4).
-      \textbf{Hint:} Find out what RTFM means and act accordingly ;). You can also always try to google your problems.
-
-      \vspace{1ex} 
-
-      \emph{Please note your name and matriculation number as a
-      comment at the top of the \texttt{main.m} script.}
-
-
-      \vspace{1ex}
-      \textbf{Presentation:}
-
-      The presentation should be {\em at most} 10\,min long and be held
-      in English. In the presentation you should present figures
-      introducing, explaining, showing, and discussing your data,
-      methods, and results. All data-related figures shown in the
-      presentation must be produced by your program --- no editing
-      or labeling by PowerPoint or other software. It is always a good
-      idea to illustrate the problem with basic plots of the
-      raw-data. Make sure the axis labels are large enough!
+    For your grade we mainly evaluate the technical aspects of your
+    code and figures.  You can view the evaluation criteria in
+    \emph{SciCompScoreSheet.pdf} on Ilias.
+
+    \vspace{2ex}
+    \textbf{Dates:}
+    Deadline for uploading the code and the presentation on ILIAS is\\
+    \centerline{\textbf{Sunday, February 21st, 2021, 23:59h}.}
+
+    The presentations are on Monday February 22nd, 09:30--12:00, Tuesday
+    February 23rd, 9:30--11:00 and Wednesday 24th, 09:30--12:00.
+
+    \vspace{2ex}
+    \textbf{Files:}
+    Bundle everything (the code, the data, and the pdf of the
+    presentation) into a {\em single} zip-file named with your last
+    name.
+
+    \textbf{Hint:} create the zip file you want to upload, unpack it
+     somewhere else on your computer and check if your main script
+     is still running properly.
+
+    \vspace{2ex}
+    \textbf{Code:}
+    The code must be executable without any further adjustments from
+    our side --- test it! A single \texttt{main.m} script
+    coordinates the analysis by calling functions and/or sub-scripts
+    (see Box 1.10 in chapter~1) which produce the {\em same} figures
+    (\texttt{saveas()}-function, pdf or png format) that you use in
+    your slides (of course your code can also generate additional
+    figures). The code must be comprehensible by a third person (use
+    proper and consistent variable and function names and document
+    the code, see chapter~4).  \textbf{Hint:} Find out what RTFM
+    means and act accordingly ;). You are allowed and even
+    encouraged to use the internet for every aspect of your project.
+
+    \vspace{1ex} 
+
+    \emph{Please note your name and matriculation number as a
+    comment at the top of the \texttt{main.m} script.}
+
+    \vspace{2ex}
+    \textbf{Presentation:}
+    Hand in your presentation as a pdf file.
+
+    The presentation should be {\em at most} 10\,min long and be held
+    in English. In the presentation you should present figures
+    introducing, explaining, showing, and discussing your data,
+    methods, and results. All data-related figures shown in the
+    presentation must be produced by your program --- no editing
+    or labeling by PowerPoint or other software. It is always a good
+    idea to illustrate the problem with basic plots of the
+    raw-data. Make sure the axis labels are large enough!
 
 }}