Apply Marco's typo fixes to docs

diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex
index 069679ae030101f73f24d66f28218216843745c9..766d3c6cafb51fc1804496749f4487b1a2c48438 100644 (file)
--- a/docs/manuals/en/main/newfeatures.tex
+++ b/docs/manuals/en/main/newfeatures.tex
@@ -620,7 +620,7 @@ and is available with Bacula Enterprise Edition and Community Edition.
 \section{Class Based Database Backend Drivers}
 
 The main Bacula Director code is independent of the SQL backend
-in version 2.5.0 and greater.  This means that the Bacula Director can be
+in version 5.2.0 and greater.  This means that the Bacula Director can be
 packaged by itself, then each of the different SQL backends supported can
 be packaged separately.  It is possible to build all the DB backends at the
 same time by including multiple database options at the same time.
@@ -640,15 +640,15 @@ Order of testing for databases is:
 \end{itemize}
 
 Each configured backend generates a file named:
-\verb+libbaccats-<sql_backend_name>-<version>.so+ 
+\verb+libbaccats-<sql_backend_name>-<version>.so+
 A dummy catalog library is created named libbaccats-version.so
 
 At configure time the first detected backend is used as the so called
-default backend and at install time the dummy 
+default backend and at install time the dummy
 \verb+libbaccats-<version>.so+ is replaced with the default backend type.
 
 If you configure all three backends you get three backend libraries and the
-postgresql gets installed as the default.  
+postgresql gets installed as the default.
 
 When you want to switch to another database, first save any old catalog you
 may have then you can copy one of the three backend libraries over the
@@ -671,7 +671,7 @@ Then you must update the default backend in the following files:
   grant_bacula_privileges
   make_bacula_tables
   make_catalog_backup
-  update_bacula_tables 
+  update_bacula_tables
 \end{verbatim}
 
 And re-run all the above scripts.  Please note, this means