Fixed ragged hyphenations, minor tweaks

Author: rayhem

chapters/Getting_your_toes_wet.tex

@@ -40,7 +40,8 @@
 \end{lstlisting}
 
 For your first program, open a terminal, create a directory for ICCP files and open your first Fortran file by typing
-\marginnote[-0.5cm]{Modern terminal emulators all have a feature called \emph{tab completion}; enter part of a command \& hit the \texttt{TAB} key and the terminal will attempt to fill in the rest of the command for you.}
+\marginnote[-0.5cm]{Modern terminal emulators all have a feature called
+  \emph{tab completion}\index{Tab completion}; enter part of a command \& hit the \texttt{TAB} key and the terminal will attempt to fill in the rest of the command for you.}
 \begin{lstlisting}[style=prompt, nolol]
   $ mkdir iccp          # create a new directory called 'iccp'
   $ cd iccp             # move to the new directory

chapters/Optimization.tex

@@ -116,7 +116,9 @@ \section{Scalability; or, the importance of big O}
 Numerical analysis is a large field, and it can be quite daunting trying to understand the merits of different methods, or even finding them.
 For this, we recommend the book \emph{Numerical Recipes}\footnote{Available free online at \url{http://apps.nrbook.com/fortran/index.html}}.
 It covers a wide range of topics, focuses on best practices, and does not ignore coding effort when comparing algorithms.
-It even includes the full source code of the implementations! We recommend always using it as your starting point, with one exception: linear algebra (see \autoref{chap:Linear algebra}).
+It even includes the full source code of the implementations! We recommend
+always using it as your starting point, with one exception: linear algebra
+(see \autoref{chap:Linear algebra}).
 
 We conclude this section with an overview of the computational complexity of certain common operations.
 This will give you an idea of the most likely bottleneck in your code.

chapters/Structuring_your_code.tex

@@ -31,7 +31,8 @@ \section{Functions and subroutines}
 Fortran subroutines are invoked with the keyword \keyword{call} followed by the name of the routine and an optional list of parameters in parentheses.
 The code for the subroutine itself appears after the keyword \keyword{contains}.
 We don't have to type \keyword{implicit none} again, since that's inherited from the program.
-\marginnote{A \textbf{big} fortran gotcha involves initializing local variables while declaring them (\ie\ \lstinline$real :: x = 10.0$). Variables like this have an implicit \keyword{save}\index{Fortran!save@\keyword{save}} statement, meaning they retain their value through subsequent calls to the subroutine. It's a good idea to either mark these variables with the \keyword{save} attribute explicitly \emph{or} separate initialization from declaration within subroutines and functions.}
+\marginnote{A \textbf{big} fortran gotcha involves initializing local
+variables while declaring them (\eg\ \lstinline$real :: x = 10.0$). Variables like this have an implicit \keyword{save}\index{Fortran!save@\keyword{save}} statement, meaning they retain their value through subsequent calls to the subroutine. It's a good idea to either mark these variables with the \keyword{save} attribute explicitly \emph{or} separate initialization from declaration within subroutines and functions.}
 When declaring the parameters, we need to specify not only the type, but also how we're going to use them, \ie, the \emph{intent}.\index{Fortran!intent(in/out)@\keyword{intent} (\keyword{in}/\keyword{out})}
 For input and output parameters, we use \texttt{\keyword{intent}(\keyword{in})} and \texttt{\keyword{intent}(\keyword{out})}, respectively.
 For parameters functioning as both, we use \texttt{\keyword{intent}(\keyword{inout})}.

chapters/The_magic_of_makefiles.tex

@@ -1,6 +1,13 @@
 \Chapter{The magic of Makefiles}{}
 \label{chap:Makefiles}
 
+\begin{quote}
+  \begin{verbatim}
+love: /dev/null
+  @echo not war
+  \end{verbatim}
+\end{quote}
+
 Once your programs become larger, it is convenient to split the source code into several files.
 However, to obtain a running program, each of these files has to be compiled separately (resulting in a \emph{relocatable object file}, with extension \texttt{.o}) and then combined (linked) into a single program.
 Doing this by hand quickly becomes tedious, so we resort to using Makefiles.

notes.tex

@@ -31,6 +31,8 @@
 %\definecolor{TUBlue}{RGB}{61,152,222}
 %\definecolor{SpartanGreen}{RGB}{24,69,59}
 
+\pretolerance=10000
+
 \hypersetup{
     colorlinks=true,
     citecolor=Blue,