Fix typos

en/chap01.tex

@@ -49,7 +49,7 @@ but check state of individual hosts. It is possible for them to run locally, as
 is the case for Plotnetcfg~\cite{plotnetcfg}, or check the host over the network
 (CaLStats~\cite{calstats}, Icinga~\cite{icinga}), but they do not provide
 overall picture. The capabilities of these tools also differ, from just
-checking reachability (CaLStats) to being able to retreive various details from
+checking reachability (CaLStats) to being able to retrieve various details from
 the hosts (Icinga, plotnetcfg).
 
 This approach can also miss some issues with the system, as described in the

en/chap02.tex

@@ -281,7 +281,7 @@ will later simplify parsing.
 \section{Test network system: Gennet}\label{s:gennet}
 
 To help test Birdvisu and understand network behaviour, we created a simple set
-of scripts called Gennet. Sice it was mainly written to aid Birdvisu, we
+of scripts called Gennet. Since it was mainly written to aid Birdvisu, we
 provide it as attachment~\ref{att:gennet} of this thesis.
 
 Gennet is a network generator. Using a hard-coded configuration and a set of

en/chap03.tex

@@ -157,7 +157,7 @@ stored only in the incident Vertices.
 
 A Topology can be marked as \uv{frozen}. This denotes an intent that it really
 should not be modified, because other code might rely on the particular shape
-of the Topology. However, making the Topology trully immutable would be
+of the Topology. However, making the Topology truly immutable would be
 impractical in Python, so we opted for this approach. In case our solution
 turns out to be prone to accidental modification of the Topology, we will
 deploy additional countermeasures against that.
@@ -176,7 +176,7 @@ There are a few caveats with parsing topologies from the ospffile format.
 First, the edges from routers to networks can only be resolved after the
 networks are known, since network's level-2 block contains information not
 present in the level-3 directive for the router (namely, the designated router
-for OSPFv2 natworks and the set of addresses for OSPFv3).
+for OSPFv2 networks and the set of addresses for OSPFv3).
 
 Since BIRD may be running more than one instance of OSPF, the
 BirdSocketTopologyProvider contains an ad-hoc parser of the response to the
@@ -243,7 +243,7 @@ As with frozen Topologies, this is not enforced by the code.
 Annotators may be used for various tasks, including but not limited to
 performing analysis of the Topology, enhancing it with additional data (e.g.
 ping response times from other system), or specifying parameters for
-visualisation. As a part of Birdvisu itself, we ship several anotators:
+visualisation. As a part of Birdvisu itself, we ship several annotators:
 TopologyDifference outputs the differences between the reference and current
 Topology, and ShortestPathTree marks the edges of the shortest path DAG. The
 next section describes how Annotators aid visualising the data.
@@ -344,7 +344,7 @@ were not satisfied with its result. To demonstrate, the
 listing~\ref{lst:graphviz} describes the topology of our home network with
 Gennet attached. Figure~\ref{fig:graphviz} then shows how each of Graphviz's
 layout engines draws the topology. While it could be possible to tweak the
-engine setings, we believe the user still knows better, so we did not continue
+engine settings, we believe the user still knows better, so we did not continue
 exploring this idea.
 
 \lstinputlisting[float=h,label=lst:graphviz,caption=Author's home topology]{../img/graphviz-fail/source.dot}

en/chap04.tex

@@ -39,7 +39,7 @@ topologies. Both can be loaded from a file, the current one can also be
 retrieved directly from a running BIRD via its socket. In the latter case, the
 user is provided with a dialog to pick an area and OSPF instance.
 
-Once both topologies are loaded, the graph of the topolgy appears. Now, the
+Once both topologies are loaded, the graph of the topology appears. Now, the
 vertices can be moved around to the user's liking. Alternatively, the
 \emph{Positions} menu provides a way to load the positions of vertices from a file.
 

en/epilog.tex

@@ -46,7 +46,7 @@ There are many ways Birdvisu can be expanded in the future. Apart from the
 stated ones (exports, better vertex placements, \dots), it could be possible to
 support other routing daemons and even other link-state protocols like Babel.
 
-Another interresting possible use case could be running Birdvisu headless. When
+Another interesting possible use case could be running Birdvisu headless. When
 combined with the export feature, this could allow using the project as a data
 source for other visualisation tools. While this is currently not possible,
 because the GUI controls all the parts of the program, it might be possible to