diff --git a/25_Outline/outline.tex b/25_Outline/outline.tex
index f2824f7..c57944d 100644
--- a/25_Outline/outline.tex
+++ b/25_Outline/outline.tex
@@ -164,8 +164,8 @@ Now the recommendation procedure looks as follows:
 
 \begin{itemize}
     \item How to optimise such that no need to search through all stored finished configurations is necessary? (e.g. improve runtime from $\mathcal{O}(n)$ to $\mathcal{O}(log\ n)$)
-    \item How to model hierarchy and knowledge about part of the products in preferences?
-    \item Letting users just chose functions and how much they value them instead of rating individual attributes (more lay friendly). And how does this compare to explicitly choosing preferences.
+    \item How to model hierarchy and knowledge about product components in preferences?
+    \item Letting users set preferences for product functions (e.g. for a forest a recreation function, a productive function, a protective function, etc.). How does it compare to explicitly choosing preferences?
 \end{itemize}