Apply manual corrections

diff --git a/docs/manuals/en/concepts/concepts.kilepr b/docs/manuals/en/concepts/concepts.kilepr
index 374c10c86fe3a49385be44f9db2605beed2760c5..ba04ea1525c6cbbc6602dcb7f3eb7c8170b144c8 100644 (file)
--- a/docs/manuals/en/concepts/concepts.kilepr
+++ b/docs/manuals/en/concepts/concepts.kilepr
@@ -161,10 +161,10 @@ order=-1
 
 [item:newfeatures.tex]
 archive=true
-column=23
+column=21
 encoding=
 highlight=LaTeX
-line=18
+line=279
 open=true
 order=0
 

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index bb63c965403d7c7c72f2ff2ebc006e788a511ba7..6ca44924006a148b111946a38e62c99293318047 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -276,8 +276,8 @@ then Bacula will not backup the two directories named:
 \section{Accurate}
 \index[general]{Accurate Backup}
 As with most other backup programs, Bacula decides what files to backup 
-for Incremental and Differental backup by comparing the change (st_ctime)
-and modification (st_mtime) times of the file to the time the last backup completed.
+for Incremental and Differental backup by comparing the change (st\_ctime)
+and modification (st\_mtime) times of the file to the time the last backup completed.
 If one of those two times is later than the last backup time, then the file
 will be backed up.  This does not, however, permit tracking what files have
 been deleted and will miss any file with an old time that may have been

diff --git a/docs/manuals/en/install/dirdconf.tex b/docs/manuals/en/install/dirdconf.tex
index 2f63639c6a86acb3e361b43a7974b99026a3b2ee..84c835570f077f23e23d6973e6d28dc52e2856f3 100644 (file)
--- a/docs/manuals/en/install/dirdconf.tex
+++ b/docs/manuals/en/install/dirdconf.tex
@@ -216,19 +216,15 @@ in the  graphical user interface. This directive is optional.
    should run  concurrently. The default is set to 1, but you may set it to a 
    larger number.  
 
-   Please  note that the Volume format becomes much more complicated with 
-   multiple simultaneous jobs, consequently, restores can take much  longer if
+   The Volume format becomes more complicated with 
+   multiple simultaneous jobs, consequently, restores may take longer if
    Bacula must sort through interleaved volume blocks from  multiple simultaneous
-   jobs. This can be avoided by having each  simultaneously running job write to
+   jobs. This can be avoided by having each simultaneous job write to
    a different volume or  by using data spooling, which will first spool the data
-   to disk simultaneously, then write each spool file to the  volume in
-   sequence.  
+   to disk simultaneously, then write one spool file at a time to the volume
+   thus avoiding excessive interleaving of the different job blocks.
 
-   There may also still be some cases where directives such as  {\bf Maximum
-   Volume Jobs} are not properly synchronized with  multiple simultaneous jobs
-   (subtle timing issues can arise),  so careful testing is recommended. 
-
-   At the current time,  there is no configuration parameter set to limit the
+   At the current time, there is no configuration parameter set to limit the
    number of console connections. A maximum of five simultaneous console 
    connections are permitted.  
 
@@ -2181,10 +2177,7 @@ console run command.  This directive is required.
    with the same name as the resource in which it appears. Any  other
    restrictions on the maximum concurrent jobs such as in  the Director, Job, or
    Storage resources will also apply in addition to  any limit specified here.
-   The  default is set to 1, but you may set it to a larger number.  We strongly
-   recommend that you read the WARNING documented under  
-   \ilink{ Maximum Concurrent Jobs}{DirMaxConJobs} in the Director's
-   resource.  
+   The  default is set to 1, but you may set it to a larger number.
 
 \item [Priority = \lt{}number\gt{}]
    \index[dir]{Priority}