[handbook][cleanup] Replace \ by \par.

doc/handbook/2_detailedinstall.tex

@@ -194,7 +194,7 @@ to avoid confusing it with the option files which came out of the distribution.
 \label{quick-start-guide}
 The previous section showed how to install and compile \Dumux. This section
 shall give a very brief introduction how to run a first test application and how
-to visualize the first output files.\\
+to visualize the first output files.\par
 All executables are compiled in the \texttt{build} subdirectories of \Dumux.
 If not given differently in the input files, this is \texttt{build-cmake} as default.
 
@@ -203,7 +203,7 @@ If not given differently in the input files, this is \texttt{build-cmake} as def
       folders can be found. Let us consider as example\\
       \texttt{porousmediumflow/2p/implicit/incompressible/test{\_}2p{\_}incompressible{\_}tpfa}.
 \item Enter the folder \texttt{porousmediumflow/2p/implicit/incompressible}.\\ Type \texttt{make test{\_}2p{\_}incompressible{\_}tpfa}
-      in order to compile the application\\ \texttt{test{\_}2p{\_}incompressible{\_}tpfa}. To run the simulation,
+      in order to compile the application\\\texttt{test{\_}2p{\_}incompressible{\_}tpfa}. To run the simulation,
       type \texttt{./test{\_}2p{\_}incompressible{\_}tpfa params.input}
       into the console.
       The added \texttt{params.input} specifies that all

doc/handbook/4_developingdumux.tex

@@ -41,7 +41,7 @@ more information.
 The options needed to be specified for that are provided using option files like
 \texttt{debug.opts} and \texttt{optim.opts}. These two compile \Dune and \Dumux
 either for debugging or for fast simulation. Programs compiled with optimization options
-can lead to a speedup of factor up to ten!\\
+can lead to a speedup of factor up to ten!\par
 In contrast programs that are compiled with optimization can hardly be debugged.
 You can modify the files and change the compiler, the name of the build director,
 add third-party dependencies, add additional compiler flags, ... .

doc/handbook/4_externaltools.tex

@@ -46,7 +46,7 @@ Secondly you have to define an instance of the class GnuplotInterface (e.g. call
 Dumux::GnuplotInterface<double> gnuplot_;
 \end{lstlisting}
 
-Usually with the ploting is dealt within a function \texttt{postTimeStep}, which firstly extracts the variables (in the exapmle below \texttt{x\_} and \texttt{y\_}) which shall be plotted. The actual plotting is done using the method of the gnuplot interface.\\
+Usually with the ploting is dealt within a function \texttt{postTimeStep}, which firstly extracts the variables (in the exapmle below \texttt{x\_} and \texttt{y\_}) which shall be plotted. The actual plotting is done using the method of the gnuplot interface.
 
 Example:
 \begin{lstlisting}[style=DumuxCode]

doc/handbook/4_parameterfiles.tex

@@ -83,7 +83,7 @@ auto modelParamGroup1 = "Model1";
 static const TYPE paramname1 = getParamFromGroup<TYPE>(modelParamGroup1, "GROUPNAME.PARAMNAME");
 \end{lstlisting}
 
-The \texttt{FVProblem} class provides a convenience function \texttt{paramGroup()}.\\
+The \texttt{FVProblem} class provides a convenience function \texttt{paramGroup()}.
 
 The parameters can then be specified in the input file:
 

doc/handbook/5_spatialdiscretizations.tex

@@ -192,9 +192,9 @@ volume faces. This is a two point flux approximation since the flux between
 the element/control volume centers $i$ and $j$ is calculated
 only with information from these two points. In contrast the box method uses
 a multi-point flux approximation where all nodes of the
-element influence the flux between two specific nodes. \\
+element influence the flux between two specific nodes. \par
 Neumann boundary conditions are applied at the boundary control volume faces
-and Dirichlet boundary conditions at the boundary control volumes. \\
+and Dirichlet boundary conditions at the boundary control volumes. \par
 The cell centered finite volume method is robust and mass conservative but
 should only be applied for structured grids
 (the control volume face normal vector ($n_{ij}$) should be parallel to the
@@ -215,7 +215,7 @@ volume centers).
 In the two-dimensional free-flow models, the continuity equation is discretized using the black control volumes, the $x$-component of the momentum equation is discretized using the blue control volumes and the $y$-component is discretized using the red control volumes. In three dimensions this works analogously.}
 \end{figure}
 
-The staggered-grid or marker-and-cell method uses a finite volume method with different control volumes for different equations. There are control volumes centered around the scalar primary variables. They correspond to the finite volume mesh. Additionally, there are control volumes located around the $x,y$ and (in 3D) $z$ velocity components which are shifted in the $x,y$ and $z$ direction, such that the velocity components are located on the edges of the cell-centered finite volume mesh (see Figure~\ref{pc:staggered}). As for the cell-centered method, the fluxes are evaluated at the edges of each control volume with a two-point flux approximation, cf. \ref{cc}.\\
+The staggered-grid or marker-and-cell method uses a finite volume method with different control volumes for different equations. There are control volumes centered around the scalar primary variables. They correspond to the finite volume mesh. Additionally, there are control volumes located around the $x,y$ and (in 3D) $z$ velocity components which are shifted in the $x,y$ and $z$ direction, such that the velocity components are located on the edges of the cell-centered finite volume mesh (see Figure~\ref{pc:staggered}). As for the cell-centered method, the fluxes are evaluated at the edges of each control volume with a two-point flux approximation, cf. \ref{cc}.\par
 The staggered-grid method is robust, mass conservative, and free of pressure oscillations
 but should, as the cell-centered TPFA method, only be applied for structured grids.
 Currently, all free-flow models in \Dumux use the staggered-grid discretization.