main ok but web

[bacula/docs] / docs / manuals / en / main / statistics.tex

diff --git a/docs/manuals/en/main/statistics.tex b/docs/manuals/en/main/statistics.tex
index a5732a46e9e9ce2d60ac05bf663624b6aef3c9d5..82b6b5f747c8eb06f8c1bdc2497116c4719a380a 100644 (file)
--- a/docs/manuals/en/main/statistics.tex
+++ b/docs/manuals/en/main/statistics.tex
@@ -14,16 +14,16 @@ If you (or probably your boss) want to have statistics on your backups to
 provide some \textit{Service Level Agreement} indicators, you could use a few
 SQL queries on the Job table to report how many:
 
-\begin{itemize}
+\begin{bsysitemize}
 \item jobs have run
 \item jobs have been successful
 \item files have been backed up
 \item ...
-\end{itemize}
+\end{bsysitemize}
 
 However, these statistics are accurate only if your job retention is greater
 than your statistics period. Ie, if jobs are purged from the catalog, you won't
-be able to use them. 
+be able to use them.
 
 Now, you can use the \textbf{update stats [days=num]} console command to fill
 the JobHistory table with new Job records. If you want to be sure to take in
@@ -47,7 +47,7 @@ prune (remove) Job records that are older than the specified period.
 
 You can use the following Job resource in your nightly \textbf{BackupCatalog}
 job to maintain statistics.
-\begin{verbatim}
+\begin{lstlisting}
 Job {
   Name = BackupCatalog
   ...
@@ -58,4 +58,4 @@ Job {
     RunsOnClient = no
   }
 }
-\end{verbatim}
+\end{lstlisting}