Tweak the 6.4 manual

diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex
index 7ed2e1d610f8e539ab8542651c6f0a45f9ffa75b..6a335b158b74871dae56dc42676495480d63fa3f 100644 (file)
--- a/docs/manuals/en/main/dirdconf.tex
+++ b/docs/manuals/en/main/dirdconf.tex
@@ -3123,14 +3123,15 @@ Job {
 
    \label{Director:Pool:ScratchPool}
 \item [ScratchPool = \lt{}pool-resource-name\gt{}]
-   \index[dir]{ScrachPool}
-   \index[dir]{Directive!ScrachPool}
-   This directive permits to specify a dedicate \textsl{Scratch} for the
-   current pool. This pool will replace the special pool named \textsl{Scrach}
-   for volume selection. For more information about \textsl{Scratch} see
-   \ilink{Scratch Pool}{TheScratchPool} section of this manual. This is useful
-   when using multiple storage sharing the same mediatype or when you want to
-   dedicate volumes to a particular set of pool.
+   \index[dir]{ScratchPool}
+   \index[dir]{Directive!ScratchPool}
+   This directive permits specifing a specific scratch Pool to be used for
+   the Job.  This pool will replace the default scratch pool named
+   \textsl{Scratch} for volume selection.  For more information about
+   scratch pools see \ilink{Scratch Pool}{TheScratchPool} section of this
+   manual.  This directive is useful when using multiple storage devices
+   that share the same MediaType or when you want to dedicate volumes to a
+   particular set of pools.
 \label{PoolRecyclePool}
 
    \label{Director:Pool:RecyclePool}
@@ -3140,7 +3141,7 @@ Job {
    This directive defines to which pool
    the Volume will be placed (moved) when it is recycled. Without
    this directive, a Volume will remain in the same pool when it is
-   recycled. With this directive, it can be moved automatically to any
+   recycled. With this directive, it will be moved automatically to any
    existing pool during a recycle. This directive is probably most
    useful when defined in the Scratch pool, so that volumes will
    be recycled back into the Scratch pool. For more on the see the

diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex
index 9d0df5447dcc150368d702e4f60fcbeed6e95f49..14b6b926ec3c65f3bef9d8d7693bd2a6004f6f3e 100644 (file)
--- a/docs/manuals/en/main/newfeatures.tex
+++ b/docs/manuals/en/main/newfeatures.tex
@@ -982,24 +982,21 @@ This project was funded by Bacula Systems.
 \label{seccom:poolfilejobretention}
 
 We added two new Pool directives, \texttt{FileRetention} and
-\texttt{JobRetention}, that take precedence over Client directives of the same
-name. It allows you to control the Catalog pruning algorithm Pool by Pool. For
-example, you can decide to increase Retention times for Archive or OffSite Pool.
+\texttt{JobRetention}, that take precedence over Client directives of the
+same name.  It allows you to control the Catalog pruning algorithm Pool by
+Pool.  For example, you can decide to increase Retention times for Archive
+or OffSite Pool.
 
-It seems obvious to us, but apparently not to some users, that given the
+It seems obvious, but apparently not to some users, that given the
 definition above that the Pool File and Job Retention periods is a global
 override for the normal Client based pruning, which means that when the
 Job is pruned, the pruning will apply globally to that particular Job.
 
-Currently, there is a bug in the implementation that causes any Pool
-retention periods specified to apply to {\bf all} Pools for that
-particular Client.  Thus we suggest that you avoid using these two
-directives until this implementation problem is corrected.
-
 \subsection{Read-only File Daemon using capabilities}
 \label{seccom:fdreadonly}
-This feature implements support of keeping \textbf{ReadAll} capabilities after
-UID/GID switch, this allows FD to keep root read but drop write permission.
+This feature implements support of keeping \textbf{ReadAll} capabilities
+after UID/GID switch, this allows FD to keep root read but drop write
+permission.
 
 It introduces new \texttt{bacula-fd} option (\texttt{-k}) specifying that
 \textbf{ReadAll} capabilities should be kept after UID/GID switch.