Spelling corrections

1 files changed, 6 insertions, 6 deletions

diff --git a/assets/manual2/manual.tex b/assets/manual2/manual.tex
index db777d9..7faed25 100644
--- a/assets/manual2/manual.tex
+++ b/assets/manual2/manual.tex
@@ -554,7 +554,7 @@ After assigning a signal to a TCB side, you can right click it to open up the si
 
 \section{Routes}\label{s:ilroutes}
 
-Routes contain information on where a train goes to, which section should be reserved for the train to pass, and how certain compontents, such as turnouts, should be set up. Routes are bound to TCB sides, but they usually need to start at ones with a signal assigned. In most cases, routes should also end in such a way that a train leaving the route can immediately enter the next route, with the most common exception being situtations where dead ends are involved, such as train yards and termini where the line physically ends (e.g. Stuttgart Hauptbahnhof).
+Routes contain information on where a train goes to, which section should be reserved for the train to pass, and how certain components, such as turnouts, should be set up. Routes are bound to TCB sides, but they usually need to start at ones with a signal assigned. In most cases, routes should also end in such a way that a train leaving the route can immediately enter the next route, with the most common exception being situations where dead ends are involved, such as train yards and termini where the line physically ends (e.g. Stuttgart Hauptbahnhof).
 
 A relatively simple example can be seen in the graph below.
 
@@ -637,7 +637,7 @@ Station/stop tracks (sometimes simply called \textit{station tracks}) are specia
 
 \section{Considerations for interlocking}\label{s:ilconsiderations}
 
-The previous sections were mainly theoretical in that the sections mostly introduced new concepts or described how to do things. This section will focus on the paractical part of interlocking, in particular certain things to consider when setting up interlocking on a rail line.
+The previous sections were mainly theoretical in that the sections mostly introduced new concepts or described how to do things. This section will focus on the practical part of interlocking, in particular certain things to consider when setting up interlocking on a rail line.
 
 \subsection{Junctions}\label{s:iljunctions}
 
@@ -654,7 +654,7 @@ As an exercise in section \ref{s:xings}, you were asked to build a T junction. A
   \draw (-3,1) -- (3,1);
 \end{centeredtikzpicture}
 
-The lazy method would be to set up the entire junction as a single track section - you only need 6 TCBs for that. However, a train passing through would occupy the entire junction, even when two trains could use the junction at the same time - for example, a train going from east to west and another one from west to east. This can be solved by a slighly more complicated setup with four sections, each shown below with a different color:
+The lazy method would be to set up the entire junction as a single track section - you only need 6 TCBs for that. However, a train passing through would occupy the entire junction, even when two trains could use the junction at the same time - for example, a train going from east to west and another one from west to east. This can be solved by a slightly more complicated setup with four sections, each shown below with a different color:
 
 \begin{centeredtikzpicture}[ultra thick]
   \draw [<-,red] (-3,2) -- (-1.5,2) arc [start angle=90,end angle=60,radius=2];
@@ -985,7 +985,7 @@ The following events are available in LuaATC:
 \item[digiline] Like \texttt{int} (see below), but triggered with digiline. The channel and message are included in the \texttt{channel} and \texttt{message} fields, respectively.
 \item[ext\_int] Like \texttt{int} (see below), but triggered when the interrupt is called by a different active component. The message is only included in the \texttt{message} field.
 \item[int] Triggered by a call to \texttt{interrupt}. The message is included in the \texttt{msg} and (supposedly for backward compatibility) \texttt{message} fields.
-\item[punch] Trigged when the LuaATC operator panel is punched.
+\item[punch] Triggered when the LuaATC operator panel is punched.
 \item[schedule] Like \texttt{int}, but triggered by the scheduler instead. The message is included in the \texttt{msg} field.
 \item[train] Triggered when a train drives pass the LuaATC track. The event table contains an \texttt{id} field, which holds the train ID. This event is only available to LuaATC tracks.
 \end{ttdescription}
@@ -993,9 +993,9 @@ The following events are available in LuaATC:
 \subsection{Approach callback}
 This subsection is relevant to the \texttt{approach} event.
 \begin{ttdescription}
-\item[atc\_set\_lzb\_tsr(\argname{speed})] Set the temporary speed restriciton of the train to \argname{speed} at the position of the track. This needs to be called every time the \texttt{approach} callback is triggered.
+\item[atc\_set\_lzb\_tsr(\argname{speed})] Set the temporary speed restriction of the train to \argname{speed} at the position of the track. This needs to be called every time the \texttt{approach} callback is triggered.
 \end{ttdescription}
-Approach callbacks are executing during the train step. This may be problematic when proforming actions with side effects on the environment that the train is in, such as switching turnouts or setting routes. It is encouraged to only run things that are necessary and defer everything else to an interrupt or a schedule.
+Approach callbacks are executing during the train step. This may be problematic when performing actions with side effects on the environment that the train is in, such as switching turnouts or setting routes. It is encouraged to only run things that are necessary and defer everything else to an interrupt or a schedule.
 
 The following operations are safe in the approach callback:
 \begin{itemize}