typos

diff --git a/report2/results.tex b/report2/results.tex
index 8b64e9a..0358daf 100644 (file)
--- a/report2/results.tex
+++ b/report2/results.tex
@@ -67,17 +67,23 @@ The assignment was a very interesting and challenging assignment. However, we
 feel that we could not get the most out of it due to several reasons.
 
 First of all it was a hassle to get to know sylvan and to be able to use the
 feel that we could not get the most out of it due to several reasons.
 
 First of all it was a hassle to get to know sylvan and to be able to use the

-package. The most problematic was to understand how can we work with state transitions efficiently. The way it works with sylvan was not evident neither from the introductory lectures, nor from the available documentation. Also, there were some trivial errors in the sylvan package that made
-debugging a lot harder. One of those errors was malformed dot output for
-printing BDDs. In the meantime we have made a pullrequest to fix that.
+package. The most problematic was to understand how can we work with state
+transitions efficiently. The way it works with sylvan was not evident neither
+from the introductory lectures, nor from the available documentation. Also,
+there were some trivial errors in the sylvan package that made debugging a lot
+harder. One of those errors was malformed dot output for printing BDDs. In the
+meantime we have made a pullrequest to fix that.

 
 Secondly, due to the relatively short introduction to BDDs the gap between our
 
 Secondly, due to the relatively short introduction to BDDs the gap between our

-knowlegde and the knowledge required to build such a solver is quite big. This
+knowledge and the knowledge required to build such a solver is quite big. This

 lead to startup problems (which we managed to solve, but lost too much time to it).
 
 lead to startup problems (which we managed to solve, but lost too much time to it).
 

-Finally, we feel a bit frustrated that we only finished and tested the reachability of a goal state checking, but did not finish the extraction of solving sequences. We have a solution for that problem, which shows potential, but still contains bugs.
+Finally, we feel a bit frustrated that we only finished and tested the
+reachability of a goal state checking, but did not finish the extraction of
+solving sequences. We have a solution for that problem, which shows potential,
+but still contains bugs.

 
 

-\subsubsection{Diviion of work}
+\subsubsection{Division of work}

 The work was divided evenly in the beginning of the project. When we noticed
 that we did not have enough time to implement two solutions or even a hybrid
 approach we decided to go through with the solution that seemed the most
 The work was divided evenly in the beginning of the project. When we noticed
 that we did not have enough time to implement two solutions or even a hybrid
 approach we decided to go through with the solution that seemed the most