From: Kern Sibbald <kern@sibbald.com>
Date: Fri, 18 Sep 2009 16:58:22 +0000 (+0200)
Subject: Tweaks to English and spelling
X-Git-Tag: Release-3.0.3~2^2~23
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=3af8f87e553f3d11a6e0ee569163c886cfb0430e;p=bacula%2Fdocs

Tweaks to English and spelling
---

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index ad0b843e..ea7e63ce 100644
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -102,10 +102,10 @@ This project was funded by Bacula Systems.
 \section{Accurate Fileset options}
 \label{sec:accuratefileset}
 
-In previous version, the accurate code was using file time creation and
-modification to determine if a file was modified or not. Now you can specify
-witch attribute to use (time, size, checksum, permission, owner, group,
-\dots).
+In previous versions, the accurate code used the file creation and
+modification times to determine if a file was modified or not. Now you can specify
+which attributes to use (time, size, checksum, permission, owner, group,
+\dots), similar to the Verify options.
 
 \begin{verbatim}
 FileSet {
@@ -158,16 +158,17 @@ FileSet {
   compare the SHA1 signature  
 \end{description}
 
-\textbf{Important note:} If you decide to use checksum in Accurate jobs, the
-File Daemon will have to read all files even if they won't be saved. It
-increases the I/O load, but also the security. By default, Bacula will 
-check modification/creation time and size.
+\textbf{Important note:} If you decide to use checksum in Accurate jobs,
+the File Daemon will have to read all files even if they normally would not
+be saved.  This increases the I/O load, but also the accuracy of the
+deduplication.  By default, Bacula will check modification/creation time
+and size.
 
 \section{Bvfs API}
 \label{sec:bvfs}
 
-To help developers in restore GUI interfaces, we have added new \textsl{dot
-  commands} that permit to browse the catalog in a very simple way.
+To help developers of restore GUI interfaces, we have added new \textsl{dot
+  commands} that permit browsing the catalog in a very simple way.
 
 \begin{itemize}
 \item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update the
@@ -176,12 +177,12 @@ To help developers in restore GUI interfaces, we have added new \textsl{dot
 
 \item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
   will list all directories in the specified \texttt{path} or
-  \texttt{pathid}. Using \texttt{pathid} avoids problems with caracters
-  encoding.
+  \texttt{pathid}. Using \texttt{pathid} avoids problems with character
+  encoding of path/filenames.
 
 \item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
   will list all files in the specified \texttt{path} or \texttt{pathid}. Using
-  \texttt{pathid} avoids problems with caracters encoding.
+  \texttt{pathid} avoids problems with character encoding.
 \end{itemize}
 
 You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
@@ -197,7 +198,7 @@ data that will be displayed.
 \label{sec:btapespeed}
 
 To determine the best configuration of your tape drive, you can run the new
-\texttt{speed} command available in \texttt{btape}.
+\texttt{speed} command available in the \texttt{btape} program.
 
 This command can have the following arguments:
 \begin{itemize}
@@ -250,7 +251,7 @@ done by adding:
 Block Checksum = no
 \end{verbatim}
 
-doing so can reduce the Storage daemon CPU speed slightly.  It
+doing so can reduce the Storage daemon CPU usage slightly.  It
 will also permit Bacula to read a Volume that has corrupted data.
 
 The default is {\bf yes} -- i.e. the checksum is computed on write
@@ -258,7 +259,7 @@ and checked on read.
 
 We do not recommend to turn this off particularly on older tape
 drives or for disk Volumes where doing so may allow corrupted data
-to be undetected.
+to go undetected.
 
 \section{New Bat Features}