diff --git a/programming/lecture/programming.tex b/programming/lecture/programming.tex
index 50adf7d..51ea85e 100644
--- a/programming/lecture/programming.tex
+++ b/programming/lecture/programming.tex
@@ -1560,14 +1560,16 @@ legend('show')
     \includegraphics[width=0.9\columnwidth]{simple_program}
   \end{minipage}
   \begin{minipage}{0.5\textwidth}
-    \textbf{Controlling a task} that involves calling sub-routines, as
-    we did above, is one of these situations (see figure). The script
-    calls functions and takes care of passing the right arguments and
-    storing the return values.  During the development phase a script
-    grows as one \emph{interactively} works on the command
+    \textbf{Controlling a task.} Solving tasks that involve calling
+    sub-routines, as we did above, is one of these situations (see
+    figure). The script calls functions and takes care of passing the
+    correct arguments and storing the return values.  \linebreak
+    \textbf{Interactive development.} During the development phase a
+    script grows as one \emph{interactively} works on the command
     line. Commands that have been tested are then transferred to the
-    script. 
+    script.
   \end{minipage}\vspace{0.25cm}
+
   Interactive programming is one of the main strengths of
   \matlab{}. Interactive refers to the interaction between the
   commands executed on the command line and the variables stored in
@@ -1575,7 +1577,8 @@ legend('show')
   on the data stored in a variable or if the returned results are
   correct speeds up the developmental progress.
 
-  As soon as there is code duplication in a script or it grows too
-  large, it is high time to consider extracting features into separate
-  functions.
+  \textbf{Special solutions.} Program code that is only valid one very
+  specific problem may reside in a script. As soon as there is code
+  duplication or it grows too large, it is high time to consider
+  extracting features into separate functions.
 \end{ibox}