diff --git a/documentation/design-documentation/chapters/chapter03.tex b/documentation/design-documentation/chapters/chapter03.tex
index 0c3aa4471f6f41691a86110626e117fb598d7b24..8f148931a7c6b27be8764df814596462e662d2ab 100644
--- a/documentation/design-documentation/chapters/chapter03.tex
+++ b/documentation/design-documentation/chapters/chapter03.tex
@@ -23,6 +23,10 @@ Some loose thoughts for this chapter, as data networks consists out of:
 		\item point-to-multipoint (multicast or broadcast)
 		\item multi-point-to-multipoint (multicast or broadcast) (XXX is this really true?)
 	\end{enumerate}
+	\item configuration of interfaces
+	\item configuration of hosts
+	\item configuration of services on hosts
+	\item configuration of global parameters, i.e., the network
 \end{enumerate}
 
 \subsection{Can the network be changed during operation?}
@@ -37,7 +41,7 @@ Changes of device or service configurations -- this is intended for semi-static
 Changes of forwarding behavior -- this is intended for dynamic configurations that require to keep state in the network:
 \begin{enumerate}
 	\item classical way: not possible, as human interaction is just too slow for any reaction.
-	\item network build-in: the control plane of a network device autonomously decides to change the flow forwarding behavior. Examples are: IP routing, firewwalls and Network Address Translators (NATs). 
+	\item network build-in: the control plane of a network device autonomously decides to change the flow forwarding behavior. Examples are: IP routing, firewalls and Network Address Translators (NATs). 
 	\item SDN way: forwarding behavior of the network can be changed via an API
 \end{enumerate}