diff --git a/Manuals/Bibliography/commoncommands.tex b/Manuals/Bibliography/commoncommands.tex
index e731ee4d7f2..303af64eaf3 100644
--- a/Manuals/Bibliography/commoncommands.tex
+++ b/Manuals/Bibliography/commoncommands.tex
@@ -73,7 +73,7 @@
     tabsize=4,
     rulecolor=,
     language=Fortran,
-        basicstyle=\footnotesize\ttfamily,
+        basicstyle=\small\ttfamily,
         upquote=true,
         aboveskip={\baselineskip},
         belowskip={\baselineskip},
diff --git a/Manuals/FDS_User_Guide/FDS_User_Guide.tex b/Manuals/FDS_User_Guide/FDS_User_Guide.tex
index 5b85c0e0480..057bfa1aad0 100644
--- a/Manuals/FDS_User_Guide/FDS_User_Guide.tex
+++ b/Manuals/FDS_User_Guide/FDS_User_Guide.tex
@@ -1029,7 +1029,6 @@ \subsection{Multiple Meshes}
 
 For cases involving many meshes, you might want to assign them colors using either the character string \ct{COLOR} or the integer triplet \ct{RGB}. You may also want to consider using the multiplying feature to easily create a 3-D array of meshes. See Sec.~\ref{info:MULT} for details.
 
-One other useful parameter for larger MPI jobs is called \ct{VERBOSE} on the \ct{MISC} line. This logical parameter suppresses information related to MPI process and OpenMP thread assignments that is printed to the diagnostic output files. By default, its value is \ct{T} for MPI jobs involving 50 or less processes, and \ct{F} for larger jobs.
 
 
 \subsection{Mesh Alignment}
@@ -12800,7 +12799,7 @@ \section{\texorpdfstring{{\tt MISC}}{MISC} (Miscellaneous Parameters)}
 \ct{TURBULENCE_MODEL}                             & Character    & Section~\ref{info:LES}                  &            & \ct{'DEARDORFF'} \\ \hline
 \ct{TURBULENT_DEPOSITION}                         & Logical      & Section~\ref{info:deposition}           &            & \ct{T}           \\ \hline
 \ct{UNFREEZE_TIME}                               & Real          & Section~\ref{info:FREZ}                 &            &                  \\ \hline
-\ct{VERBOSE}                                       & Logical      & Section~\ref{info:multimesh}            &            &                   \\ \hline
+\ct{VERBOSE}                                       & Logical      & Section~\ref{out:file}                  &            & \ct{F}            \\ \hline
 \ct{VISIBILITY_FACTOR}                            & Real         & Section~\ref{info:visibility}           &            & 3                 \\ \hline
 \ct{VN_MAX}                                       & Real         & Section~\ref{info:VN}                   &            & 1.0               \\ \hline
 \ct{VN_MIN}                                       & Real         & Section~\ref{info:VN}                   &            & 0.8               \\ \hline
@@ -14608,6 +14607,9 @@ \section{Diagnostic Output ({\tt .out})}
 
 Following the completion of a successful run, a summary of the CPU usage per subroutine is listed in the file called \ct{CHID_cpu.csv} (Section~\ref{out:CPU}). This is useful in determining where most of the computational effort is being placed.
 
+Add \ct{VERBOSE=T} to the \ct{MISC} line to add addiational information about time usage to the diagnostic file.
+
+
 \section{Heat Release Rate and Related Quantities (\ct{_hrr.csv})}
 \label{out:hrr}
 
@@ -14691,96 +14693,6 @@ \section{CPU Usage Data}
 \section{Time Step Data}
 \label{out:timestep}
 
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
-The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
-\begin{lstlisting}
-Time Step,Wall Time,Step Size,Simulation Time,CPU Time
-\end{table}
-
-The \ct{CHID_cpu.csv} file is printed out at the end of the simulation. To force it to be printed out periodically during the simulation, set \ct{DT_CPU} or \ct{RAMP_CPU} on the \ct{DUMP} line. The latter parameter allows you to write out the files at specified times.
-
-\section{Time Step Data}
-\label{out:timestep}
-
 The file called \ct{CHID_steps.csv} records data on the size of time steps and the amount of elapsed CPU time.
 \begin{lstlisting}
 Time Step,Wall Time,Step Size,Simulation Time,CPU Time