Thesis: removes some todos

diff --git a/thesis/master-thesis-erlenkr.tex b/thesis/master-thesis-erlenkr.tex
index 4eaea92f89d957be1e91853b5a7d4bb59a321a6f..9da86b182f25d6a4ad80e56eb71bd7dfc5fe3969 100644 (file)
--- a/thesis/master-thesis-erlenkr.tex
+++ b/thesis/master-thesis-erlenkr.tex
@@ -3048,7 +3048,6 @@ refactorings.
 The refactoring world of \name{Eclipse} can in general be separated into two parts: The 
 language independent part and the part written for a specific programming 
 language -- the language that is the target of the supported refactorings.  
-\todo{What about the language specific part?}
 
 \subsubsection{The Language Toolkit.}
 The Language Toolkit\footnote{The content of this section is a mixture of 
@@ -3149,13 +3148,9 @@ created with it as a parameter.
 
 \subsection{Shortcomings}
 This section is introduced naturally with a conclusion: The JDT refactoring 
-implementation does not facilitate composition of refactorings. 
-\todo{refine}This section will try to explain why, and also identify other 
-shortcomings of both the usability and the readability of the JDT refactoring 
-source code.
-
-I will begin at the end and work my way toward the composition part of this 
-section.
+implementations do not facilitate composition of refactorings. This section will 
+try to explain why, and also try to identify other shortcomings of both the 
+usability and readability of the JDT refactoring source code.
 
 \subsubsection{Absence of generics in Eclipse source code}
 This section is not only concerning the JDT refactoring API, but also large 
@@ -5070,7 +5065,6 @@ many cases. That it probably did not alter the behavior of a smaller project
 shows us nothing more than that though, and might just be a coincidence. 
 
 \section{Summary}
-\todoin{Write? Or wrap up in final conclusions?}
 \todoin{``Threats to validity''}